It builds, tests, and ships — on its own
Your AI dev team
doesn't sleep.
Forge runs a team of specialized agents that plan, build, test, review, and ship on their own, around the clock. You drop the work and answer the questions; they keep the quality up.
Free & open source. One binary, no SaaS — bring your own keys.
forge serve web UI + CLI · same daemon, your box
- 7
- specialized roles
- 24/7
- works unattended
- 1
- binary, zero deps
- 0
- SaaS bills
// it holds the bar
It writes the code —
and keeps the bar high.
The coder ships features, but never grades its own homework. The tester writes the tests, reviews every change, and holds it to the standard. The refactorer keeps paying down debt so quality doesn't drift. Work moves forward around the clock — and nothing substandard lands on one agent's say-so.
- → Separation of duties — the coder never touches its own tests.
- → Every change is tested and reviewed before it lands — no regressions slip through.
- → Continuous cleanup keeps quality from drifting while you sleep.
// in one binary
Everything the team
needs, in one binary.
- 01
Runs around the clock
Each role works on its own cadence, unattended — no cron to babysit, no chat window to sit in.
- 02
Holds the bar
The tester writes the tests, reviews every change, and keeps it up to standard. The coder never grades its own homework.
- 03
Cleans up after itself
The refactorer makes regular passes on tech debt, so the codebase doesn't rot underneath you.
- 04
Schema-safe state
Agents update state through the CLI, never raw JSON. Nothing corrupts state.json.
- 05
Web UI + terminals
A Tokyo Night dashboard, live runs, and built-in ttyd terminals in the browser.
- 06
Your keys, your box
Bring your own Claude or opencode key. Your code never leaves the machine you run it on.
// you're the PO
You're the product owner.
The team does the rest.
- 1
Drop the work.
Add requirements, drop files in the inbox, create tasks. That's your whole job.
- 2
The team self-organizes.
Lead plans and assigns. Coder builds, tester checks, docs writes — each on its own cadence.
- 3
It ships.
Deliverables land in docs/output. You review, answer questions, repeat.
// in the loop, not on call
Stay in control without
babysitting it.
The team asks when it's blocked — questions queue up in a Q&A you answer
from the CLI or the web. You message the team, get in-app notifications, and
Telegram pings on your phone. Drop files in an inbox; deliverables come back
in docs/output.
- › Questions queue
- › Telegram pings
- › Messages & notifications
- › Inbox → outbox
// one binary you own
One binary.
Your machine. Your keys.
Forge is a single Go binary with the UI and prompts embedded.
forge install writes a TOML config and a systemd service. No Docker,
no database, no SaaS. Bring your own Claude or opencode key — your code never
leaves the box.
- single binary
- go:embed assets
- flat-file state
- one TOML
- systemd
// the roster
Meet the team.
Seven roles, each with a lane and a clock. Same accent colors as the app.
- lead every 15m
Always on. Plans, talks to you, orchestrates, owns memory.
- coder every 5m
Implements features. Never touches tests.
- tester every 30m
Writes tests, reviews code, finds the bugs.
- devops every 60m
CI/CD, Docker, infrastructure.
- researcher every 60m
Spikes, investigations, unknowns.
- docs every 60m
Keeps the docs honest.
- refactorer every 120m
Audits tech debt, leaves it cleaner.
Spin up your team
tonight.
It's one binary and one command. A dev team that never sleeps — and never asks for equity. Free, open source, yours.