AI Summaries

Local Claude

Use your Claude subscription — no API key needed.

Requirements

Claude Code CLI installed (claude available in your PATH)
Active Claude Pro, Team, or Enterprise subscription

If you have Claude Code installed and running, you already meet both requirements. Run claude --version to verify.

Setup

Run the init wizard and choose Local Claude:

bash

larkx init

? AI summaries — how do you want to generate them?
    Skip  (recommended — summaries cost extra tokens)
  ❯ Local Claude  (uses your Claude subscription — no key needed)
    Anthropic API key

larkx checks that claude is in your PATH. If found, it saves { "ai": { "provider": "local-claude" } } to .larkx/config.json.

Generate summaries

bash

larkx index --ai

larkx spawns claude -p once per unsummarized file. Each call runs in about 3–10 seconds. Progress is shown as Summarizing files... N/total.

Each file summary is a separate claude subprocess call. For large projects this can take several minutes. Summaries are cached — interrupted runs pick up where they left off.

Verify

bash

# Check config
cat .larkx/config.json

# View cached summaries
cat .larkx/summaries.json

# See summaries in MCP output
larkx context --level 4