trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- GET /api/v1/user/next-steps answers a spawned forge's first three steps for its owner, as MCP `next_steps` does
- GET /api/v1/admin/quotas and PUT /api/v1/admin/quotas/{key} read and set the per-account quotas, as MCP `quotas` does
- GET /api/v1/crew/now answers what the crew is doing right now, as MCP `now` does
- GET /api/v1/repos/{owner}/{name}/vision answers the repository's vision and direction, as MCP `vision` does
- The changelog's days and "shipped today" follow the reader's clock
- A pull the access wall holds says so: it stops reading "approved and green" and "moving"
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:39at56z5zh is past its budget: trevato/forge: "the Files page of a 40-file diff: fastest cold view of 3 and fastest repeat view of 5 stay under their …
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:l4srihhymu is past its budget: trevato/forge: "the decision ledger > stop is not the last word on a red check: the environment's fault runs it again, …
- GET and PUT /api/v1/user/notify read and set your phone notify URL, as MCP `notify` and Settings already do
- On a preview, the /__forge/ door links "What changed" to the pull's files, for a reader of the repository
- MCP `issues` lists a repository's issues by state, label and author, paged, as GET …/issues does
- MCP `hooks` takes action `deliveries` with an `id` and answers that webhook's last deliveries, as the hooks page shows them
- Outward-facing and hard-to-undo actions ask first in the conversation, and act once on a yes
- Enter on a webhook in the terminal's Hooks screen opens its last 20 deliveries, each with its state, status and why it failed
- readBuildYield holds the main thread for over a second, repeatedly
- The test runner stops killing healthy shards, and each test file is isolated
- PATCH /api/v1/repos/{owner}/{name}/labels/{id} renames or recolours a label, as MCP repo_labels update and the labels page already do
- GET /api/v1/repos/{owner}/{name}/hooks/{id}/deliveries answers a webhook's last deliveries, as the hooks page shows them
- Release keeper: cut on cadence, verify under page load, roll back to the named known-good version, hold with a reason
- A public app's pages carry a Link to the forge's manifest for its repository, so an agent landing on the app finds what it can do
- On a fork, the page manifest offers its writer how it follows its parent: read it, take the parent's updates, propose its changes up
- The page manifest offers "make it yours" on a repository with an app, so an agent finds the copy without being taught
- A signed-out visitor sees Make it yours on every public app in /explore, and it carries them through sign-in to the plan of their copy
new above
offline