Principle: The fabric is the product. The tools are the asset; the model is a tenant. Decouple them so any agent, present or future, can call the same set. See PRINCIPLES.md.
We use Claude Code as the agent. Any MCP-capable agent works the same way — the pattern is what matters.
3.1 Install Claude Code
On the box:npm install -g @anthropic-ai/claude-code pulls the same binary. On a Windows machine you’d run irm https://claude.ai/install.ps1 | iex instead — but this build runs on your Linux box, so the curl form above is the one.)
It needs a paid Anthropic account (Pro, Max, or API credits on the Console) — the free Claude.ai plan doesn’t include Claude Code. This is the model subscription line from the essay’s cost breakdown; budget for it.
- Claude Code docs (overview, install, settings): https://code.claude.com/docs
- Anthropic plans and pricing: https://www.anthropic.com/pricing
- Get API credits / console: https://console.anthropic.com/
3.2 Point it at your gateway, not straight at Anthropic
So every call runs through the one endpoint you control (and shows up in the gateway’s logs). Set these on the box (add to~/.bashrc to persist):
- Claude Code settings & environment variables: https://code.claude.com/docs (see Settings)
3.3 Give it three tools over MCP
MCP (Model Context Protocol) is the open standard agents use to call tools. Start with a filesystem tool (so the agent can read/write your project and, next step, your vault) and GitHub. Copyagent/mcp.example.json to the location Claude Code reads, or use the CLI:
- Connect MCP servers (quickstart): https://code.claude.com/docs/en/mcp-quickstart
- MCP standard: https://modelcontextprotocol.io
- Reference servers (filesystem, git, etc.): https://github.com/modelcontextprotocol/servers
- Official GitHub MCP server: https://github.com/github/github-mcp-server