Agent Tooling Compatibility
Last verified: 2026-05
Use this when: you need to choose which AI coding tool or adapter files a generated project should include.
Quick Answer
Do not generate every adapter. Pick the tools the user will actually use, keep the root instructions short, and point each tool back to AGENTS.md and agent_docs/.
Tool Picker
| Need | Good default | Files |
|---|---|---|
| Local agent coding and verification | Codex | AGENTS.md, .codex/config.toml, .agents/skills/ |
| Planning, skills, hooks, subagents | Claude Code | CLAUDE.md, .claude/skills/, .claude/agents/, .claude/settings.json |
| IDE workflow and background agents | Cursor | .cursor/rules/, .cursor/BUGBOT.md, .cursor/environment.json.example |
| VS Code and GitHub PR workflow | Copilot | .github/copilot-instructions.md, .github/instructions/, .github/prompts/ |
| Google agent-first workflow | Antigravity/Gemini legacy | GEMINI.md, .gemini/settings.json where supported |
| Local/private coding | Continue, Cline, Aider, OpenHands | Tool prompt plus local endpoint and approval rules |
| Prototype/front door | v0, Lovable, Bolt, Replit, other builders | Builder exit review before production |
Checklist
- [ ] Only selected tools get adapter files.
- [ ] Each adapter points to
AGENTS.md,agent_docs/, andREVIEW-CHECKLIST.md. - [ ] Tool permissions are ask-first for shell, write, network, MCP, production, billing, and destructive actions.
- [ ] Background agents use isolated branches/worktrees.
- [ ] Reviews and tests still run after agent output.
Example
If the user says "Cursor and Copilot," generate .cursor/rules/, .cursor/BUGBOT.md, .github/copilot-instructions.md, optional .github/instructions/, optional .github/prompts/, and skip Claude/Codex/Gemini files.
Links
- Claude Code changelog
- Cursor changelog
- GitHub Copilot cloud agent docs
- Google Gemini CLI to Antigravity CLI transition
September 2026 protocol update
Documentation checked 2026-09-05: the MCP 2026-07-28 release introduces a stateless core, authorization changes, and a formal extensions framework. Tasks and MCP Apps are extensions; protocol support alone does not establish that a client supports either. MCP Apps enables assistant-hosted interactive UI.
For every claimed combination record client/version, SDK/version, protocol revision, transport, required extensions, authentication flow, scenario, date, result, and evidence path. This repository has not run a live client/SDK interoperability matrix for the new revision. Earlier May entries remain historical guidance; verify the relevant combination before adopting it. See the assistant-app recipe and release evidence.