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-suite
- The repository head's actions draw §5's bar and .repo-actions leaves the stylesheet (rebase branch scout/4594-the-repository-head-s-actions-draw-5-s-b) P8 Story
- A directory's `?all=1` lists at most 5,000 entries and says how many it left out (from branch scout/6196-…) Later
- The /__forge/ door's "More pulls" line says how many and links to the open pulls (from branch scout/6411-…) Later
- /migrate's first field is the repository URL, and with no account connected the page is that field and Connect GitHub (from branch scout/6406-…) Later
- /.well-known/mcp.json names the running version and commit, the same ones llms.txt prints Later
- Tick up to 20 of an account's repositories on /migrate and start them all with one "Migrate selected" Later
- Each connected account on /migrate is one row that opens to a search and its 8 most recently pushed repositories Later
- An issues list finds the open pulls that close its rows from their numbers and bodies alone, not 200 whole pulls Later
- In a preview, the forge pill's panel says the pull's check: green, red with its first failing test, or running Later
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:ky51wt3erj is past its budget: trevato/forge: "tools/list stays under 40 KB, with 3 KB of headroom (37,000 bytes)" failed on 3 pulls in the last hour … Later
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:14q2ira1ie is past its budget: trevato/forge: "a plan of 2,000 closed and 300 open issues, 3,000 pulls and 1,500 runs reads in under 50 ms with the sa… Later
- Any agent, any provider: URL → account → its own forge → granted access → a landed pull on the owner's repo, with no human step but one grant (grokbot is the first tester) Later
- The review and build briefs say a preview's /__forge/ and pill come from the host forge, so changes to them are judged by test Later
- Studio Design tab: a component explorer and a live theme editor; themes compile to edge-served CSS that updates every app on the theme in real time Later
- A weekly design wave: a designer role passes over every page and component (tabs first), fixes small things as pulls, and files design asks for next time Later
- The front page's build shows its stretches in Server-Timing on a cache miss Later
- Run the cold-read audit once and commit the coldRead block (#5882) Later
- The terminal's migrate sorts each account's repositories by last push, previews a pasted URL, and migrates several at once, like /migrate Later
- GET a repository's milestones answers under 50 ms: trevato/forge's `read` phase is 1,365 ms today P8 Story
- Re-cut a conflict in a split file mechanically instead of a full agent run (#6140, part 3) Later
- A fork's files page reads its drift from the parent under 3 ms when neither tip has moved P3 Fork tree look ·
- The cold front page build is slow: batch the per-repo canRead queries and the runtime status scan Later
- releases.json links each release to its entry on /changelog P8 Story
- The MCP lists an app's open pulls, as the door and `ssh app@forge pulls` do Later
- A browser test loads the owner's home at 375 px and fails on any sideways scroll Later