XNews

Thorsten Ball Details Agent Workflow Spanning Build, Release and Production Observability

Thorsten Ball Details Agent Workflow Spanning Build, Release and Production Observability

Thorsten Ball of AmpCode outlined a workflow in which agents operate across build, release, CI, production logs, feature flags and monitoring rather than only replacing editor typing. He described a roughly 2 million-line monorepo built almost entirely by AI, about 15 AGENTS.md files plus skills, and an OOM incident handled through Slack, logs, BigQuery, a feature flag and a verification Orb. Ball said he has written almost no code locally for about eight weeks and uses the strongest model, Opus 5.5, for agent work.

Event version 1.

Key insights

Agents extend beyond the editor

Ball argued that placing agents only in the former text-editor slot while keeping push and review unchanged does not raise output. Agents should also deploy, read CI, inspect production logs, toggle flags and check metrics.

Codebase readability and process form a triangle with agents

Ball described the gain as coming from agents multiplied by codebase readability and process. About 15 AGENTS.md files and skills for the dev server, gcloud, BigQuery and deployment let agents see, start and inject data with fewer hallucinations.

Strongest model and asynchronous use

Ball said he always uses the strongest model, naming Opus 5.5, while cheaper or open models suit fixed workloads. He advances work asynchronously, requests multiple UI variants at once, and reviews only load-bearing code.

Evidence before review

Ball requires indisputable evidence that code runs, including E2E tests, screenshots, recordings and test matrices, before review. He said he has written almost no code locally for about eight weeks.

OOM incident handled by agents

An OOM report arriving in Slack started an Opus thread that checked top memory processes and alerts, logs, BigQuery and similar bugs. The fix was wrapped in a feature flag, released, approved by a human, then verified by spawning an Orb that consumed memory, with a recording sent back.

Source posts