体验：catalog/status 追踪 claude/codex/gemini，没有 grok
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
体验
all-cli catalog / status 追踪 AI 终端 claude、codex、gemini、opencode，没有 grok。README 的 AI terminals 列表同样漏掉 Grok Build。本机装了 grok 的人跑 all-cli catalog ai 或 all-cli status 看不到它。
这与 #54（doctor vs diagnose 帮助）、#55（--no-progress）、#56（catalog 无匹配无下一步）、#57（README Usage 不把 catalog 当发现入口）、#58（schema）不是同一件事。
证据
internal/tools/registry.go：toolNA("claude"…)…gemini… 无grok。internal/tools/metadata.go：无 grok purpose。README.md：AI terminals (claude, codex, openclaw, opencode, gemini, …)。- 用户路径：
all-cli catalog grok或all-cli catalog ai。
本地修复方向
把 grok 加成 ai 类 detect-only 条目（binary grok），README 列表补上。不要改 doctor/diagnose 帮助或 catalog 空匹配文案。
明确不在范围
- 不实现 grok context switch
- 不 push、不开 PR
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with internal/tools/registry.go and internal/tools/metadata.go to compare the existing AI terminal entries, then update README.md’s AI terminals list. Add Grok as a detect-only AI entry using the grok binary and its purpose metadata, without changing doctor/diagnose help or catalog no-match wording. Verify the catalog and status paths recognize an installed grok binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100