On 3rd October, my astro-coach agent tried to fix a production Supabase environment problem. It kept retrying until a model usage limit stopped it. The tempting summary is “the agent tried to fix production.”

That summary hides most of the engineering.

Step in the 3 October astro-coach run

Who did it

What it handed on

Diagnose the production Supabase environment problem

Person

A diagnosis and a specific fix to attempt

Bake the environment settings into the application build

Code

A build artifact whose configuration needed verification

Encounter a hang

Code/tool execution

An unresolved execution state the agent could not read

Decide to retry the environment fix

Model, acting through the agent

Another invocation, without resolving the previous attempt’s state

Keep retrying until a model usage limit stopped the run

Model choosing retries; code executing them

An interrupted workflow, without a confirmed outcome

Confirm the login message and whether users could actually log in

Person…