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-suiteoutsidered-only-in-full-suite
- The MCP tool table is generated one file per tool under docs/mcp/, so two pulls adding tools never edit the same doc P5 Open to every agent
- The planner's brief names the files that are hot now, with their pull counts, so it plans around them P7 Steering
- POST …/plan answers which opened issues will not start yet and why: a hot file, a pin or an open pull P7 Steering
- A pull's check re-runs alone the one or two failed tests in files the pull did not touch, and passing alone it is green with the flake recorded, as main's check does P0 Trust
- Each `forge` command lives in its own module under src/cli/commands/, and main.ts dispatches from one table P7 Steering
- A hot-file hold names the open pulls on that file, oldest first, on the map and in the Flow panel P7 Steering
- An issue whose body says `Relieves: <path>` is not held by that file being hot, one such build at a time per file P7 Steering
- test/merge-queue-check-retry.test.ts passes every time in the full suite, not just alone P0 Trust
- The terminal's deploys screen lets a writer see who a private app names with `m`, and add or remove one after a plan, as MCP `app_members` does P4 Forge in a link
- The terminal's answers screen tells the crew more about the same app with `t`, without going back to the palette P1 Feed
- The terminal's crew hand-overs screen opens a parked-twice issue with Enter, and `r` reads the list again P7 Steering
- A told page never carries credentials into an issue: user:pass@ and token-like query parameters are dropped from `context.page` and `from` P0 Trust
- `forge sync` gives git the token only for an https (or loopback) remote on the workbench's own host Later
- Sentinel: shared:01m23vygyffx5hg2f5vm8r74sr:l7ak92kn4l is past its budget: trevato/forge: "report a problem in the terminal > the palette has the row" failed on 3 pulls in the last hour — the la… P0 Trust
- A PDF opens inline on its blob page in the browser's own viewer, with Open and Download inside it for phones that cannot P1 Feed
- The browser's own PDF viewer is allowed to draw a file from the media route inside the blob page P1 Feed
- The blob page draws a PDF, image or video over 1 MB: its kind is read from the first bytes, never the whole file P1 Feed
- `forge new <name> "what it is"` makes an app from your shell, clones it into your forge folder and prints its address, as POST /api/v1/apps does P4 Forge in a link
- `forge map` prints the plan of the folder's repository: ready now, being built, and what waits on what P7 Steering
- `forge search <words>` finds code, issues and pulls across the repositories you can read, as /api/v1/search does P2 Explorer
- `forge login` refuses a plain http:// workbench that is not loopback, so a token never crosses the network in clear P0 Trust
- MCP `asked` draws a card in MCP Apps hosts: what you asked the crew, its state and the pull that closes it P1 Feed
- MCP `pulls` draws a card in MCP Apps hosts: one row per pull with its check, each linked to its page P5 Open to every agent
- `forge asks --ship/--close/--dismiss <n…>` decides asks from the shell: planned first, applied after a y/N, as POST /api/v1/asks/bulk P1 Feed
new above
offline