Fulcrum
Your repo, your work board, your agents — one local-first Agent OS.
A fulcrum is the pivot point of a lever — the supporting structure that turns small effort into large output. Same idea here: small commits land big outcomes through the agents you supervise.
Project management + agent orchestration + docs + memory + a CLI/TUI/Web triad,
all running on your machine. PGlite by default; swap in Postgres with one env
var. SaaS-ready schema from day one. Online features ship but stay dark behind
explicit feature flags until you opt in.
Quick Start · Three Surfaces · How it Works · User Manuals · Acknowledgements
Why Fulcrum
Coding agents are everywhere; the work around them is fragmented. Tickets in
Jira, docs in Notion, runs in a sandbox no one watches, memory in a markdown
file someone forgot to commit. Fulcrum collapses that into one process you
control:
- Local-first by default — your project, your DB, your machine. No telemetry leaves the box unless you flip a flag.
- Three surfaces, one model — Web, CLI, TUI all hit the same NestJS public API. Whatever you do in one is real in the others, immediately.
- Sandbox-first agent runs — agents run inside isolated worktrees + container images, not your dev shell. Powered by Matt Pocock's Sandcastle.
- OpenAI Symphony-compatible —
fulcrum doctor validates conformance to the openai/symphony orchestration spec; the work-board → run lifecycle implements its contract.
- No vendor lock-in — PGlite for dev, Postgres for prod via
FULCRUM_DATABASE_URL. Same schema both ways.
Quick Start
# 1. clone + install
git clone https://github.com/moabualruz/fulcrum
cd fulcrum
bun install
# 2. spin the stack (3 processes)
cd apps/server && bun run src/index.ts & # NestJS public API @ :3000
cd apps/web && FULCRUM_SERVER_URL=http://localhost:3000 bun run dev # SvelteKit web @ :5173
bun run apps/tui/src/index.ts # OpenTUI terminal
# 3. install the CLI globally (one binary)
bun run build && cp dist/fulcrum-darwin-arm64 ~/.local/bin/fulcrum
fulcrum doctor # confirms the stack is wired
Open http://localhost:5173/, pick your project, ship work.
Three Surfaces, One Brain
The same NestJS server backs every surface. The web is a pure invocation
layer — it never opens a database — and the TUI / CLI hit the same /api/v1/*
endpoints. Whatever a human can do, an agent can do.
Web
SvelteKit · :5173 | CLI
Bun-compiled · one binary | TUI
OpenTUI · keyboard-first |
 |  |  |
The Operate stage is identical across surfaces — same doctor, same MCP
inventory, same plugin registry:
Full per-surface guides + every screen captured against live data live in
docs/manuals/.
Tasks, Boards, and the Build Graph
The work spine — what your team is doing, who's doing it, and what's blocked.
Workspace kanban — /boards
Five-column board over canonical statuses (pending, in_progress, blocked, completed, cancelled) with every task in the workspace. Tabs swap into List, Table, Gantt, or Calendar views without leaving the page. New tasks are created inline per column.
Project board — /projects/<slug>/board
Same kanban, scoped to one project. The "manual task workbench" header summarizes Backlog / Unstarted / Started / Completed / Canceled so a PM can read status at a glance before drilling into cards.
