Supervising coding agents with Herdr
How Herdr keeps coding sessions available while you detach, and what changes when its server restarts.
Guides, news and explanations about AI and reliable systems.
How Herdr keeps coding sessions available while you detach, and what changes when its server restarts.
Separate detection from response and find delays that an improving average can conceal.
The permissions, state and recovery paths an agent needs when its tool calls can change a running service.
Use instrumentation and context propagation to connect the evidence in an investigation.
Clarify ownership across shared platforms, service reliability, and incident response.
Separate a completed task from evidence that the underlying risk was reduced.
Account for context limits, retries, latency, and the work behind a useful result.
Evidence can split a 5 Whys investigation into several contributing causes. A concurrency example shows how to turn those explanations into useful tests.
Conflicting restart instructions show where a source-backed notebook helps: finding the relevant passages, dates and exceptions for the runbook owner.
Power and cooling affect the work a GPU pool can sustain. Device signals, request completions and queue growth help distinguish a physical limit from a workload change.
A rollback exception tests whether Opus 4.6 preserves decisive evidence across a long session, and whether the resulting answer arrives in time to help.
A timed-out scaling request needs a durable record and destination-state checks. Reusable operational skills need to recover unfinished work as well as start it.