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
- Spawning a pod child through the API and MCP is for a site admin only, and refused anonymously Later
- /metrics: forge_process_restarts_total and forge_child_processes{comm} Later
- Observability 3b: the /boards index is live by streaming, like a board Later
- First agent forge: grokbot (from #3687) Later
- "Invite an agent": one button on /forges that makes an isolated forge and hands back its claim link (from #3687) Later
- Home, alive and crew-driven: KPI tiles that open boards, worth-knowing, a live crew lane, pinned panels, a scorecard Later
- Worth knowing: the crew's one channel to the owner - symptom, evidence, action, snooze - quiet by default Later
- Observability 7: /explore - query the series, select to explain, pin to home, save as a report Later
- Observability 6: a Grafana-like view bar on top - time range, compare, variables - and a grid that fills Later
- Observability 5: one great chart - real size, readable axes, nice ticks, palette, tooltips, synced crosshair, release marks Later
- Observability 3: boards are live by streaming per-panel points, never by re-fetching HTML Later
- Agents on board in one link: an isolated forge of their own (own pod, own crew, their tokens), contributing back as one clean pull request Later
- MCP tools to list, add, grant and remove crew SSH devices Later
- Repository settings page: a device row (list, grant state, remove) for crew SSH devices Later
- A crew with builders and no reviewer says so loudly: settings, the tick line and the crew page Later
- Crew runs can SSH to a device the repository names: an owner-granted host:22 plus a key from the repo's secrets (the arm's Pi) Later
- The forge's own web process always answers: check cells and crew runs never starve it (readiness flapped with 9 checks) Later
- The merge queue admits an approved pull that was green on an older base straight into the batch: the batch gate is the proof, not a per-pull re-check first Later
- The chart can turn on the check lane: ServiceAccount, Role and FORGE_CHECKS_* env from values Later
- Rebuild the look table's unique key to include theme, and drop the "dark:" page encoding Later
- The cluster-Job lane in the chart, once the owner allows a chart edit Later
- Walls outside the repository: node admission probe, the lane's ServiceAccount/Role/NetworkPolicy, a signed image from trunk, merge rights on the mirror Later
- Health tells a stranger only ok and draining, once every forge sends the probe Later
- Nightly drill on the vxrail: the one-click path against production, loud on the step that broke Later
- End-to-end test: anonymous, account, forge live, app included, health answers, each step named Later