Skip to content

Session status service has get() method but no single-session HTTP endpoint #29166

Closed as not planned

Description

@wccyzxy

Description

The SessionStatus.Service has a get(sessionID) method that returns a single
session's runtime status (idle/busy/retry), but no HTTP endpoint exposes it.
Currently only GET /session/status exists, which returns all non-idle statuses
as a Record<SessionID, Info>. Clients that need just one session's status have
to pull the full list and filter client-side.
Add GET /session/:sessionID/status that delegates to the existing get() method,
following the same pattern as other single-session endpoints.

Plugins

No response

OpenCode version

1.2.17

Steps to reproduce

  1. Start opencode serve
  2. Call GET /session/:sessionID/status
  3. Get 404 Not Found (endpoint doesn't exist)
  4. Only GET /session/status exists, returns all statuses with no way to query a single session

Screenshot and/or share link

No response

Operating System

Linux(Ubuntu 22.04.5)

Terminal

tmux

Activity

  1. github-actions commented on May 25, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • This reads as a feature request (adding a missing HTTP endpoint), but it doesn't use the [FEATURE]: title prefix and hasn't used the Feature Request template (no verification checkbox, no explanation of the problem/need from a user perspective).
    • If this is intended as a bug report, the required fields (Steps to Reproduce, Operating System, Terminal) are all left as _No response_, which makes it impossible to evaluate.

    Please edit this issue to either:

    1. Convert it to a proper feature request by adding [FEATURE]: to the title and filling in the Feature Request template, or
    2. Fill in the bug report fields with relevant context.

    Please edit this issue to address the above within 2 hours, or it will be automatically closed.


    This issue might be related to existing issues about /session/status. Please check:

    If you believe this was flagged incorrectly, please let a maintainer know.

  2. added
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on May 25, 2026
  3. github-actions commented on May 25, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! It now meets our contributing guidelines — the description is clear, steps to reproduce are provided, and the OS info is included. We appreciate the improvements!

  4. github-actions commented on Jul 25, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions