Plan mode cannot write plan files; painful to iterate.

[babhishek21]

Expected Behavior

Agent in plan mode should be able to write plans to persistent storage. Optionally, let the user configure to write the plans to the project directory's .commandcode/plans/ location.

1. User enabled plan mode (Shift + Tab cycle)
2. User prompts agent to plan how to solve a problem
3. Agent comes up with a plan and writes it to ~/.commandcode/plans/.... Optionally, if user-configured, agent writes the plan to .commandcode/plans/... in the project directory itself.
4. User and agent can iterate on the plan.
5. Plan file is available to peruse at will for the user in their favorite editor.

Actual Behavior

1. When in plan mode, agent supposedly creates a plan file to ~/.commandcode/plans/... but the path doesn't actually exist. This might be due to the fact that plan mode restricts any file changes.

2. The plan is also not entirely readable in the TUI:

• screenshot when plan is not expanded
• screenshot when plan is expanded (Ctrl + o). Note that the entire plan is still not readable.

3. When the agent is asked to write the plans to a user provided location, it warns that it cannot do disk writes in plan mode. The user has to switch out of plan mode, make the agent write the plan, and then switch back to plan mode again to iterate. Additionally, the agent continues to (allegedly) make plan iterations to the system path ~/.commandcode/plans/... (which doesn't exist).

Command Code Version

0.25.7

Operating System

macOS

Terminal/IDE

ghostty

Shell

fish

Additional context

No response

[saqibameen]

Can you confirm that ~/.commandcode/plans/... is not being created? It is supposed to auto create that directory and write to it.

[babhishek21]

There isn't a plan subfolder at all.

[saqibameen]

Thanks for confirming. @vipulgupta2048 can you please take a look at this one?