renderer at a site. NEVER use
`mcp__claude-in-chrome__*` tools — they are slow, unreliable, and not what this
project uses.
**Server / sidebar / extension internals:** before editing `browse/src/server.ts`,
`extension
139k24d agoReviewMountCreate a free account to mount
ruff format`
- Pre-commit hooks: `uv run pre-commit run --all-files`
**MCPServer Mode:**
The library can run as an MCPserver for integration with Claude Desktop:
```bash
Steady7 mentions in 2 weeks
1 project uses a version of this
120k5mo agoReviewMountCreate a free account to mount
JuliusBrusseePipes a download into a shellCLAUDE.md
mcp — the Caveman MCPserver (Go core + launcher, Apache-2.0)
A thin **stdio JSON-RPC** adapter exposing the compression [engine](../engine/CLAUDE.md) as
five MCP tools to any host (Claude Code
Steady7 mentions in 2 weeks
No other project uses it yet
115k7mo agoReviewMountCreate a free account to mount
accepted through the raw retry, and a compressed PAYG conversation without MCP recovery that streams (the server-side retrieve tool cannot ride a stream, so the conversation stays raw from
Steady7 mentions in 2 weeks
No other project uses it yet
115k7mo agoReviewMountCreate a free account to mount
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.