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

未关闭
  • 哪里不对？
#1,070 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
node.js, typescript
领域
cli

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
没有语言数据
星标
4.2k
派生
377
平均合并
1 天 17 分钟
30 天内合并 PR
7

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

CommandCodeAI/command-code 的其他 Issue

查看 CommandCodeAI/command-code 的全部 Issue

相似的 Issue

更多 CLI Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。