Skip to main content
Strawberry has a built-in plan and todo system for multi-step work. The source of truth is a PLAN.md file at the root of the chat session workspace. The companion creates and updates this file with normal file tools. Strawberry parses structured todo blocks and shows the current plan in the chat UI.

​
How plans work

  • One chat session has one canonical PLAN.md.
  • Each sub-agent can have its own PLAN.md.
  • Markdown headings and prose are used for plans, notes, sources, and decisions.
  • Structured todo blocks represent user-visible execution state.
  • Plans stream into the chat UI while they are written.
  • Strawberry reparses the plan after successful file writes or edits.

​
Todo format

Todos use XML-style blocks inside markdown:
Common states include pending, in_progress, and completed.

​
What you see

In chat, Strawberry can show:
  • The plan summary
  • Current todo state
  • Sub-agent progress
  • Related tool activity
  • A link to open the full plan file

​
Ask for review

Tell your companion explicitly when you want it to pause after drafting an approach:
You can then approve or revise the approach in chat.

​
Best practices

  • Ask for a plan when the task has multiple phases, dependencies, or risk.
  • Keep plan todos specific and testable.
  • Ask Strawberry to update the plan when scope changes.
  • Use plans for work you may need to resume later.