Engineering
Built like infrastructure, not like a prompt collection.
Five repositories, one system: a web command center, an edge gateway, core intelligence services, an MCP server and the fleet daemons that turn machines into workers.
Next.jsReact 19TypeScriptTailwindthree.jsCloudflare WorkersHonoKVR2FastAPIPostgreSQLpgvectorMCPClaude CodeCodextmuxsystemdlaunchdNext.jsReact 19TypeScriptTailwindthree.jsCloudflare WorkersHonoKVR2FastAPIPostgreSQLpgvectorMCPClaude CodeCodextmuxsystemdlaunchd
The stack
Frontend
Web
Next.js, React, TypeScript and Tailwind for the command center and this site, statically exported to Cloudflare Pages.
Edge
Edge gateway
Cloudflare Workers with Hono: auth, routing, rate limits, caching, KV sessions, R2 storage and the Telegram bot.
Backend
Core services
Python and FastAPI for projects, memory, retrieval, orchestration, briefs, analytics and the job queue.
Storage
Data
PostgreSQL with pgvector for project state, embeddings, compiled Brain pages, telemetry and usage history.
MCP
Agent interface
An MCP server with 100+ tools for Claude Code, Codex and Claude Desktop, which is how agents plan, dispatch and remember.
Compute
Fleet daemons
Worker and session daemons on Linux and macOS that claim jobs, run agents in tmux, send heartbeats and report outcomes.
Principles
Model-agnostic
No single provider is the architecture. Claude and Codex share one lifecycle, and swapping a model is a routing change.
Durable state
Sprints, tasks and handoffs outlive sessions, machines and interfaces. Nothing important lives in a terminal.
Conservative autonomy
Reversible work proceeds. Judgment calls escalate, and destructive actions always ask.
Evidence before confidence
Tests, verify passes and telemetry decide what’s done, not an agent’s claim.