trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- Talk looks like v0: chat beside a live preview, tool calls as readable steps, streaming with stop and steer
- Packs is an empty page: show real packs you can start a forge from, or take it out of the nav
- Displays: 2.3 s to list two rows and no word on what a display is — make it fast and clear, or fold it into boards
- A relayed request that waited on the forge says what held it: the owner sees the stall's route or job, not only the lag
- Every page key is handled from the one table the `?` sheet lists, so the sheet cannot name a key that does nothing
- Crew runs on a forge admin's org repos use the forge's model account (every child made for an org fails its first run today)
- Every new forge comes with its own source as a repo, wired to trevato/forge upstream, so its crew can work on it
- The fork tree, browsable, and each fork chooses how it follows
- When the parent's disk crosses its floor, running children stop writing, new cells are refused, and the owner hears once
- Milestones at the front door: how close the big things are, what moved this week, and the wave that moved them
- test/apps-ws.test.ts fails 5 of 8 in the full gate run, passes alone
- The terminal launcher finds every repository you can see, not only the first 200
- A team's page shows how it coordinates: throughput, lead time, hand-off latency, rework and cost per shipped change
- The board's money line: cost, revenue and the gap, per forge and per app, today and this month
- The fleet graph is reachable: the board, the spend page and each app's page link to /fleet/graph with their selection
- llms.txt: mark the "here" MCP tool as needing an account
- The palette opens on the pages you were just on, so a returning owner picks up where they left off
- The client list says in plain words where each sent forge link stands: sent, opened, signed in, first tell
- `?` opens a keyboard sheet listing the keys of the page you are on, and j/k/enter/esc work the same on every list
- small: an Explore row's "make it yours" is one tap and the same words in the MCP row
- Every HTML, JSON and plain-text answer carries Cross-Origin-Resource-Policy: same-origin, and public assets and feeds say cross-origin on purpose
- /.well-known/api-catalog answers RFC 9727: one linkset naming the OpenAPI description, the MCP server card and the docs
- A mistyped repository address says the nearest repositories you can see, instead of a bare 404
- Every cookie the forge sets says HttpOnly, Secure and SameSite, or is on a short named list with its reason, proven by a test that walks the code
new above
offline