Allow approval with optional guidance for future actions #5187

Describe the feature or problem you'd like to solve

Allow “Yes” on permission prompts to include optional guidance for future agent actions and Assisted permission decisions.

Proposed solution

In the permission prompts I encounter, “No” is the only option that lets me send explanatory text back to the agent. Sometimes I want to approve the action exactly as proposed while also explaining how similar commands should be approached in the future.

Let me choose “Yes” and optionally add that guidance. The pending action should be approved unconditionally and run unchanged. The accompanying text should be available to both the agent when planning subsequent actions and Assisted permission mode when evaluating subsequent requests.

This would let me communicate intent at the moment I’m reviewing an action, without rejecting something I actually approve. It is not conditional approval of the current action or blanket approval of future actions.

Example prompts or workflows

In each example, the pending action is approved as-is. The accompanying guidance is for future actions, not a request to modify or reconsider the current command.

1. Guide how similar commands are constructed. Approve a Git staging command with: “Yes. Next time, stage specific file paths rather than the whole working directory.” The current command runs unchanged; the agent receives guidance for subsequent commands.
2. Explain the scope of my intent. Approve a dependency installation with: “Yes. Installing dependencies needed to run this project’s tests is part of the task. Ask me before adding unrelated packages or installing tools globally.” That context is available to the agent and Assisted permissions for later installation requests.
3. Explain why an exception is acceptable. Approve a command outside the sandbox with: “Yes. This test needs access to the local service outside the sandbox. That doesn’t mean other commands should run outside it.” Subsequent decisions can take that reason into account rather than treating this approval as broad permission.

Additional context

No response