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 lists an app's variables, sets one and unsets one, never showing a value, as MCP `app_env` does
- The terminal's People screen suspends or unsuspends an account with `s` and a confirm, as MCP `account_suspend` does
- MCP `app_notes`: an app's admin lists the notes sent from its forge button, hides one, bans or unbans its sender
- The terminal's issue screen edits an issue's title and body with `e`, as the page does
- The terminal lists a repository's waiting reports from outside and accepts or dismisses each, as the page does
- The terminal's pull screen holds a pull with `h` and a reason, and lets it go with `h` again, as MCP `hold` does
- The terminal's About screen shows whether outsiders may direct the crew, and `o` turns it on or off after a plan, as MCP `outsiders` does
- The terminal lists the crew's Claude subscriptions, wakes a resting one and sets its budget, as MCP `subscriptions` does
- The terminal's limbs screen watches or stops watching a milestone with `w`, as MCP `watch` does
- A test pins what the forge CLI prints: columns line up with wide characters, and piped output carries no colour
- MCP `merge`: a person lands a pull from any MCP client, as the pull page's Merge button does
- A test fails when an MCP tool in the index is missing from docs/MCP.md
- grepRepos answers at the code budget: the first batch's hits always kept, later batches cut off, abandoned greps still holding their slots
- The terminal's deploys screen redeploys or stops production with a key and a confirm, as MCP `app_deploy` does
- MCP `pins`: list, pin and unpin the caller's pinned repositories, with the same rules as the API
- The terminal's issue screen says what an issue waits for, and `w` adds or removes a wait, as MCP `wait_for` does
- The terminal lists your SSH keys, adds one and removes one with a confirm, as MCP `ssh_keys` does
- The terminal lists where you are signed in and ends one session with a confirm, as MCP `sessions` does
- The terminal lists a forge admin's sealed secrets by name and sets or removes one, never showing a value
- Every repository admin sees the Held files card on /boards, with the hold form, and only the holds of repositories they administer
- The terminal's take-back is tested on a conflict
- The terminal's runs list cancels a queued or running crew run with `x` and a confirm, as the run page does
- GET and POST /api/v1/repos/:owner/:name/app/notes: an app's admin lists the forge button's notes, hides one, bans or unbans its sender
- POST /api/v1/admin/releases/:sha/rollback plans, then rolls the forge back to a kept release, with the releases page's rules
- MCP `asks_act` takes back a mute: `listen` brings a muted repository's asks back, as /asks/listen does
new above
offline