trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- MCP `new_app` makes an app from a sentence alone: the name is derived as the web and terminal do
- A token a person deletes stays deleted: its OAuth refresh token ends with it
- GET /api/v1/repos/:owner/:name/pulls/:number/looks lists a pull's looks, with its row in the OpenAPI contract
- Describe an app in one sentence in the terminal (palette `new-app`) and it is made with the crew on it, through newAppFromSentence
- GET /openapi.json at the root redirects to /contract/openapi.json, as /api/v1/openapi.json does
- /:owner/:name/events lists a repository's events in the browser, newest first and paged, as MCP `events` reads them
- GET /openapi.json at the root redirects to /contract/openapi.json, as /api/v1/openapi.json does
- Describe an app in one sentence in the terminal (palette `new-app`) and it is made with the crew on it, through newAppFromSentence
- /:owner/:name/map answers under 300 ms on trevato/forge and its Server-Timing names each step of the read: today one `map` phase takes 2.5–3.6 s
- The changelog is an Atom feed too: /changelog.atom lists what went live, and the page links it
- /:owner/:name/events lists a repository's events in the browser, newest first and paged, as MCP `events` reads them
- Describe an app in one sentence in the terminal (palette `new-app`) and it is made with the crew on it, through newAppFromSentence
- GET /openapi.json at the root redirects to /contract/openapi.json, as /api/v1/openapi.json does
- /api/v1/here names the changelog among what an anonymous visitor can do
- An OAuth token that expires can be refreshed: the code exchange returns a rotating refresh_token, so a harness never has to send the person back to sign in
- A resumed turn of the forge's agent cannot repeat a write that already happened
- docs/MCP.md points at the live tool list instead of carrying a stale copy of it
- The closed pulls list answers under 30 ms: its `words` phase is 71 ms today
- Settings › Webhooks shows a failed delivery's Redeliver button, as the terminal's `r` does
- New app's name-from-sentence loop is one exported action, newAppFromSentence in src/actions/apps.ts, and the web form calls it
- An open pull's page renders in under 20 ms: its `render` phase is 60–70 ms today because reads hide inside it
- /capacity and MCP `capacity` say whether this forge can swap itself, and why not: tcp_migrate_req, SSH held, or FORGE_SELF_SWAP off
- The apps shelf reads each app's newest crew run in under 10 ms: /trevato and /apps spend 320–400 ms in shelf-runs today
- /:owner/:name/map answers under 300 ms on trevato/forge and its Server-Timing names each step of the read: today one `map` phase takes 2.5–3.6 s
new above
offline