Frenchie in VS Code (GitHub Copilot)
Slash commands work once MCP is registered.
Install
From your project root:
npx @lab94/frenchie install --agent vscode --api-key fr_your_key_hereNeed help picking an agent? See the invocation matrix.
Invoke
Primary pattern:
/frenchie TOR.pdfCopilot discovers the frenchie MCP server from .vscode/mcp.json and registers a matching slash command. Invoke it from the Copilot chat panel.
Example
You:
/frenchie TOR.pdfAgent:
Copilot calls ocr_to_markdown with the file path, the server writes .frenchie/TOR/result.md, Copilot opens the file if needed.
Known gotchas
"--help hangs" on preflight (fixed in 0.3.0)
Copilot preflights the bundled stdio binary with npx @lab94/frenchie mcp --help before registering the server. Pre-0.3.0 the subcommand unconditionally booted the stdio server and waited for JSON-RPC, which Copilot read as a hang. 0.3.0 adds a --help / --version / --selftest short-circuit. Upgrade if you see "package fetch failed."
Cross-reference: /docs/troubleshooting#help-hangs
AWS STS errors are not ours
A Copilot preflight session surfaced UnrecognizedClientException: The security token included in the request is invalid and attributed it to our package. That error is almost always Copilot's own AWS-hosted backend (expired STS token), not a CodeArtifact or npm problem. Retry in a fresh Copilot session or run the install from a regular terminal to confirm.
Cross-reference: /docs/troubleshooting#aws-sts-error
More
- 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