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.
| Initial g1t: services, event bus, intents and attempts | 1 | { |
| 2 | "$schema": "../../node_modules/wrangler/config-schema.json", | |
| 3 | "name": "g1t", | |
| 4 | "account_id": "1e6f2cffa3f445920836e8ebe446bb58", | |
| 5 | "compatibility_date": "2026-09-26", | |
| Agents as a team: lifecycle, merge queue, billing and a new shell | 6 | // Runs beside the services it calls, which run beside their databases: |
| 7 | // a page makes several calls in turn, and only the page travels back. | |
| 8 | "placement": { "mode": "smart" }, | |
| Initial g1t: services, event bus, intents and attempts | 9 | "main": "./workers/app.ts", |
| Docs as their own app; shared theme package | 10 | "routes": [{ "pattern": "g1t.sh", "custom_domain": true }], |
| Initial g1t: services, event bus, intents and attempts | 11 | // The site holds no data of its own; everything goes through services. |
| 12 | "services": [ | |
| 13 | { "binding": "IDENTITY", "service": "g1t-identity" }, | |
| 14 | { "binding": "REPOS", "service": "g1t-repos" }, | |
| 15 | { "binding": "WORK", "service": "g1t-work" }, | |
| Agents as a team: lifecycle, merge queue, billing and a new shell | 16 | { "binding": "RUNNER", "service": "g1t-runner" }, |
| What happened across an outcome, as a feed beside its graph | 17 | { "binding": "BILLING", "service": "g1t-billing" }, |
| Integrations: your own model provider, alerts that open issues, tickets agents read | 18 | { "binding": "EVENTS", "service": "g1t-events" }, |
| 19 | { "binding": "INTEGRATIONS", "service": "g1t-integrations" } | |
| Initial g1t: services, event bus, intents and attempts | 20 | ], |
| 21 | "observability": { "enabled": true }, | |
| 22 | "upload_source_maps": true | |
| 23 | } |