ENOSPC: no space left on device #55186

Activity

1. opencode-agent commented on Oct 13, 2026

   

   opencode-agentBot

   on Oct 13, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the report! I think this is a duplicate of #52776. In both, the TUI crashes at startup while it sets up a watch on ~/.config/opencode to reload config changes, and Linux refuses the watch.

   The error says "no space left on device", but here it usually doesn't mean your disk is full. It means your user has run out of inotify watches (fs.inotify.max_user_watches). Every program you run shares that limit, including editors, language servers and other file watchers. A fix that stops this from crashing the TUI is proposed in #52788.

   Until that lands, raising the limit should let OpenCode start:

   sudo sysctl fs.inotify.max_user_watches=524288
   # to keep the setting after a reboot:
   echo 'fs.inotify.max_user_watches=524288' | sudo tee /etc/sysctl.d/99-inotify.conf

   Possible duplicates and related issues, most likely first:

   • TUI crash: ENOSPC: no space left on device, watch '/home/davicompai/.config/opencode' #52776: the same crash, watching ~/.config/opencode, with the same stack trace
   • tui: startup crash with EMFILE when inotify instances are exhausted (unguarded fs.watch in ConfigProvider) #51489: the same config watch failing with EMFILE when inotify instances run out
   • tui: crashes with ENOSPC when inotify watch limit is exhausted #51208: the same kind of ENOSPC crash from another TUI watcher (state storage)

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different. Please follow #52776 for updates.
2. opencode-agent

   added

   pending close

   triaging

   on Oct 13, 2026
3. opencode-agent

   closed this as duplicateon Oct 14, 2026
4. opencode-agent commented on Oct 14, 2026

   

   opencode-agentBot

   on Oct 14, 2026 – with OpenCode Agent

   Contributor

   More actions

   I haven't heard back, so I'm closing this as a duplicate of #52776. It's the same crash: the TUI can't set up its watch on ~/.config/opencode because your user has run out of inotify watches. That's why your disk still has free space. Please follow #52776 for updates. A fix is proposed in #52788.

   Until it lands, raising fs.inotify.max_user_watches should let OpenCode start, for example sudo sysctl fs.inotify.max_user_watches=524288. If your problem turns out to be different, reply here and we can reopen it.