trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- A test pins the local terminal's stash: `p` pops, `d` drops only after a confirm, and cancelling keeps the entry
- A test pins deleting a branch in the local terminal: `d` refuses unmerged work, `D` says it will lose it, both ask first
- A test pins discarding a change in the local terminal: `d` asks first, and cancelling keeps the file byte for byte
- GET a repository's decisions pages: `limit` (1–100, default 30) and a `next_cursor`, trevato/forge's first page under 40 KB
- A test pins granting and revoking egress through MCP: a site admin only, never an agent
- A test pins reading an app's egress grants through MCP: an admin-scope token only, and the same answer as the API
- A test pins MCP `feed_chips`: switching a chip off hides it from `feed` and `asks`, and bad input changes nothing
- Holding a file from any page goes through one form handler that takes where to return, and refuses an unknown or unreadable repository in the same words
- One query answers the repositories a person administers, with no counts and no loop per repository
- GET a repository's branches compares only the branches it returns: `git` under 60 ms for a 30-branch page of trevato/forge
- GET /api/v1/search greps code within the same budget as the /search page
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:2tt6qpm3j9 is past its budget: trevato/forge: "flow panel cache > an agent never sees an admin's figures" failed on 3 pulls in the last hour — the lan…
- /.well-known/mcp.json names the commit it runs, so an agent on a preview knows which build it is talking to
- MCP `forks`, in its own tool file: a repository's forks the caller may see, each with how far ahead and behind
- MCP `org_create`: make an organization, with the same rules as POST /api/v1/orgs
- MCP `agents`: list the forge's agents the caller may see, with what each is for
- A repository's prompt routes leave api.ts for src/http/api/prompts.ts
- A repository's webhook routes leave api.ts for src/http/api/hooks.ts
- A test pins waking a resting Claude account from Settings → Subscriptions, a forge admin's only
- A test pins an app's custom domains in Settings: add, check, delete, a repository admin's only
- A test pins verifying a cloud account from Settings: a forge admin only, and a failing provider explained in words
- A test pins resending the email-verification link: throttled, capped, and honest when already verified
- A test pins rotating, renaming and removing a cloud account from Settings: a forge admin only, never echoing the key
new above
offline