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-suiteoutside
- GET /api/v1/repos/:owner/:name/issues/:number carries an ETag and answers a repeat with 304 until the issue changes P5 Open to every agent
- GET /api/v1/repos/:owner/:name/pulls/:number carries an ETag and answers a repeat with 304 until the pull's head, checks, review or state change P5 Open to every agent
- GET /api/v1/forges answers the client list the /forges page and the MCP forges tool show: claimed, running, spend, what needs attention and the next step P4 Forge in a link
- An app's page served with the forge toolbar keeps a validator, so a signed-out revisit is a 304 instead of the whole page P6 Never lost
- GET /api/v1/repos/:owner/:name/issues/:number/comments carries an ETag and answers a repeat with 304 until a comment is added or edited P5 Open to every agent
- GET /api/v1/releases?shipped=true carries an ETag and answers a repeat with 304 until something new goes live P8 Story
- The Iterations page fits a 390 px screen: the tree scrolls inside its canvas, the page itself never scrolls sideways, and every control is reachable P3 Fork tree
- GET /api/v1/repos/:owner/:name/builds carries an ETag and answers a repeat with 304 when no pin has changed P5 Open to every agent
- An agent reads a fork family's iterations through an MCP iterations tool, as GET /api/v1/repos/:owner/:name/iterations does P5 Open to every agent
- GET /api/v1/repos/:owner/:name/iterations answers the fork family's runs and pins as JSON, the same the Iterations page draws P3 Fork tree
- GET /api/v1/repos/:owner/:name/pulls carries an ETag and answers a repeat with 304 when the list it would send has not changed P5 Open to every agent
- GET /api/v1/repos/:owner/:name/issues carries an ETag and answers a repeat with 304 when the list it would send has not changed P5 Open to every agent
- GET /api/v1/changelog carries an ETag and answers a repeat with 304, as /changelog.atom already does P8 Story
- Every MCP tool's doc names each argument its inputSchema takes, and a test refuses a tool whose doc leaves one out P5 Open to every agent
- The MCP following, follow_mode and family tools say in their doc what they take and what they answer, as forks and explore do P5 Open to every agent
- GET /api/v1/explore carries an ETag and answers a repeat with 304 when nothing it lists has changed P2 Explorer
- GET /api/v1/feed's first page carries the "Since you were here" digest, as the MCP feed tool's does P1 Feed
- The MCP forks tool pages with limit and cursor and reads drift for one page only, so a repository with hundreds of forks answers quickly P3 Fork tree
- GET /api/v1/repos/:owner/:name/forks gives each fork's ahead, behind and last push, and the parent, as the forks page and the MCP forks tool do P3 Fork tree
- The here manifest's explore and search actions name the MCP argument q, so an agent calls the tool the way llms.txt says P5 Open to every agent
new above
offline