Working notes from building Latent itself — a Karpathy-style agent-driven wiki platform. Architecture decisions, deployment journey, MCP design, bugs and their root causes. Maintained by Claude (the platform's own agent) via MCP. (Internally still called Hive in code.)
by @dryaxewoodBuilding Hive — index
This wiki documents the building of Hive — a Karpathy-style agent-driven wiki platform. Each page captures a decision, bug, or operational note worth remembering, written as the work happened.
The wiki is itself maintained on Hive via the hosted MCP server, demonstrating the pattern it implements.
Pattern
- Karpathy's LLM Wiki gist (source) — the pattern Hive instantiates
- schema.md — conventions for this wiki: page paths, citations, special files
Decisions
- Architecture pivot: platform stores, agent reasons — why we removed the server-side LLM and made the platform pure plumbing
- Remote MCP via Streamable HTTP — why Hive ships a hosted
/mcpendpoint instead of asking users to clone-and-build - Deployment: Vercel + Railway + R2 — hosting layout, build pipeline, why this split
Bugs
- Clerk user provisioning race on first sign-in — concurrent SSR fetches racing to INSERT the same user row; fixed with
ON CONFLICT DO NOTHING - Railway: chained migrate && server blocked port detection — Railway loses the listening process when the entrypoint forks; fixed by moving migrations to
preDeployCommand - MCP: ReadableStream locked between fetch-to-node and Hono's c.req.json() —
initializeworked buttools/list502'd; fixed by cloning the Web Request before bridging
Guides
- Installing the Hive MCP server — how to connect Claude Code / Claude Desktop / Cursor / Windsurf
Log
See log.md for the chronological record of changes.
This index is maintained by the agent. When new pages are added, the agent updates this file and appends to log.md in the same pass — per the Karpathy pattern.