You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs/cli.md tool ID list out of sync with src/core/config.ts #1213
The Supported tool IDs (--tools) line in docs/cli.md is missing vibe, which is a valid, available tool registered in src/core/config.ts.
This is a pre-existing gap — vibe was already absent before PR #1211 (which only added atomcode to the existing list). The companion doc docs/supported-tools.md already lists vibe correctly, so only docs/cli.md needs updating.
Missing entry
Tool ID
Present in config.ts
Present in docs/cli.md
Present in docs/supported-tools.md
vibe
✅
❌
✅
Note:agents also appears in src/core/config.ts but is not in the docs/cli.md list — please verify whether it is a user-facing tool ID or an internal/group entry and update docs accordingly if needed.
Fix
In docs/cli.md, line 110, add vibe in alphabetical order between trae and windsurf:
Closing as fixed. docs/cli.md was brought back in sync in the stores rework (#1190, commit a0decbe), including vibe.
Verified exact parity against src/core/config.ts on current main: all 34 available tool IDs match in both directions, nothing missing either way. On the agents question: it is marked available: false in config (internal entry), so its absence from the user-facing list is correct rather than lucky.
Activity
docs: close recurring gaps (existing projects, editing changes, unins…
docs: comprehensive overhaul — discoverability, explore-first, and cl…
docs: comprehensive overhaul — discoverability, explore-first, and cl…
clay-good commentedon Jul 22, 2026
Closing as fixed.
docs/cli.mdwas brought back in sync in the stores rework (#1190, commit a0decbe), includingvibe.Verified exact parity against
src/core/config.tson current main: all 34 available tool IDs match in both directions, nothing missing either way. On theagentsquestion: it is markedavailable: falsein config (internal entry), so its absence from the user-facing list is correct rather than lucky.