Skip to main content

Documentation Index

Fetch the complete documentation index at: https://recipe.uselettuce.dev/llms.txt

Use this file to discover all available pages before exploring further.

Five minutes from zero to your coding agent calling lettuce — no CLI, no local setup.

​
1. Sign up

Create an account at uselettuce.dev/signup with email + password. The first person to sign in owns a new account; invite teammates later from the Team page.

​
2. Generate an API key

API keys (cwz_…) are what your coding agents present to lettuce — one per agent / machine / teammate is fine.
1

Open the API keys page

Go to uselettuce.dev/keys.
2

Click New key

Give it a recognisable name — e.g. claude-code-macbook or cursor-work-laptop.
3

Copy the key

The full cwz_… value is shown once, right after you create it. Copy it into your password manager now — you cannot retrieve it later.
Keys are stored hashed. A lost key cannot be recovered — revoke it from the same page and create a new one.

​
3. Add a repo

Open uselettuce.dev/repos, click Add repo, give it a name and a git URL. 
Name:   my-repo
Git URL: https://github.com/you/repo.git
Status moves pending → ready — usually within a minute. After that, the repo stays current automatically when you push.
Public repos only for now. Private-repo support is on the roadmap.

​
4. Connect your agent

Pick the snippet for the agent you use. All point at the same endpoint, https://uselettuce.dev/mcp, with your cwz_… key in the Authorization header.

​
Claude Code

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

​
Cursor

Save to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally): 
{
  "mcpServers": {
    "lettuce": {
      "url": "https://uselettuce.dev/mcp",
      "headers": { "Authorization": "Bearer cwz_<your-key>" }
    }
  }
}
Full per-agent details (VS Code, Windsurf, Cline, mcp-remote) on the Connect your agent page.

​
5. Tell the agent to use it

Agents won’t reach for a new tool unprompted. Drop this into the repo’s CLAUDE.md (or your agent’s equivalent system prompt): 
For navigation, prefer lettuce MCP tools over grep/Read:
understand → locate → callers/callees → read_snippet.
Only fall back to grep when lettuce returns nothing.

Always pass the `repo` arg — the name of the repo on lettuce.
The exact location per agent (CLAUDE.md, .cursor/rules, .github/copilot-instructions.md, Windsurf rules, Cline custom instructions, …) is on the Agent instructions page. Ask: “Who calls process_payment, and what would break if I rename it?” — your agent should now call a lettuce tool to answer it.