You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update: I did some more digging; it seems that to reproduce what I'm running into you need to also set the directory query key when creating a new session via the api/sdk.
only sessions attaching to this server will appear in the result
idle status gets automatically removed from the list
So to retrieve value from the API, the simplest test is to create a session that attach to the server using opencode attach <server-url> (or create from webui) and let agent start doing stuff, then query /session/status.
Activity
github-actions commentedon Dec 30, 2025
This issue might be a duplicate of existing issues. Please check:
This is a similar API-related issue where session endpoints returned empty responses. Feel free to ignore if this doesn't address your specific case.
fcrisafulli-dev commentedon Dec 30, 2025
Update: I did some more digging; it seems that to reproduce what I'm running into you need to also set the
directoryquery key when creating a new session via the api/sdk.works as expected:
/session/status will always be blank if a session is created like below
rekram1-node commentedon Dec 30, 2025
Yeah this is expected, the server boots up as global, sessions arent necessarily global.
Also there is no sessionid param needed or accepted
TomCC7 commentedon Feb 16, 2026
A clarification to later visitors:
So to retrieve value from the API, the simplest test is to create a session that attach to the server using
opencode attach <server-url>(or create from webui) and let agent start doing stuff, then query/session/status.