trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The terminal's deploys screen probes a running app with `p`: every door tried as nobody, a user and an admin, read-only, as MCP `probe` does
- The terminal's People screen marks a person's email verified with `v` and a confirm, as MCP `account_verify` does
- The terminal's Flow dialog lists each repository's last merge-queue gates with their verdict and first failing test, as MCP `queue_gates` does
- The terminal's failure domains screen runs a restore drill on the newest snapshot with `d` and a confirm, as MCP `restore_drill` does
- The terminal's "What I can do" screen says when your email is unverified, and `v` sends a new verification email, as MCP `email_verify` does
- The terminal's asked screen narrows to unshipped, flagged or all with `s`, and flips oldest/newest with `o`, as MCP `asked` does
- The terminal's forks screen says where this repository stands against what it follows, and what the crew is doing about it, as MCP `following` does
- The terminal's one-commit view says the commit's check: green, red or not run, and why, as MCP `commits` with `oid` does
- The terminal's run screen says a word to a running crew run with `s`, as the run page's steer box and MCP `steer` do
- The terminal's issue screen lets a writer say an issue may go ahead when what it waited for closed as dropped or split, as MCP `confirm_wait` does
- The terminal's runs screen runs a failed or cancelled agent run again with `a` and a confirm, as the run page's requeue does
- `enter` on a run in the terminal opens its log, the last 200 lines, refreshing while it runs, as MCP `run_log` does
- The terminal's repository screen makes an app you can see your own with `Y`, planned first, as MCP `make_it_yours` does
- The terminal's System screen says how the forge is: the version and commit it runs, draining or not, the rollout and its incidents, as MCP `health` does
- The terminal says who may sign up — open, invite or closed — and a forge admin changes it after a plan, as MCP `signup` does
- MCP `flags` answers what `readFlags` answers, for a forge admin
- The terminal's usage screen says what the crew's tokens bought: dollars, runs, changes landed and cost per change, as MCP `returns` does
- The terminal lists a repository's webhooks, adds one and removes one, never showing a secret, as MCP `hooks` does
- The terminal's resilience screen seals or forgets the off-box snapshot mirror, never showing a key, as MCP `mirror_set` does
- The terminal's repository screen shows the app's vision: its purpose and the pillars in order, from docs/VISION.md, as MCP `vision` does
- The terminal's resilience screen sets or forgets where snapshots go, never showing a key, as MCP `backups_destination` does
new above
offline