Integrate reviewed DEV branch (#57, #60, #61, #63, #64) - #73
Merged
Merged
Conversation
Provider CLI resolution is driven by declarative command definitions instead of assuming the executable matches the provider id. MiniMax Code (`mcode`), Antigravity (`agy`) and Cursor resolve through the same registry, known install directories, recheck and install links that #52 introduced. Cursor prefers `cursor-agent`; a generic `agent` is accepted only when its real path is verified as Cursor, because Grok also installs an `agent` executable. Each new agent gets normal and resume launches where the CLI documents them, its YOLO flag only where one exists, launcher entries with a settings migration, its provider mark and session restore. MiniMax Code has no permission-bypass flag, so its YOLO profile launches the stock CLI and says so. Antigravity restores as a fresh session because it has no resumable id that CanvasTTY can persist. Provider ids, labels and launcher order live in a dependency-free `providerCatalog.ts` that `contracts.ts` re-exports, so the Even G2 companion bundle stays free of URLs outside its network whitelist; its phone launcher lists the new agents too. Lifecycle hooks are prepared only for providers that have a hook adapter, so the new agents never write Grok's shared hook configuration. ADR: docs/adr/ADR-20260921-provider-cli-command-definitions.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tion - Provider API keys are stored in the main process, encrypted with Electron safeStorage; the renderer only sees which keys exist. - API profiles name a model backend (protocol, HTTPS base URL, key reference, default model) with built-in presets. - Sessions carry role and parent metadata; restore drops orphaned subagents instead of resurrecting them. - Per-provider capability descriptors state what CanvasTTY can really do with each agent, and agent control (spawn, send, observe, result, cancel, children) works over ordinary terminal sessions. - An orchestration MCP surface rides the existing agent-bridge design: authenticated user-local socket, one-use bootstrap capabilities, scoping to the caller's own session subtree, and MCP injection for Claude, Codex, OpenCode, Kimi and Hermes. Only orchestrator sessions receive it; ordinary launches are unchanged. ADR: docs/adr/ADR-20260921-orchestration-mcp-rides-agent-bridge.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 24, 2026
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.
Included changes
Contributor attribution
main; its resulting window-state fix is present here.Co-Authored-Bytrailers from feat(providers): add Cursor, MiniMax Code, Devin and Antigravity agents #63 and feat(orchestration): API keys, API profiles and agent-to-agent delegation #64 are preserved.Merge with a merge commit, not squash, so the original authored commits and co-author trailers reach
mainwith their GitHub attribution.This branch starts from the merged #72 baseline. #62 and #65–#69 are outside this integration.
Verification
git diff --check origin/main...HEADpassed. Automated tests, typecheck, production build, and macOS Dock reopening were not run locally under the project's testing instructions; CI status is checked before merge.