GOA orchestrator falsely marks idle worker sessions as queued and spawns duplicate sessions #45

What happened

When orchestrating tasks via GOA, it frequently claims that an existing worker session is still "queued" or busy, refusing to dispatch instructions even though the worker session is already finished and idle. When told that the session is idle, GOA acknowledges the session is idle via enowx_session_read, but then spawns duplicate new session tabs instead of continuing in the idle session.

Steps to reproduce

1. Have an active worker session finish a task and return to idle prompt.
2. In the GOA tab, instruct GOA to continue work or assign the next task to that session.
3. GOA delays or refuses dispatch, asserting that the session is still in a queued state.
4. Point out that the session is idle. GOA admits the queue status was out of sync, but spawns a redundant new session tab instead of reusing the idle session.

enowX version

0.7.0

Where the session ran

This device

Operating systems

Windows 11 x64

Agent and its version

OpenCode 1.18.35 (GOA)

Logs