Todo-List-Driven Autonomous Agent

aka todo.md Agent, Persistent Markdown Plan, Externalised Plan File

category: planning-control-flow · status: emerging

Intent

Have the agent author a plan file (e.g. todo.md) early in the run, tick items as it completes them, and re-inject the remaining plan into context; the file is durable plan and working memory.

Context

A long-horizon autonomous task in a sandboxed VM with file-system access; the run may span hundreds of tool calls and exceed any usable in-context plan.

Problem

In-context plans drift to the middle of the window where the model attends least; without a durable plan artefact, paused or context-truncated runs cannot recover; the agent forgets which sub-tasks are done.

Forces

Solution

Early in the run, the agent writes its plan as a checklist file (todo.md) in its sandbox. Each turn: read the file, work the next unticked item, update the file (tick the item, add follow-ups, drop dead-ends). Re-inject the unticked tail of the file into the prompt before the model's next turn. The file outlives any single context window. Paired with a sandboxed VM that gives the agent persistent storage and basic tools (browser, shell, file editor).

Structure

Sandbox VM (browser, shell, files) + agent loop: read(todo.md) -> select next item -> act -> update(todo.md) -> repeat.

Constrains

The agent may not advance past an unticked item without recording the action in the plan file; arbitrary in-context-only plans are forbidden.

Consequences

Benefits

Liabilities

Known Uses

Related Patterns

References