Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Icons are cached at the edge | 1 | { |
| 2 | "$schema": "../../node_modules/wrangler/config-schema.json", | |
| 3 | "name": "g1t-runner", | |
| 4 | "account_id": "1e6f2cffa3f445920836e8ebe446bb58", | |
| 5 | "compatibility_date": "2026-09-26", | |
| 6 | "main": "./src/index.ts", | |
| 7 | "workers_dev": false, | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 8 | // One image (the base plus the runner binary), on three machine sizes. |
| 9 | // scripts/deploy.mjs deploys with each image set to the reference it | |
| The docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were. | 10 | // built and pushed ("The runner's images" in |
| 11 | // docs.g1t.sh/guides/deploy-to-cloudflare/), so a deploy builds | |
| 12 | // nothing; "./Dockerfile" here is for building by hand. | |
| Icons are cached at the edge | 13 | "containers": [ |
| 14 | { | |
| 15 | "class_name": "AttemptSandbox", | |
| 16 | "image": "./Dockerfile", | |
| 17 | "instance_type": "standard-1", | |
| 18 | "max_instances": 20, | |
| 19 | // A deploy replaces sandboxes. Ones that are busy are given this | |
| 20 | // long, in seconds, to finish first, so shipping g1t does not | |
| 21 | // kill agents in the middle of their work. | |
| 22 | "rollout_active_grace_period": 7200 | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 23 | }, |
| 24 | { | |
| 25 | // Workflow jobs with `runs-on: g1t-2core`: 2 vCPU, 8 GiB, 16 GB. | |
| 26 | "class_name": "Sandbox2Core", | |
| 27 | "image": "./Dockerfile", | |
| 28 | "instance_type": "standard-3", | |
| 29 | "max_instances": 10, | |
| 30 | "rollout_active_grace_period": 7200 | |
| 31 | }, | |
| 32 | { | |
| 33 | // Workflow jobs with `runs-on: g1t-4core`: 4 vCPU, 12 GiB, 20 GB. | |
| 34 | "class_name": "Sandbox4Core", | |
| 35 | "image": "./Dockerfile", | |
| 36 | "instance_type": "standard-4", | |
| 37 | "max_instances": 10, | |
| 38 | "rollout_active_grace_period": 7200 | |
| Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next. | 39 | }, |
| 40 | { | |
| 41 | // Workspace agents' own computers (src/computer.ts): the same image | |
| 42 | // in MODE=computer, one per agent, awake only while a session uses | |
| 43 | // it. Modest to start; raise it as agents get computers. | |
| 44 | "class_name": "AgentComputer", | |
| 45 | "image": "./Dockerfile", | |
| 46 | "instance_type": "standard-1", | |
| 47 | "max_instances": 20, | |
| 48 | "rollout_active_grace_period": 7200 | |
| Icons are cached at the edge | 49 | } |
| 50 | ], | |
| 51 | "durable_objects": { | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 52 | "bindings": [ |
| 53 | { "name": "SANDBOX", "class_name": "AttemptSandbox" }, | |
| 54 | { "name": "SANDBOX_2CORE", "class_name": "Sandbox2Core" }, | |
| Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next. | 55 | { "name": "SANDBOX_4CORE", "class_name": "Sandbox4Core" }, |
| 56 | { "name": "COMPUTER", "class_name": "AgentComputer" } | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 57 | ] |
| Icons are cached at the edge | 58 | }, |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 59 | "migrations": [ |
| 60 | { "tag": "v1", "new_sqlite_classes": ["AttemptSandbox"] }, | |
| Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next. | 61 | { "tag": "v2", "new_sqlite_classes": ["Sandbox2Core", "Sandbox4Core"] }, |
| 62 | { "tag": "v3", "new_sqlite_classes": ["AgentComputer"] } | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 63 | ], |
| Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next. | 64 | // Where agents' computers keep their homes between wakes (src/computer.ts). |
| Agents' computers keep their homes. The runner binds the agent homes bucket, which now exists with its rule that abandoned uploads go after a day, so a computer that sleeps wakes with what it had and the Computer tab shows the disk attached. The deploy guide says a self-hosted g1t without the bucket comments the binding out. | 65 | // The operator makes the bucket before the first deploy with this binding |
| 66 | // ("Agents' computers" in docs.g1t.sh/guides/deploy-to-cloudflare/): | |
| Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next. | 67 | // |
| 68 | // npx wrangler r2 bucket create g1t-agent-homes | |
| 69 | // npx wrangler r2 bucket lifecycle add g1t-agent-homes abort-uploads homes/ --abort-multipart-days 1 | |
| 70 | // | |
| Agents' computers keep their homes. The runner binds the agent homes bucket, which now exists with its rule that abandoned uploads go after a day, so a computer that sleeps wakes with what it had and the Computer tab shows the disk attached. The deploy guide says a self-hosted g1t without the bucket comments the binding out. | 71 | // Without it computers work but forget their home when they sleep, and |
| Every agent can have its own computer. A session that needs one wakes it: a home of its own on g1t cloud, one per agent and never shared, where it runs commands, reads and writes files and keeps what it made, with each session working in its own folder under a shared home; after ten idle minutes it sleeps, its home kept as a snapshot and restored when it wakes, and Reset wipes the home while memory and artifacts stay. Its shell and files are abilities with the usual choices, Alone, Alone when asked, Ask first or Never, offered only inside sessions and never to a chat reply; every command shows on the session with its output, and the agent's new Computer tab shows the state, the disk used of the five gigabytes included, the recent commands, and Wake, Put to sleep and Reset. Machine time counts only while it is awake, on the sandbox lines of the ledger that name the agent and who asked, held to the same spend caps as the session; the disk itself costs nothing in this version. The runner gained a long-lived supervisor that answers the computer's requests inside the container, and the runner service a computer per agent that keeps its snapshot in the agent homes bucket when one is attached, and says so when none is. The REST API and the agent tool can read a computer, wake it, put it to sleep and reset it. The agents, abilities, sessions, runners, billing and deploy guides say how it works and what an operator sets up; pinning a computer to your own runner, its browser and take-over come next. | 72 | // the Computer tab says the disk isn't attached yet. |
| Agents' computers keep their homes. The runner binds the agent homes bucket, which now exists with its rule that abandoned uploads go after a day, so a computer that sleeps wakes with what it had and the Computer tab shows the disk attached. The deploy guide says a self-hosted g1t without the bucket comments the binding out. | 73 | "r2_buckets": [{ "binding": "HOMES", "bucket_name": "g1t-agent-homes" }], |
| Icons are cached at the edge | 74 | "services": [ |
| 75 | { "binding": "IDENTITY", "service": "g1t-identity" }, | |
| 76 | { "binding": "REPOS", "service": "g1t-repos" }, | |
| 77 | { "binding": "WORK", "service": "g1t-work" }, | |
| 78 | { "binding": "BILLING", "service": "g1t-billing" }, | |
| 79 | { "binding": "INTEGRATIONS", "service": "g1t-integrations" }, | |
| 80 | { "binding": "ACTIONS", "service": "g1t-actions" }, | |
| 81 | { "binding": "DEPLOYMENTS", "service": "g1t-deployments" }, | |
| Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API | 82 | { "binding": "PROJECTS", "service": "g1t-projects" }, |
| 83 | // The context hub: the Context section every agent run starts with. | |
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 84 | { "binding": "CONTEXT", "service": "g1t-context" }, |
| 85 | // The event bus: abuse.flagged, when a sandbox looks like it is mining. | |
| 86 | { "binding": "EVENTS", "service": "g1t-events" } | |
| Icons are cached at the edge | 87 | ], |
| 88 | // A sweep for lifecycle steps whose trigger was missed or whose sandbox | |
| Merge branch 'worktree-agent-ac5b181a013e54348' | 89 | // died before reporting, which also starts queued nightly backups. |
| Icons are cached at the edge | 90 | "triggers": { "crons": ["*/5 * * * *"] }, |
| 91 | // Events it reacts to: a pull request ready for review, or its head moving. | |
| 92 | "queues": { | |
| Merge branch 'worktree-agent-ad8a36dfcd4176015' into spend-guardrails | 93 | "consumers": [{ "queue": "g1t-events-runner", "max_batch_size": 20, "max_batch_timeout": 1, "max_retries": 3, "dead_letter_queue": "g1t-events-dlq" }] |
| Icons are cached at the edge | 94 | }, |
| 95 | "vars": { | |
| 96 | // Each workspace chooses where its agents' model spend goes: its own | |
| 97 | // provider (under Integrations) or g1t's hosted models, paid from its | |
| 98 | // credit. While billing takes no real money, hosted models are open | |
| 99 | // only to these workspaces; once it does, to every workspace. | |
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 100 | "HOSTED_AGENT_WORKSPACES": "flagon-io", |
| Merge branch 'model-routing' | 101 | // How g1t routes agent work: "Auto" (AgentRouting and route in |
| 102 | // src/model-env.ts). Nobody assigning an agent has to choose; a workspace | |
| Merge branch 'main' into actions-toolkit-oidc-artifacts | 103 | // can still choose a tier per kind of work under Integrations. Staff |
| 104 | // choose each tier's model, the background model and each job's tier and | |
| 105 | // effort in sudo (Agents & models; billing's model_defaults), which the | |
| 106 | // runner reads once a minute and puts on top of this. So "tiers", "tasks" | |
| 107 | // and "effort" here apply only while billing cannot be read; the labels, | |
| 108 | // change sizes, "frontierAfter" and "learning" always do. "tiers": the | |
| Merge branch 'model-routing' | 109 | // catalogue, the model behind small (fast), large (standard) and frontier |
| 110 | // (most capable); "modelName" is shown to people, "model" is sent to the | |
| 111 | // provider, "price" (dollars per million tokens) is for estimates only. | |
| 112 | // "tasks": the tier each kind of job starts on, or "change" to size the | |
| 113 | // change a review reads ("smallChange" or less and nothing sensitive: small; | |
| 114 | // more than "largeChange": frontier). "frontierLabels", "largeLabels" and | |
| 115 | // "smallLabels" move work by its issue's labels. A failed attempt goes one | |
| 116 | // tier up and "frontierAfter" failures in a row to frontier; "learning" | |
| 117 | // steps work down or up by the repository's own recent runs of the kind. | |
| Merge branch 'main' into worktree-agent-a69aeabc4b0deeb97 | 118 | "AGENT_ROUTING": "{\"tiers\":{\"small\":{\"modelName\":\"Claude Haiku 5.5\",\"model\":\"claude-haiku-5-5\",\"price\":{\"input\":0.1,\"output\":0.5,\"cacheRead\":0.01,\"cacheWrite\":0.125}},\"large\":{\"modelName\":\"Claude Sonnet 5.5\",\"model\":\"claude-sonnet-5-5\",\"price\":{\"input\":2,\"output\":10,\"cacheRead\":0.1,\"cacheWrite\":2.5}},\"frontier\":{\"modelName\":\"Claude Opus 5.5\",\"model\":\"claude-opus-5-5\",\"price\":{\"input\":4,\"output\":20,\"cacheRead\":0.2,\"cacheWrite\":5}}},\"tasks\":{\"implement\":\"large\",\"revise\":\"large\",\"answer\":\"small\",\"review\":\"change\",\"update\":\"small\",\"plan\":\"small\"},\"effort\":{\"plan\":\"high\",\"answer\":\"medium\",\"update\":\"low\"},\"smallChange\":{\"files\":10,\"lines\":200},\"largeChange\":{\"files\":60,\"lines\":3000},\"largeLabels\":[\"security\"],\"frontierLabels\":[\"architecture\"],\"smallLabels\":[\"documentation\",\"docs\",\"typo\"],\"frontierAfter\":2,\"learning\":{\"window\":20,\"minRuns\":5,\"stepDownAt\":0.9,\"stepUpAt\":0.5}}", |
| Icons are cached at the edge | 119 | // Where sandboxes send model requests, with a token for their run. |
| 120 | // The proxy holds the keys: g1t's gateway's, or the workspace's own. | |
| 121 | "MODELS_URL": "https://models.g1t.sh", | |
| 122 | // Set to a Cloudflare AI Gateway id to route model traffic through it. | |
| 123 | // Used only when MODELS_URL is unset. | |
| 124 | "AI_GATEWAY_ID": "g1t", | |
| Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API | 125 | "CLOUDFLARE_ACCOUNT_ID": "1e6f2cffa3f445920836e8ebe446bb58", |
| 126 | // Guardrails' network list is enforced by starting sandboxes without | |
| 127 | // internet and passing their HTTP(S) through this Worker. "off" opens | |
| 128 | // every sandbox's network again, whatever its guardrails say. | |
| Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look | 129 | "EGRESS": "enforce", |
| 130 | // Sandboxes stop themselves when they look like they are mining | |
| 131 | // (crates/runner abuse.rs). "off" turns the CPU watch off; miners | |
| 132 | // named in commands are refused either way. | |
| Merge branch 'worktree-agent-ac5b181a013e54348' | 133 | "ABUSE_WATCH": "on", |
| Merge branch 'main' into actions-toolkit-oidc-artifacts | 134 | // Each workflow job gets a Docker Engine of its own, inside its |
| 135 | // sandbox, started the first time a step uses Docker or the job has | |
| 136 | // `services:` or `container:` (crates/runner docker/). "off" gives | |
| 137 | // jobs none. | |
| 138 | "DOCKER": "on", | |
| Merge branch 'worktree-agent-ac5b181a013e54348' | 139 | // Nightly backups (src/backup.ts): each sweep starts this many of the |
| 140 | // backups the repos service queued, with at most BACKUPS_RUNNING at | |
| 141 | // once. "0" starts none. | |
| 142 | "BACKUPS_PER_SWEEP": "4", | |
| 143 | "BACKUPS_RUNNING": "6" | |
| Icons are cached at the edge | 144 | }, |
| Merge branch 'worktree-agent-a8752162fea25f63f' into spend-guardrails | 145 | // Every log kept: few requests, and a failed run must be traceable. |
| 146 | "observability": { "enabled": true, "head_sampling_rate": 1 } | |
| Icons are cached at the edge | 147 | } |
This file's history is long; its oldest lines are credited to the oldest commit read.