Skip to content

feat(core): implement v2 session forking - #34343

Closed
opencode-agent[bot] wants to merge 1 commit into
v2from
session-forking
Closed

opencode-agent[bot] wants to merge 1 commit into
v2from
session-forking

Conversation

@opencode-agent

Copy link
Copy Markdown
Contributor

Summary

  • add SessionV2.fork(...) that creates a child session and copies projected history rows with fresh message IDs
  • copy promoted session input rows and advance the child event sequence so future prompts do not collide with copied seqs
  • expose /api/session/:sessionID/fork and regenerate the client

Notes

  • messageID acts as an exclusive boundary to match the existing app flow that restores the selected user prompt into the input box.
  • The fork is a point-in-time copy; later parent history changes do not affect the child.

Tests

  • bun test test/session-create.test.ts from packages/core
  • bun typecheck from packages/core
  • bun typecheck from packages/protocol
  • bun typecheck from packages/server
  • bun typecheck from packages/client
  • pre-push hook: bun turbo typecheck (29/29 tasks successful)

Co-authored-by: opencode-agent[bot] <opencode-agent[bot]@users.noreply.github.com>
@thdxr
thdxr marked this pull request as ready for review June 29, 2026 01:16
@opencode-agent opencode-agent Bot added 2.0 core Anything pertaining to core functionality of the application (opencode server stuff) labels Jul 3, 2026
@github-actions

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

Labels

2.0 automated-pr-cleanup contributor core Anything pertaining to core functionality of the application (opencode server stuff)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant