trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
P4 Forge in a link
220 of 239 done
19 open · 73 merged in 7 days · moved
About 2 days at this week's pace: 74 closed in 7 days, 19 open.
A candidate to trim: 19 open and nobody building.
Limbs
-
MCP: propose to the parent forge and list proposals 13 of 13 done
Blocked
1 more blocked
Merged in 7 days
- 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)
- /docs reads the forge's documentation on the forge itself: an index and each doc rendered, with no hop to the code host
- 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)
86 more merged
- Every new forge comes with its own source as a repo, wired to trevato/forge upstream, so its crew can work on it
- Any agent with only the URL starts building in one call: account, repo and live app, no person or crew needed
- The client list says in plain words where each sent forge link stands: sent, opened, signed in, first tell
- Request access: a stranger can ask for an account, and the admin allows it with one tap
- An agent asking `forges` sees each child's size and usage, as the machines page shows them
- A parent funds a child forge's crew: a $ cap per child on the parent's own credential, metered, shown on both forges
- A mirrored repo's page names its upstream, its licence and its original authors
- The first-login jargon test covers the site menu and command palette labels, and what it finds is reworded
- The new-forge page reads in plain words: a test fails it on the jargon list, for a visitor and for the owner
- A forge link says when it ends and its sender revokes it in one tap
- small: one name per thing in the account menu: SSH keys, access keys and linked sites read the same on the label, the page title, the empty line and the palette
- The first-login page shows each app with the crew member working on it, in one plain line
- When a fix for a note lands, the crew says in plain words what was wrong and what changed
- The sender reads the crew's replies to their note inside the forge button
- A test fails the first-login page on jargon, in its visible text and its labels, for every role that lands there
- Your dotfiles from a repository you name are in every shell you open
- docs/features/client-forge.md walks a zero-technical client from one link to the crew at work, and a test follows every link in it
- A note's sender gets the issue's link whenever they can read the repository
- A template repository whose folders each hold TEMPLATE.md and template.json offers each folder as a template
- small: the knobs panel shows the reserve as a read-only row beside Weekly budget
- The loopback-only look test cannot skip in the forge's check: a skip there is a failure that says why
- Knobs: the small share and polish cap are gone, and pace floor, reserve and queue depth follow Speed
- A machine's shell page says a detached session's stop time and picks it up where it was
- A looks capture gets a picture of a loopback app when loopback is the machine's only network
- A from-app note gets a first-look reply from the crew within a minute
- An app terminal you have open is in your sessions list and stops like a shell
- Admins mark repositories as app templates, and New app offers a picker when more than one is marked
- /packs reads pack repos the owner marks, and packs/ leaves the forge's source tree
- Stop a shell, or stop all idle ones, from your account and through MCP
- A machine shell opens to a greeting, a prompt with the repository and branch, and history that persists
- Your account lists the machine shells you hold, live and recent, and the sessions MCP tool lists them too
- A real Rust hello-world app builds with cargo and answers / in a test
- A build that hits its CPU, memory or time limit says which on the app page in one line
- New app copies a template repository's tip (readable by the caller, capped, no symlinks), with a door to name it
- A pack app's source can be a forge repo, and deploying it forks from the forge with lineage
- A from-app issue is assigned on arrival, and the flow alarm fires when one waits
- An app whose / answers an error is not boot ok
- Knobs: one panel on the crew page with five plain dials, each showing its live effect, editable in place
- After every release a cell child cannot wake for ten minutes: the boot opens every hosted child and fills FORGE_CHILD_AWAKE_MAX ("the forge is full")
- The packs' upstreams are read-only forge mirrors under the packs owner, re-synced on a schedule
- A machine shell that prints output is not idle, and its idle stop is a setting with its reason
- A refused host is said out loud on the app page, and allowing it is one switch
- An app that names Rust gets cargo on its install, test and run steps from a pinned cached toolchain, and a Rust hello-world app serves
- forge.json can name a pinned toolchain, and an unknown or unavailable one fails the deploy in one plain line
- A stranger's pull diff or a failed check log cannot close its fence in a crew brief
- A new or migrated app tells its owner where it stands, live, until it runs
- Settings › Move to another owner fits a 390 px phone, and the pull quotes its measured width
- An open pull is always on the Pulls page: the tab's count and the list agree
- forge.json run may be a compound command: cd sub && bun server.ts starts
- Every forge preview takes a phone look of the sample repository's Settings scrolled to "Move to another owner", with its measured width
- src/spawn/pod.ts renders a child forge's namespace, quota, PVC, Deployment and default-deny policies, from pull #3743's branch
- The pinned forges page updates, rolls back and checks a forge, each after a confirm
- The app page's adapter runs list has no sideways scroll at 390px, with a look on the pull
- An adapter that fails five scheduled pulls in a row is paused, and its app page says so in one line
- MCP moves a repository to another owner, as `POST …/transfer` does
- A forge admin's page lists the pinned forges: name, version, address, health and last change
- A git clone or fetch of a moved repository's old HTTPS URL reaches the new one
- The terminal's Adapter screen lists the last pull runs
- The app page's Adapter section has Pull now, as the API and MCP already do
- The terminal's Adapter screen runs a pull now with one key
- The app page lists an adapter's last ten pull runs
- A repository's Settings page moves it to another owner, as the API and terminal already do
- A writer can run an adapter's pull now through the API and MCP, without waiting for its schedule
- docs/ADAPTERS.md's Status says what runs today: the forge calls /pull on schedule and records each run
- A new forge's admin is asked for an everyday account in one plain block on home, not a boxed card
- An app's members and custom domains speak the home page's language
- Connecting an origin, the device code and the authorize step, speaks the home page's language
- An app's settings form, visitors and environment names speak the home page's language
- Where visitors come from, for the forge and for one app, speaks the home page's language
- The New forge page at /forges/new, where the owner spawns a forge for a client, speaks the home page's language
- A spawned forge's first-login next steps speak the home page's language
- The /claim page, where a spawned forge's owner takes it, speaks the home page's language
- The new-organization page and a team's page speak the home page's language
- Settings › Origins speaks the home page's language
- /migrate and a migration's job page speak the home page's language
- The /forges list, its fresh-link page and its remove confirm speak the home page's language
- The /bring steps speak the home page's language
- The /apps list answers a warm request under 50 ms and works with JavaScript off, and a test holds both
- The /apps list speaks the home page's language
- The /forges and /forges/new pages speak the home page's language, with looks before and after
- The docs and /settings/origins say plainly that a forge older than 0.7.346 is connected from the newer side, and that upgrading it lets it connect outward too
- One command on your own machine deploys a pack: its apps running with their history, the crew set up, only the model credential left to supply
- The /forges and /forges/new pages fit a 390 px phone: no sideways scroll, the form's fields and long forge names wrap
- Hosted forges have a wake rate per person and a forge-wide ceiling on how many run at once; a sleeping forge doesn't count
- Hosted forges per person are limited by count and storage, each refused in plain words
- One press on the home page opens a pack: what it brings and the one command that deploys it
Issues
210 closed
-
An app whose / answers an error is not boot ok #10565 done
-
The New forge page asks for a name and a size, and nothing else #3095 not doing
-
The /apps list speaks the home page's language #9711 not doing
-
The app page lists an adapter's last ten pull runs #10127 not doing