Skip to content

feat(sdk): expose session resume through API - #52496

Closed
opencode-agent[bot] wants to merge 1 commit into
devfrom
session-resume-api
Closed

opencode-agent[bot] wants to merge 1 commit into
devfrom
session-resume-api

Conversation

@opencode-agent

@opencode-agent opencode-agent Bot commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add POST /api/session/:sessionID/resume to start or join existing execution without admitting a message, returning once it settles.
  • Regenerate Promise/Effect clients and OpenAPI artifacts, and document the prompt({ resume: false }) → sessions.resume() flow in both SDK guides.
  • Cover execution and missing-session behavior through the server endpoint and embedded SDK.

Verification

  • bun test test/session-instances.test.ts (server)
  • bun test test/promise.test.ts --test-name-pattern "Promise host uses the embedded router" (SDK)
  • Package typechecks: client, protocol, server, SDK; focused oxlint; services/www typecheck, generated check, build.
  • Full bun run check was blocked by an unrelated Rolldown thread-pool resource error in @opencode/posts; the SDK file’s pre-existing event cancellation test also fails (receives iterator completion instead of a transport error).

The regenerated OpenAPI snapshots also pick up prior snapshot drift on v2 beyond this endpoint.

Requested by: @kommander (Sebastian via Slack)

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant