trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
Later ✕
P0 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
- 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
- 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 Later
- The cold front page build is slow: batch the per-repo canRead queries and the runtime status scan Later
- 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
- The check host cannot start a cell: FORGE_REQUIRE_CELLS turned main red (0c82bad5); give the host cells, then require them again Later
- Private apps: the crew's reviewer can't reach their previews (bare 404 at the edge), so reviews stall and pulls get handed to a person Later
- A cold-read UI audit of the top pages, scored in docs/design/baseline.json Later
- Toast and skeleton parts in ui.ts, shown in the gallery Later
- A global component registry (shadcn registry format): every app installs owned copies, updates arrive as pulls, a gallery with usage, MCP install; the app template rebuilt on it Later
- Repo header: descriptions clamp to 2 lines with expand (apps API separates description from brief), and a clear crew status line: "paused at its ceiling" with a Raise button Later
- Move in: bring all of GitHub and Vercel into the forge through one trusted flow (inventory → plan → paced copy → verify), read-only toward the sources; clean-up is a separate, later step Later
- /advisories: the forge listens to CVE.org, OSV, GHSA, NVD, CISA KEV and EPSS, matches them to every repo's dependencies, and gives a sleek explorer with fix-pull actions, MCP tools and integrations Later
- Security against 24/7 agent swarms: OSV dependency scans with auto-fix pulls, secret scanning at push, code scanning in review, an exposure map with rate limits, a scheduled red team Later
- Errors, Sentry-grade and first-party: stock Sentry SDKs → the forge (envelope protocol + OTel), grouping, suspect pull, and the healing loop (error → issue → fix → resolved → regression reopens) Later
- The atlas of abstractions: the forge as one typed object graph; see each abstraction's lifecycle, merge apps (schema + data), an idea garden for demos, one shell for all apps Later
- Standard app settings, like iPhone Settings: apps declare settings in forge.json; one store edited from the forge or the app; live, no restart Later
- Clogs: prevent them (inflow governor, hot-file limit), say so at the top of home within 15 min, and a /flow page to clear one in two clicks Later
new above
offline