Skip to content

fix: return from settings to active task - #279

Merged
Devin-AXIS merged 1 commit into
mainfrom
agent/fix-settings-return-session
Aug 10, 2026
Merged

fix: return from settings to active task#279
Devin-AXIS merged 1 commit into
mainfrom
agent/fix-settings-return-session

Conversation

@Devin-AXIS

Copy link
Copy Markdown
Owner

Summary

  • Preserve the active task ID when leaving Settings.
  • Return to the exact task route instead of the workspace-level empty session route.
  • Add a focused regression assertion for the Settings return path.

Root cause

Opening Settings already stored the current sessionId in navigation state. The Settings shell read that ID but dropped it from the Back to app route, navigating to /workspace/:workspaceId/session instead 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

  • Focused Settings route test: 6 passed, 0 failed.
  • Full App tests: 709 passed, 0 failed.
  • App TypeScript check: passed.
  • Maintainability audit: 0 errors, 0 warnings.
  • git diff --check: passed.
  • Real Electron CDP flow: opened Settings from task ses_01344ea02ffevOlrtoDfnPMlau, clicked Back to app, returned to the same /session/:sessionId URL, 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.

@Devin-AXIS
Devin-AXIS marked this pull request as ready for review August 10, 2026 18:23
@Devin-AXIS
Devin-AXIS merged commit 32304fc into main Aug 10, 2026
1 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants