Prove cockpit backend selection stays explicit#501
Merged
Conversation
The parser and resolver already support tmux, kitty, and auto backend choices. This change locks the operator-facing gx cockpit surfaces so future cockpit work cannot quietly collapse explicit tmux, Kitty preference, auto fallback, or invalid-backend errors. Constraint: Existing gx cockpit without --backend must remain on the tmux path. Rejected: Switch the default backend to auto | that would change existing gx cockpit behavior without an explicit flag. Confidence: high Scope-risk: narrow Directive: Keep explicit tmux and auto fallback coverage when changing cockpit backend resolution. Tested: node --test test/cockpit-terminal-backend.test.js test/cockpit-command.test.js Tested: openspec validate --specs
NagyVikt
deleted the
agent/codex/cockpit-backend-selection-cli-2026-04-30-14-10
branch
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
1 participant
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.
Automated by gx branch finish (PR flow).