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.
| API and MCP server, Rust identity service, registration, site redesign | 1 | { |
| 2 | "$schema": "../../node_modules/wrangler/config-schema.json", | |
| 3 | "name": "g1t-api", | |
| 4 | "account_id": "1e6f2cffa3f445920836e8ebe446bb58", | |
| 5 | "compatibility_date": "2026-09-26", | |
| API and MCP server in Rust; a public index at the API root | 6 | "main": "build/index.js", |
| 7 | "build": { "command": "cargo install -q worker-build@0.8.7 && worker-build --release" }, | |
| API and MCP server, Rust identity service, registration, site redesign | 8 | "workers_dev": false, |
| 9 | // One Worker, two hostnames: REST on api, MCP on mcp. Both are thin | |
| 10 | // adapters over the same operations. | |
| 11 | "routes": [ | |
| 12 | { "pattern": "api.g1t.sh", "custom_domain": true }, | |
| 13 | { "pattern": "mcp.g1t.sh", "custom_domain": true } | |
| 14 | ], | |
| 15 | "services": [ | |
| 16 | { "binding": "IDENTITY", "service": "g1t-identity" }, | |
| 17 | { "binding": "REPOS", "service": "g1t-repos" }, | |
| 18 | { "binding": "WORK", "service": "g1t-work" }, | |
| Agents as a team: lifecycle, merge queue, billing and a new shell | 19 | { "binding": "EVENTS", "service": "g1t-events" }, |
| 20 | { "binding": "RUNNER", "service": "g1t-runner" }, | |
| Integrations: your own model provider, alerts that open issues, tickets agents read | 21 | { "binding": "BILLING", "service": "g1t-billing" }, |
| 22 | { "binding": "INTEGRATIONS", "service": "g1t-integrations" } | |
| API and MCP server, Rust identity service, registration, site redesign | 23 | ], |
| 24 | "observability": { "enabled": true } | |
| 25 | } |