Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Tasks and Chores

Toolang treats durable work as a first-class part of the runtime. Tasks are the tracked work items an agent should work through. Chores are local recurring triggers that can create, update, or advance that work.

Tasks are the durable unit

Use a task when work needs:

  • explicit ownership
  • a stable thread of progress
  • updates over time
  • a final recorded outcome

Local tasks live under the agent room:

${AGENT_HOME}/.toolang/agents/{AGENT}/tasks/

A local task file stays readable and editable:

---
id: docs-ship
requester: owner
status: todo
---
 
## Task
Review the changed docs and publish a release summary.
 
## Notes
 
## Progress
 
## Outcome

Toolang treats that task as a durable thread. When the task changes, the runtime can enqueue a normal task turn for the same agent.

Chores are recurring local triggers

Chores live alongside tasks:

${AGENT_HOME}/.toolang/agents/{AGENT}/chores/

Use a chore when work should happen on a schedule or policy trigger, for example:

  • check for newly assigned remote issues
  • publish a periodic summary
  • refresh derived local state

A chore is not a separate communication primitive. If a chore needs to involve another actor, it should usually do so by creating or updating a task, or by sending a chat message.

Remote task systems still become local tasks

Toolang keeps one task model inside the runtime. Remote systems such as GitHub issues or Linear tickets should be mirrored into local task files first. That keeps runtime behavior consistent:

  • local and remote work use the same task thread model
  • the same agent prompt can handle both
  • provider-specific logic stays in services and chore sync logic

Chat, task, and chore each do different jobs

  • use chat for quick coordination
  • use task for durable delegation and tracked work
  • use chore for recurring local triggers

That separation keeps collaboration readable without adding a different runtime model for every work source.

Read next

  • Read Running Agents for the runtime surfaces that process tasks and chores.
  • Read Runtime State for tasks/, chores/, and pulse.json.
  • Read Task Model for the exact local-task, remote mirror, and task-service rules.
© 2026 Toolang