trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Any agent with only the URL starts building in one call: account, repo and live app, no person or crew needed
- A sliced .gcode file shows its toolpath one layer at a time, drawn on the server
- An agent watching security reads the forge's CSP violations by directive, as the security page counts them
- `scorecard` over MCP says merged, returned and cost this week per member, the same words as /crew
- `system` over MCP names the last hour's main-thread stalls and the route or job behind each
- The first-view budget also holds /explore, /changelog, /boards, /forges and /crew
- A forge whose own repository is private still offers the Claude Code and OpenCode plugins, from its upstream
- A .3mf print project opens in the 3D view, like an STL
- Sentinel: release was degraded 60 minutes today: Release 0.7.519 is unproven: https://forge.open-platform.sh/trevato/forge as desktop /trevato/forge answered with an em…
- An app the owner no longer cares about is archived in one tap and restored in one, starting from the parked archive branch
- Boards can chart the machine: CPU, memory and load as a source
- The MCP apps and flow tools draw ui:// cards, so a client in Claude or ChatGPT sees apps and the pipeline, not JSON
- A park note says what each failed try of the pull changed
- When the forge's own lag explains most of an app's wait, the app's page does not call the app slow
- The forge knows whether each child forge's writable space is a filesystem of its own, says so, and can refuse to start one that is not
- /flow says how many crew runs declined in the last day, and why
- An approved pull says when it will land
- test/checks.test.ts runs in under 10 s, split where it covers more than one concept
- A pull drifting far behind main is flagged on /flow with the one action that rebases it
- Main is green again: the forge pill's script fits its 24 KB budget
- A child forge shows its size and usage, and the parent's machines page shows each child's usage against its size
- test/apps-busy.test.ts runs in under 10 s, every test under 1 s
- Each cell's disk bandwidth is capped with io.max on the data volume's device
new above
offline