fix: return from settings to active task - #279
Merged
Merged
Conversation
Devin-AXIS
marked this pull request as ready for review
August 10, 2026 18:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
Opening Settings already stored the current
sessionIdin navigation state. The Settings shell read that ID but dropped it from the Back to app route, navigating to/workspace/:workspaceId/sessioninstead of/workspace/:workspaceId/session/:sessionId.With no selected task in the route, the session page remained on the Preparing workspace / Pulling in the latest messages state.
User impact
Users can open Settings from an active task and return to the same conversation immediately. No settings behavior, session content, Design, Video, templates, plugins, or OpenCode runtime behavior changes.
Validation
git diff --check: passed.ses_01344ea02ffevOlrtoDfnPMlau, clicked Back to app, returned to the same/session/:sessionIdURL, rendered the existing transcript, and confirmed both loading messages were absent.No video or Fraimz artifact was captured because this checkout does not include a loadable Fraimz skill; the exact user flow was exercised against the running Electron client via CDP.