feat(providers): add Cursor, MiniMax Code, Devin and Antigravity agents

[BIackFIame]

Goal

Add Cursor, MiniMax Code, Devin and Antigravity as first-class agents, on top of the CLI detection from #52.

Behavior

• Provider CLI resolution uses declarative command definitions (command names plus known install directories) instead of assuming the executable matches the provider id. Existing providers resolve exactly as before.
• MiniMax Code resolves as mcode and Antigravity as agy. Cursor prefers cursor-agent. A generic agent counts as Cursor 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 its CLI documents them, a YOLO flag only where one exists, launcher entries with a settings migration, its provider mark, install link and session restore.
• Provider ids, labels and launcher order move to a dependency-free providerCatalog.ts that contracts.ts re-exports. The Even G2 companion imports only that module, so its production bundle stays inside its network whitelist, and its phone launcher lists the new agents.
• Lifecycle hooks are prepared only for providers that have a hook adapter, so the new agents never write Grok's shared hook configuration (~/.grok/hooks).
• MiniMax Code has no permission-bypass flag, so its YOLO profile launches the stock CLI and the danger text says so. Antigravity restores as a fresh session because there is no resumable id to persist.

Documentation

ADR: docs/adr/ADR-20260921-provider-cli-command-definitions.md. Architecture docs updated in all three languages.

Verification

• npm run typecheck passed. Full suite: 674/674; Even G2 companion tests (npm run test:even): 47/47.
• On macOS with Grok's agent on PATH, the registry resolved Cursor to cursor-agent and Grok to its own binary. MiniMax Code, Devin and Antigravity were not installed on the test machine, so their launch paths are covered by tests only.

Series

Each part is one commit on top of the previous one. Please merge them in order.

Part	PR	Scope	Lines
1	#63	Providers: Cursor, MiniMax Code, Devin, Antigravity	+579/−90
2	#64	API keys, API profiles, agent delegation (MCP)	+4275/−63
3	#65	Remote servers, placement, privacy tiers, accounts	+6620/−40
4	#66	Isolation: capsules, worktrees, containers	+5508/−839
5	#67	ACP, connection settings, remote containers	+6827/−563
6	#68	Project context and learning	+6148/−370
7	#69	Routing, reasoning effort, server preparation, sign-in	+3122/−467
8	#70	Open issues and safe fixes from open PRs	+306/−58

Compatibility with open upstream PRs

integration/stack-with-open-prs is this whole stack with #54–#62 merged on top and every conflict resolved. On that branch both TypeScript checks, 1492/1492 tests, npm run test:even (47/47) and electron-vite build pass.

• fix(even-g2): isolate transport keys per paired device #54, fix(even-g2): align local-network Settings card layout #56, fix(canvas): honor region bounds when snapping resize #57, fix(canvas): let sticky note editors scroll their own text #59, fix(plugins): prevent stale version writes during updates #60 merge cleanly.
• fix(settings): keep rejected writes out of live settings #58: conflicts in SettingsStore.ts. Keep this stack's store: it already serializes every write and publishes a value only after the disk write succeeds. fix(settings): keep rejected writes out of live settings #58's new tests pass against it unchanged.
• fix(window): restore state events after macOS Dock reopen #61: mechanical. registerIpc returns the window observer; keep both sides. This stack's IPC tests stub both window-state helpers, so they pass in either merge order.
• fix(even-g2): require explicit grant for answer capture #55:
  • TerminalManager.ts: keep this stack's launch structure. The answer-capture grant must also reach the prepared and measured-grid first start, because every real agent launch goes through that path.
  • hook-helper.mjs: keep this stack's 512 KiB input read and safe cut, and gate the answer on fix(even-g2): require explicit grant for answer capture #55's grant.
  • Fix and tests: 64ef294 (grant through prepared starts, feat(updates): add GitHub release updates across platforms #62 follow-ups) and c2dd726 (hook test under the grant).
• feat(updates): add GitHub release updates across platforms #62: whichever of this stack and feat(updates): add GitHub release updates across platforms #62 lands second needs the same commit:
  • The restore step in shutdownForUpdate must clear shuttingDown. Otherwise no session can start after a failed update; feat(updates): add GitHub release updates across platforms #62's own test fails without this.
  • Restore only live sessions, using the orphan-subagent rule.
  • Refuse to install while a server is being prepared or a capsule test runs.
  • Open About through SettingsLocation.

I will rebase this stack onto whichever of these lands first.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[howdeploy]

Integrated into main via #73. Your authored provider commit and @claude co-author trailer are preserved in the merge history. Thank you, @BIackFIame.