trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Stop a shell, or stop all idle ones, from your account and through MCP
- /packs reads pack repos the owner marks, and packs/ leaves the forge's source tree
- A real Rust hello-world app builds with cargo and answers / in a test
- A pull opens on its verdict: can it land, what holds it, then the change
- An origin can be connected read-only, and every write-through path refuses it
- Disk health rules: a spec catalog and alerts only on what the drive itself reports
- /talk?about= names its subject: one line above the composer, only for what the viewer can read
- An app whose / answers an error is not boot ok
- A from-app issue is assigned on arrival, and the flow alarm fires when one waits
- A machine shell opens to a greeting, a prompt with the repository and branch, and history that persists
- Your account lists the machine shells you hold, live and recent, and the sessions MCP tool lists them too
- A build that hits its CPU, memory or time limit says which on the app page in one line
- A pack app's source can be a forge repo, and deploying it forks from the forge with lineage
- After every release a cell child cannot wake for ten minutes: the boot opens every hosted child and fills FORGE_CHILD_AWAKE_MAX ("the forge is full")
- Knobs: one panel on the crew page with five plain dials, each showing its live effect, editable in place
- New app copies a template repository's tip (readable by the caller, capped, no symlinks), with a door to name it
- A crew run's sandbox refuses writes outside its worktree and hosts past the egress allowlist, each a test
- Knobs: one panel on the crew page with five plain dials, each showing its live effect, editable in place
- A refused host is said out loud on the app page, and allowing it is one switch
new above
offline