What happened
agentctl peek <id> and agentctl status <id> consistently time out (hit the 5s adapter timeout) when querying opencode sessions. The process is confirmed alive via ps -p.
What was expected
These commands should be near-instant — they read from a .jsonl session file, not a live API call.
How to reproduce
agentctl launch opencode --cwd <dir> -p "<any prompt>"- Wait for session to start working
agentctl peek <id> -n 10 → times outps -p <pid> → confirms process is alive
The agentctl list -a output also shows Warning: Adapter(s) timed out after 5000ms: ... opencode on every invocation.
Workaround
Use ps -p <pid> to check if the process is alive. Can't view session output until it completes.
Environment
agentctl from npm link (local build), opencode 1.2.11 (Homebrew), macOS arm64
What happened
agentctl peek <id>andagentctl status <id>consistently time out (hit the 5s adapter timeout) when querying opencode sessions. The process is confirmed alive viaps -p.What was expected
These commands should be near-instant — they read from a .jsonl session file, not a live API call.
How to reproduce
agentctl launch opencode --cwd <dir> -p "<any prompt>"agentctl peek <id> -n 10→ times outps -p <pid>→ confirms process is aliveThe
agentctl list -aoutput also showsWarning: Adapter(s) timed out after 5000ms: ... opencodeon every invocation.Workaround
Use
ps -p <pid>to check if the process is alive. Can't view session output until it completes.Environment
agentctl from npm link (local build), opencode 1.2.11 (Homebrew), macOS arm64