Quickstart

Name:   my-repo
Git URL: https://github.com/you/repo.git

claude mcp add --transport http lettuce https://diet.uselettuce.dev/mcp \
  --header "Authorization: Bearer cwz_<your-key>"

{
  "mcpServers": {
    "lettuce": {
      "url": "https://diet.uselettuce.dev/mcp",
      "headers": { "Authorization": "Bearer cwz_<your-key>" }
    }
  }
}

# Codebase navigation — use the Lettuce MCP

This repo is indexed by Lettuce. For any "where is X / how does Y work /
who calls Z" question, use the Lettuce MCP instead of grepping.

1. Call `mcp__lettuce__understand(task='<the question>', repo='<repo>')`
   ONCE. It returns ranked candidate symbols with code, top caller/callee,
   docs hits, a `confidence` score, and a `next_step_hint`.

2. Branch on `next_step_hint.action`:
   - `answer_now`               → answer from the response. Don't grep,
                                  don't re-read "to verify" — the code
                                  returned is identical to what's on disk.
   - `answer_or_read_snippet`   → answer, unless you need one file fully —
                                  then call `mcp__lettuce__read_snippet` ONCE.
   - `read_snippet_then_answer` → call `read_snippet` ONCE on the top
                                  candidate, then answer.
   - `bail_to_grep`             → the graph missed; grep with the suggested
                                  `grep_terms`, then answer.

3. After at most 2 Lettuce calls (understand + at most one read_snippet),
   answer. Re-grepping or re-reading what `understand` already returned only
   adds cost, not correctness. If the graph genuinely missed it, say so
   rather than chasing with grep.