Why AI coding agents' plans should be committed to the repo, not left in session folders

A developer argues that the plans AI coding agents generate are part of the deliverable and should live in a committed file on the task branch. Claude Code stores its plans in ~/.claude/plans/, a folder cleaned up automatically after 30 days by default, while GitHub Copilot CLI saves plan.md under a per-session folder. Codex's documentation does not say where its plans are stored, so they are assumed to live in the chat itself. Keeping plans with the session means reviewers typically cannot see the reasoning behind a change in the pull request. The author suggests committing the plan so reviewers and agents from any vendor can read and check the code against it.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in