[FEATURE]: Ability to pass in a sessionId for the opencode session to be tied to #4398

Closed
opened 2026-02-16 17:43:40 -05:00 by yindo · 2 comments
Owner

Originally created by @quuu on GitHub (Jan 7, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I have a multi-opencode orchestrator, and when i close it and re-open i'd like to resume the same session I was on previously.

opencode -c just opens globally the last session

and i know there's opencode -s <sessionId> but it requires me to somehow screen scrape and get that session id back

I'm proposing

opencode new -s <sessionId> and that sessionId being assigned to that instance for me to opencode -s <sessionId> and come back to it

this also works with opencode new -s "feature-dashboard" and let me come back to working on that feature on a specific project

(maybe the -s should be .git scoped)

Originally created by @quuu on GitHub (Jan 7, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request I have a multi-opencode orchestrator, and when i close it and re-open i'd like to resume the same session I was on previously. `opencode -c` just opens globally the last session and i know there's `opencode -s <sessionId>` but it requires me to somehow screen scrape and get that session id back I'm proposing `opencode new -s <sessionId>` and that sessionId being assigned to that instance for me to `opencode -s <sessionId>` and come back to it this also works with `opencode new -s "feature-dashboard"` and let me come back to working on that feature on a specific project (maybe the -s should be .git scoped)
yindo added the discussion label 2026-02-16 17:43:40 -05:00
yindo closed this issue 2026-02-16 17:43:40 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 7, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #5381: [FEATURE]:opencode run --session [set new session id] - Similar request to set custom session IDs for programmatic session management
  • #3434: Feature request: Start and continue a session with opencode run -s - Proposes similar behavior to create sessions if they don't exist with a custom ID
  • #7265: [FEATURE]: Allow independent plan/build per session - Related to multi-session orchestration

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 7, 2026): This issue might be a duplicate of existing issues. Please check: - #5381: [FEATURE]:opencode run --session [set new session id] - Similar request to set custom session IDs for programmatic session management - #3434: Feature request: Start and continue a session with opencode run -s - Proposes similar behavior to create sessions if they don't exist with a custom ID - #7265: [FEATURE]: Allow independent plan/build per session - Related to multi-session orchestration Feel free to ignore if none of these address your specific case.
Author
Owner

@quuu commented on GitHub (Jan 8, 2026):

duplicate

@quuu commented on GitHub (Jan 8, 2026): duplicate
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4398