Repository navigation
fix(native-chat-view-recovery): restore existing terminal chat toggle - #66
Merged
Merged
Conversation
added 3 commits
October 23, 2026 15:50
…ve-chat-view-recovery # Conflicts: # config/architecture-policies.jsonc # docs/issue/README.md
9 tasks done
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.
Eligible terminal tabs hid “Continue in Chat UI” even though the same-pane view toggle already worked through the terminal menu and keyboard. Restore both directions in the tab context menu, reuse the existing labels and platform shortcut, and keep the original terminal/session callback and capability gates.
Validation: 26 related tests; full typecheck; localization, architecture, fork registry/docs and changed-code quality gates passed. A normal AppImage completed terminal → chat → terminal locally and through a real SSH tunnel to an isolated Ubuntu host, with the same terminal handle, incarnation and shell PID and an unchanged transcript. The specified historical session was separately repaired through existing Orca hook metadata and displayed in the current web UI; its transcript size, mtime and SHA256 stayed identical. No provider resume or prompt was used for that repair. Requirements and evidence are in the feature journal.