Tutorial

Keep a project plan across coding-agent sessions

Resume a project in a new Claude Code or Codex session using the same local KaidoPlan file.

Put the plan where both sessions can find it

Keep the .kaido file in a stable local folder and tell each coding agent its exact path. If you move to another machine, transfer the file through your approved workflow first. The plan does not synchronize itself. For the example below, download the public sample and run the commands from its directory.

kaidoplan task list --file release-demo.kaido --lang en
kaidoplan schedule path --file release-demo.kaido --lang en
kaidoplan violations --file release-demo.kaido --lang en

Give the next session a narrow brief

Ask it to open the plan, identify the task closest to blocking release, and cite the task ID and any constraint in its reply. Tell it to inspect the file without making changes. This gives you something to check against the app instead of relying on a previous conversation summary.

Save and verify approved changes

If you decide to update the plan, save the change and have the next session read the same file again. Verify task state and schedule impact. Keep design rationale, unresolved decisions and implementation links in your handoff note; reference the plan from that note so another agent can reconstruct both the dates and the reasoning.