This error occurs because your system's temporary directory (/tmp) has run out of space, hit a user quota, or lacks execution permissions, preventing the Bun runtime from extracting the native OpenTUI rendering library (libopentui.so).
When applications bundle @opentui/core using a compiled Bun binary, every process invocation extracts a unique libopentui.so file into /tmp. Over time, these accumulated files can completely fill a tmpfs (RAM disk) partition. When space runs out, Bun fails to generate the .so file, triggering a "cannot open shared object file: No such file or directory" crash on the virtual file system ($bunfs) path.
Follow these steps to resolve the issue:
1. Clear out leaked temporary files
Free up space in your temp partition by deleting the stale, leaked shared object files. Safe files to delete can be matched using these patterns in your terminal:
bash
# Safely clear the leaked OpenTUI objects from /tmp rm /tmp/.*.so 2>/dev/null rm /tmp/*libopentui*.so 2>/dev/null
Use code with caution.
(Running processes will retain their open file descriptors in memory, so this is safe to run while troubleshooting).
