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 your OAuth apps for connecting origins, adds one and removes one, never reading back a secret, as MCP `origin_apps` does
- `forge tell "words"` tells the crew from your shell, about the repository of the folder you are in
- The terminal lists the crew's agents with model, brief and budget, and an admin changes one after a plan, as MCP `agent` does
- The /__forge/ door says who of the crew is working on this app or preview now, as the pill does
- Convert the 71 expectBudget call sites to counted work
- On a preview, the pill's "Preview of pull #N" line is a link to that pull on the forge
- A preview's toolbar page lists the files its pull changed, each a link to that file's diff
- The terminal lists a repository's labels on a read-only Labels screen
- 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, …
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:10c56sox9a is past its budget: trevato/forge: "reserved names > every top-level page of the forge is a reserved name" failed on 3 pulls in the last ho…
- A weekly model review: the forge moves each role to the cheapest model that holds its quality, from its own numbers
- The map page has a First button on each ready issue, and the ranked one shows first
- Forge a repository: one action on any repository spins up a fresh forge with it as the template
- A screenshot never shows a browser error: looks of private apps show a certificate warning
- A crew run can open its own preview on a private repository
- Release the issues the old Later-gate rule still holds (#7636, #7637 and others)
- A plain fork offers how it follows its parent (tell me / take updates) on its own page
- A roll's old forge stops writing before the new one starts its work: write pause under 30 s
- The crew does not build the same thing twice
- The gate cannot lock itself out: a known-good gate and a break-glass path
- Timing tests stop failing because the machine is busy
- The test runner stops killing healthy shards, and each test file is isolated
- A person's "this first" on a ready issue makes the dispatcher start it before the rest
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:1hngo4csjz is past its budget: trevato/forge: "README.md stays under 60 KB" failed on 3 pulls in the last hour — the lane's red, not theirs; they wait…
- Verify after landing: the full suite runs on main on a schedule, names the culprit, and proposes the revert
new above
offline