Serve mode can retain idle instances and stale subprocess state

[sjawhar]

Description

Shared opencode serve instances can keep stale per-directory resources alive longer than intended: idle instances, subprocess handles, RPC/listener state, and related background cleanup work are not aggressively reclaimed. This shows up as long-lived server state even after the relevant worktree/session is no longer active.

The hardening work here adds explicit instance activity tracking, idle disposal, stale bash process reaping, and listener/cache cleanup so per-directory instances can shut down cleanly instead of accumulating background state.

Plugins

No response

OpenCode version

0.0.0--202604082056 (local built binary / dev branch work)

Steps to reproduce

1. Start opencode serve against a project.
2. Create activity that opens per-directory instances and starts subprocess-backed work (bash/task/LSP/session flows).
3. Leave the server idle or switch away from the active worktree/directory.
4. Observe that process/listener cleanup is incomplete and state can linger longer than expected.

Screenshot and/or share link

No response

Operating System

Ubuntu 24.04

Terminal

Ghostty

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Memory leak: serve and web commands leak child processes on exit; SSE heartbeat interval leaks on server-initiated close #14091: Memory leak: serve and web commands leak child processes on exit — covers similar subprocess and resource cleanup concerns in the serve command (closed)