Agent Atlas / Runtimes and workbenches

laude-institute/headlong

A Bash microharness for persistent agents whose dispatcher-owned wake clock, thought stream, trajectory DAG, recursive shell loop, and backoff policy expose the operating costs of agency between human requests.

Persistent agent microharness Scope profile Reported + sourced Reviewed August 26, 2026
Intended operator

Individuals and teams running one long-lived agent across terminal, web, Slack, or Telegram.

Primary surfaces

persistent agent runtime / terminal and web dashboard / Slack and Telegram bridges

Tracked repository

laude-institute/headlong

Teaching mechanism

The next thought is a scheduled systems event

The monolith writes a future wake epoch, the always-alive dispatcher turns it into a trajectory step, and a backoff policy decides how soon the agent should think again based on whether the last wake produced visible work, only a thought, an idle, or an error.

Evidence limitA continuous wake loop demonstrates persistent execution, not consciousness, reliable initiative, production safety, or measured long-term value.
Inspect the source
System map status

Reporting is still in progress.

This scope profile names the project's place in the field and one useful mechanism. It does not claim that every runtime boundary has been inspected.

Learn Through This Project

10 lessons
Chapter 1 Before the First Model Request Chapter 2 The Invisible Prompt Chapter 3 Tool Calls: Contract, Authorization, Execution Chapter 4 Loops, Workflows, and Recovery Chapter 5 Delegation Is a Distributed System Chapter 6 Memory Is a Typed Storage Contract Chapter 7 The Approval Trap Chapter 8 The Human Control Loop Chapter 9 Trust Must Make Its Case Chapter 10 The Future Has Three Branches

Compare Its Boundaries

8 labs
Comparison labTool ContractsComparison labGoverned MemoryComparison labDelegation ReceiptsComparison labApproval BoundariesComparison labHuman WorkbenchComparison labSessions And RecoveryComparison labEvidence And EvaluationComparison labMaturity Signals

Latest Reporting

3 articles
Builder Work: Give Extra Memory a Budget, Not the Whole Context

September 27, 2026 — A Headlong review found that helpful citations could overwhelm a small context request—or stop it halfway through. The repair gives optional memory its own limits while preserving the base. laude-institute/headlong

 Builder Work: A Redaction Test That Had Never Written a Note

September 23, 2026 — Headlong’s privacy fix gained a stronger test only after review noticed that the supposedly protected memory file never existed. laude-institute/headlong

 Builder Work: Headlong Puts Its Runtime Out of Reach

September 16, 2026 — A persistent agent needs somewhere to experiment without rewriting the machinery that keeps it alive. Headlong’s systemd deployment draws that line—and its migration shows why the line is harder than a read-only flag. laude-institute/headlong

Primary Sources

Headlong repository

Primary public source for the persistent loop, trajectory, context, shell execution, messaging bridges, sandboxing, and tests.

 Thought-only backoff commit

Fresh code receipt for distinguishing internal rumination from visible work and pacing the resulting spend.

Open Questions

  • Can persistent agency become measurably useful without turning rumination, shared context, and unattended shell access into permanent operating risk?

Evidence state describes what this Atlas profile can support today. It is not a product score and it is not evidence that uninspected capabilities are absent.