docs → tools → claude-code

Frenchie in Claude Code

Slash commands work out of the box. Results auto-save.

Install

From your project root:

npx @lab94/frenchie install --agent claude --api-key fr_your_key_here

Need help picking an agent? See the invocation matrix.

Invoke

Primary pattern:

/ocr TOR.pdf

Also works:

/transcribe meeting.mp3
/frenchie-status

Claude Code is the only Tier A agent that runs our bundled slash commands directly — the installer copies .claude/commands/ocr.md, .claude/commands/transcribe.md, and .claude/commands/frenchie-status.md into your project.

Example

You:

/ocr ./TOR.pdf

Agent:

Claude calls ocr_to_markdown with the file path. The stdio server writes .frenchie/TOR/result.md. The tool response is metadata only (savedTo, wordCount). Claude reads the file if you ask for content.

Known gotchas

Scope precedence when upgrading from 0.1.x

If Claude Code still uploads + curl-PUTs files after you re-install, a leftover HTTP entry at user or local scope is shadowing the new project stdio entry. Run claude mcp remove frenchie -s local (and -s user if needed), then re-run install --api-key.

Cross-reference: /docs/troubleshooting#http-shadow

Main Frenchie docs — MCP tools, credits, rate limits, full API
All agent guides — the full invocation matrix
Troubleshooting — symptom-first fixes for every error we've seen
Migration guide — upgrading from 0.1.x, 0.2.x, 0.3.0, or 0.3.1