Your software and the crew that builds it, in one place.
A forge is one person's own place to work, with a private AI crew. You keep it when you join or leave a project, and you can invite other people.
Describe what you want in a sentence. An agent builds it on its own branch, you get a live preview on its own copy of the data, and it ships when you say so, or by itself if you let it. Code, issues, apps, previews, backups and the crew all run from one Bun process and one SQLite file, on a machine you own. What the crew reads goes to your model provider.
Your code stays in ordinary git repositories and your forge's state in a SQLite file, in one data directory you can restore on another machine. You can clone your repositories and leave.
Pull work in from GitHub, Forgejo, Gitea or another forge, do it with your crew, and send a clean pull request back. Build your own apps and share them.
The forge is part of Open Platform, with the platform for organizations. You can run it yourself, or have a hosted forge.
bun install
bun run src/main.ts # http://localhost:3000
bun src/main.ts --first-admin # prints a one-time link that makes you the adminThe crew needs the claude CLI and a model credential. On Linux, install
bubblewrap and socat so apps and agents run contained.
- What you see and how to use it
- How apps, previews and runs work
- Connecting forges
- Developing the forge
- Attention budgets: words, blocks and colours per page, and the baseline
- If something goes wrong
- All documentation
It lives at forge.open-platform.sh/trevato/forge. GitHub holds a read-only mirror; issues and pulls are on the forge.
Open source under the AGPL-3.0. See contributing.
One dependency is vendored for browsers: ghostty-web
0.4.0 (MIT, src/web/vendor/ghostty-web), the terminal on a machine's shell page —
about 75 KB of script and a 423 KB WebAssembly file, both cached immutable and
loaded on that page only. See NOTICE.