Automate with chores

Chores let agents perform one-off or recurring tasks automatically. You can define them in Markdown files or .too programs, schedule their execution, and manage their runs.

Define chores

To create a chore that checks documentation in a project, first grant the agent access to the directory:

too eve workspace add ./project --name repo
too eve chore new check_docs

The new command opens your editor and creates chores/check_docs.md in the agent's home.

Define a one-off chore:

---
title: Check documentation links
---
 
Check Markdown documentation links in repo:// and report broken targets.

Without a schedule, the chore runs once when created or when its body changes.

To run it every six hours, add a schedule to the frontmatter:

---
title: Check documentation links
schedule: FREQ=HOURLY;INTERVAL=6
---
 
Check Markdown documentation links in repo:// and report broken targets.

Edit or delete the definition with:

too eve chore edit check_docs
too eve chore delete check_docs

You can also define chores directly in agent.too:

chore check_docs:
  schedule = FREQ=DAILY;INTERVAL=1
  Check Markdown documentation links in repo:// and report broken targets.

Inline definitions take precedence over Markdown chores with the same name. The CLI authoring commands manage Markdown definitions; inline chores are edited in their source files.

See Chore file formats for additional fields and examples.

Start the chore driver

The chore driver dispatches scheduled work and new one-off chores. Start the agent with the driver enabled:

too eve start --enable chore

To enable both chat and chore:

too eve start --enable chat,chore

If the agent is already running with different drivers, stop it before restarting:

too eve stop
too eve start --enable chat,chore

The agent must remain running for the chore driver to dispatch work.

Run and manage chores

List the agent's chores:

too eve chore list

Each chore maintains its own thread and execution history. See Inspect and control runs to review results and monitor active work.

To request an immediate run, including for a completed one-off chore:

too eve chore run check_docs

Repeated manual requests are merged when an occurrence is already pending. If a chore is running, one follow-up occurrence can be queued.

To cancel pending or active work:

too eve chore cancel check_docs

Canceling clears pending work or stops the active occurrence without removing the definition or its future schedule.

Deleting a chore prevents future dispatches but preserves its history. It does not cancel an occurrence already running.

A finished, failed, or canceled one-off chore does not restart unless its body changes or another run is requested.