🤖 fix: guide agent to evaluate plan relevance before incremental edits

[ammar-agent]

Problem

When a user requests a new plan for something entirely different from the previous task, the agent keeps referring to and building upon the old plan. This happens because:

1. The plan file persists across different requests (stored at ~/.mux/plans/{workspaceId}.md)
2. When planExists is true, the instruction said: "You can read it and make incremental edits"
3. This biased the agent toward incremental edits rather than recognizing when a fresh start is needed

Solution

Updated getPlanModeInstruction to give the agent clear guidance about evaluating whether the existing plan is relevant:

1. Read first - Agent must read the plan before deciding
2. Evaluate relevance - Explicitly check if it relates to current request
3. Delete if unrelated - Clear guidance to remove stale plans
4. Keep incremental edits - Still available when plan IS relevant

Generated with mux

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.