[ACP] Add Command Code to the ACP registry (2 files, PR ready)

Abierto
  • ¿Algo no está bien?
#1,070 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
node.js, typescript
Área
cli

Línea de trabajo

Read the ACP registry PR linked in the issue and inspect its two metadata files. Confirm the license URL, authorship, and --no-auto-update approach with the maintainers; the issue leaves these decisions open. Done means the registry entry is accepted with the agreed metadata and install command.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hi folks — thank you for cmd acp. I use Command Code from JetBrains Rider every day, and ACP is the reason that works.

I'd love to see Command Code in the ACP registry. I've opened a PR with the entry (registry#717) — two metadata files, no source changes — but it should carry your name, so I'd rather hand it over than push it through myself.

Why it matters: the registry is what makes an agent findable. In JetBrains Air, registry agents show up in the picker, install in one click, and update and uninstall cleanly. Agents outside it work only for people who already know the launch command and are willing to hand-edit JSON.

That was my experience: I had to discover cmd acp from your docs, hand-write ~/.jetbrains/acp.json (including an absolute node path, because a Dock-launched Rider doesn't inherit my shell PATH), and live with a generic icon and no version management — the custom-agent schema is just command/args/env, nothing more. None of that is a bug on your side; it's just friction your users each hit privately before giving up.

The entry, if useful:

{
  "id": "command-code",
  "name": "Command Code",
  "version": "1.88.0",
  "description": "Coding agent that continuously learns your coding taste, built for open models",
  "repository": "https://github.com/CommandCodeAI/command-code",
  "website": "https://commandcode.ai/docs/acp",
  "authors": ["Command Code (https://commandcode.ai)"],
  "license": "proprietary",
  "license_url": "https://commandcode.ai/terms",
  "icon": "./icon.svg",
  "distribution": { "npx": { "package": "[email protected]", "args": ["acp", "--no-auto-update"] } }
}

npx -y [email protected] acp --no-auto-update completes the ACP initialize handshake in a clean HOME (flag accepted before and after acp), and registry CI requires the pinned spec to match version — after that, versions re-sync from npm hourly.

Three things only you can settle: license_url (your repo has no LICENSE, so it points at commandcode.ai/terms — happy to switch); authorship (say the word and I'll close my PR so it lands under your name, or hand you the two files); and --no-auto-update (there because the CLI self-updates via npm install -g --prefix, which fights a client-managed install — an env switch like auggie's AUGMENT_DISABLE_AUTO_UPDATE would work equally well).

Either way, thanks for shipping ACP support — it's genuinely nice to use, and this is only about getting it in front of more people with less ceremony.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4.2k
Forks
377
Merge medio
1 d 17 min
PR fusionados (30 d)
7

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommandCodeAI/command-code

Todos los issues de CommandCodeAI/command-code

Issues similares

Más issues de CLI

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.