cronekorkn/dotfiles
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(agents): say when ccc comes before grep

Browse source 
Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com>
This commit is contained in:
mwiegand 2026-10-09 21:48:54 +02:00
parent 4940a7066d
commit f5878f1f06
No known key found for this signature in database
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
agents/AGENTS.md
View file

@ -133,12 +133,13 @@ on your own. Command forms, flags, dataset sharing and failure modes are in the
checkout stays first choice when it exists. Never call
`ask_codebase` on your own — it spawns a nested server-side agent
(minutes per call, shared vLLM); use it only when explicitly asked.
- **`ccc` for semantic code search.** Repos containing a `.cocoindex_code/`
directory are indexed by `ccc`. Reach for it on conceptual questions ("where
is X used / what handles Z"), where a keyword grep would miss indirect usage:
`ccc search '<concept>'` from the project root. It is embeddings only: exact
strings (UUIDs, ticket IDs, error messages) stay with `grep`/`rg`. Details and
gotchas in the `ccc` skill.
- **`ccc` before `grep` for concept questions.** In a repo with a
`.cocoindex_code/` directory, a question about a concept ("where is X
handled", "what talks to Y", "which code does Z") starts with
`ccc search '<concept>'` from the project root, then `grep` verifies what it
found. An exact string (UUID, ticket ID, error message, identifier) goes
straight to `grep`/`rg`: ccc is embeddings only and will not find it. Gotchas
in the `ccc` skill.
- **`ccc index` / `ccc init` are read-safe maintenance.** They only write to the
gitignored `.cocoindex_code/` directory, never to source. Run them without
confirmation prompts; treat like `grep` for permission purposes.