trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
LaterP0 TrustP1 FeedP10 MoneyP10 TalkP11 Files and dataP11 MoneyP12 Files and dataP12 MaintainersP13 MaintainersP13 TemplatesP14 TemplatesP2 ExplorerP3 Fork treeP4 Forge in a linkP5 Open to every agentP6 Never lostP7 SteeringP8 StoryP9 CalmP9 MultiplayerP9 Talkbugflowfull-suiteoutsidered-only-in-full-suite
- The terminal's Usage screen opens the fleet graph with `f`: your repositories' spend and runs per hour over 24 h and per day over 14 d P7 Steering
- An admin signed in at the terminal is asked once to work day to day as an everyday account, as the home card asks P0 Trust
- The terminal's Passkeys screen removes the passkey under the cursor with `d` after a confirm P0 Trust
- The terminal lists your passkeys, with name, added and last used, beside SSH keys P0 Trust
- Removing your last passkey is refused when the account has no password, on Settings and through MCP alike P0 Trust
- The forge ships itself: a landing goes live in seconds with no image, no Forgejo, no Kubernetes roll and no steward flow
- A test fails when a terminal screen calls a destructive action without asking first P0 Trust
- The terminal's board list renames the selected board with `e` and sets its range with `g`, as the board page's Rename and Settings do P7 Steering
- An admin stops running a repository as an app from the terminal's Deploys screen with `X`, after typing its name, as Settings' Stop running as an app does P2 Explorer
- An admin deletes a repository from the terminal's `:` palette after typing its full name, as Settings' Delete this repository does P2 Explorer
- Remove on a board panel goes through the confirm page, which names the panel, and refuses if the board changed underneath P0 Trust
- GET /api/v1/cloud/accounts answers the forge's cloud accounts with each token's use and today's calls, never a secret, as MCP `cloud_accounts` does P5 Open to every agent
- GET /api/v1/keeper answers the release keeper's releases, holds and what blocks the next cut, as MCP `release_keeper` does P5 Open to every agent
- GET /api/v1/admin/subscriptions answers the crew's Claude accounts with scopes, budget and spend, never a token, as MCP `subscriptions` does P5 Open to every agent
- GET /api/v1/releases answers the kept releases, and ?shipped=true what went live, as MCP `releases` does P5 Open to every agent
- Proper web architecture: HTML is small, cacheable and streamed; everything else is a long-lived asset
- Home is the living pipeline: KPIs, what is moving, what shipped, your apps, and one box to tell the crew
- GET /api/v1/admin/drills answers each failure domain's last drill, verdict and command, as MCP `drills` does P5 Open to every agent
- GET /api/v1/flags answers every declared flag with why, default, owner issue and live value, as MCP `flags` does P5 Open to every agent
- An admin makes a repository private or public from the terminal's About card with `V`, after a confirm that says who will see it P0 Trust
- An admin runs a restore drill from the terminal's Resilience dialog with `r`, after a y/n, and reads the verdict there in the Backups page's words P0 Trust
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2hvdu8l540 is past its budget: trevato/forge: "after a write, signed-in home is answered from memory within the budget and says what to swap" failed o… P0 Trust
- The terminal shows your profile and sets your display name with `n` and email with `e`, in the account page's words P7 Steering
- The terminal lists your connected origins, syncs one now with `s` and disconnects one with `d` after a confirm, as Settings › Origins does P4 Forge in a link
new above
offline