Track agent-catalog support backlog

[Drswith]

Summary

Track unsupported agent-support candidates for the Quantex catalog and keep backlog triage aligned with the support-matrix policy.

Why

We have a growing set of tools that may overlap with Quantex's lifecycle scope, but they are not all the same kind of product. This issue should distinguish:

• already implemented support
• active implementation work
• CLI-first candidates that fit Quantex mainline evaluation
• tools that have a CLI but are not primarily lifecycle agent CLIs
• tools that are explicitly excluded or still too ambiguous to action

Issue policy

• Keep this issue as the top-level tracking issue for agent-catalog expansion.
• Create a dedicated per-agent issue only when a candidate is ready for actionable implementation work.
• Use OpenSpec alongside the per-agent issue whenever the catalog contract or product-facing behavior changes.

Recently delivered

• Add Kimi Code CLI to the agent catalog #135
• Add Crush to the agent catalog #136
• feat(agents): add Goose agent support #140
• feat(agents): add ForgeCode agent support #144
• feat(agents): add Kiro CLI support #139
• feat(agents): add Amp agent support #145
• feat(agents): batch agent catalog support additions #153
• feat(agents): batch terminal agent support additions #156
• feat(agents): add deepseek tui support #170

Candidate backlog: CLI-first

These are the best-fit candidates for Quantex's mainline lifecycle-CLI scope.

• adal
• auggie
• amp
• command-code
• codebuddy
• deepseek
• forgecode
• iflow-cli
• junie
• kiro-cli
• mistral-vibe
• neovate

Candidate backlog: Has CLI but not clearly CLI-first

These products expose a CLI, but the upstream product is broader than a standalone lifecycle agent CLI. They may still be worth supporting, but they should be triaged more carefully.

• bob
• cortex
• deepagents
• devin
• dexto
• goose
• openclaw
• openhands
• pochi

Needs clarification before action

These names are too ambiguous or the upstream product identity is not yet clean enough for a per-agent implementation issue.

• autohand
• kode
• universal

Not a standalone Quantex-style lifecycle agent CLI

Keep these visible so we do not repeatedly re-triage them as if they were straightforward CLI candidates.

• aider-desk: desktop / GUI layer rather than a standalone lifecycle agent CLI
• antigravity: IDE / agent platform rather than a clear CLI-first tool
• replit: agent product exists, but not as a clear standalone lifecycle CLI

Excluded for now

• tabnine-cli: CLI surface does not fit Quantex's lifecycle-management scope
• warp: terminal product rather than a Quantex-style lifecycle agent CLI
• zencoder: CLI is bundled with the vendor GUI install and lacks an independent installation path

Done when

• Every unsupported CLI under active implementation has its own dedicated issue.
• The candidate list stays aligned with the support matrix and active OpenSpec changes.
• Non-CLI or non-mainline candidates remain clearly labeled so implementation work starts from the right subset.
• Excluded tools remain documented with a short rationale.