[TheLoroXD]

Issue for this PR

Closes #29166

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Adds GET /session/:sessionID/status by exposing the existing single-session SessionStatus.Service.get() method over HTTP. The handler first checks that the session exists, matching the other session-specific read endpoints.

This draft also includes generated OpenAPI/SDK changes and route coverage for idle status and typed 404 responses. I saw the duplicate bot flagged #29165 and #29244; this PR keeps the same scope but includes tests and SDK output.

How did you verify your code works?

• bun run script/generate.ts
• bun test --timeout 30000 test/server/httpapi-session.test.ts from packages/opencode
• bun run typecheck from packages/opencode
• pre-push bun turbo typecheck

Screenshots / recordings

N/A, API-only change.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Found potential duplicates! Here are the related PRs:

Potential Duplicates

1. PR feat(api): add single-session status HTTP endpoint #29244: feat(api): add single-session status HTTP endpoint

   • feat(api): add single-session status HTTP endpoint #29244
   • This appears to be addressing the exact same feature (single-session status HTTP endpoint)

2. PR fix(opencode): expose single session status endpoint #29165: fix(opencode): expose single session status endpoint

   • fix(opencode): expose single session status endpoint #29165
   • Also related to exposing the session status endpoint

These PRs are likely addressing the same GitHub issue (#29166 mentioned in your description) and may have overlapping changes or implementations for the session status endpoint feature.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍

[github-actions]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.