Skip to content

Track agent-catalog support backlog #134

Description

@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.
  • Treat src/agents/catalog/*.json, src/agents/catalog.schema.json, src/agents/generated/catalog-agents.ts, src/agents/generated/catalog-data.ts, and openspec/specs/agent-catalog/spec.md as the current supported-catalog source of truth; this issue is planning and triage only.
  • Keep completed candidates checked in their original triage bucket so the backlog checkboxes remain meaningful.

Recently delivered: catalog lifecycle enablers

Active catalog/enabler backlog

  • None currently open as of 2026-06-18. Keep new implementation-ready candidates as dedicated issues and link them here.

Candidate ledger: CLI-first

Checked entries have already been promoted into the supported catalog. Unchecked entries remain best-fit candidates for Quantex's mainline lifecycle-CLI scope.

Candidate ledger: Has CLI but not clearly CLI-first

These products expose a CLI, but the upstream product is broader than a standalone lifecycle agent CLI. Checked entries are supported; unchecked entries need more careful triage before implementation.

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. Checked entries were clarified and delivered.

Delivered outside the original candidate buckets

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
  • 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.
  • Catalog/enabler follow-ups are either delivered, moved into OpenSpec-backed implementation work, or intentionally dropped.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions