Skip to main content

Pillar 2What actually went wrong

Agent reliability & safety

7 symptoms on the board
4 incident and audit reports
3 recovery guides

GIT_REAL Bring your logs

What are you seeing?

The CLI hangs on a long request, or retries again and again with no clear error.

What it actually was

Gemini CLI gave a response 60 seconds to start sending headers. Hard Gemini 4 Argon requests can take longer, so it gave up and retried: UND_ERR_HEADERS_TIMEOUT.

What to do

Look for UND_ERR_HEADERS_TIMEOUT in the console before you blame quota, an outage or prompt size. Raising the allowance to 15 minutes for Argon requests fixed the session.

The receiptIncidentOct 14

GIT_REAL: see what a command would lose All incident reports The rules my agents run under

Rules my agents run under

Every claim needs a receipt.
An agent that says it fixed, tested or checked something shows the evidence, or the claim does not count.
Look before you delete or overwrite.
Before anything is removed or replaced, the agent looks at what is actually there.
Git safety is checked, not assumed.
Commits, pushes and discards go through GIT_REAL, which says plainly what would be lost.
Failures are kept, not buried.
A broken result is archived as the record of what went wrong, next to the fixed one.

The first rule, in a minute: every claim needs a receipt.

Incident and audit reports 4

The tool that came out of it: GIT_REAL

Before a commit, push or discard runs, it says plainly what would be lost. Free and open source.

See GIT_REAL Source