Feature Request: Add Option to Explain Rejection

[schmoelder]

When prompted with a command execution request like:

### Waiting for your response:

 execute(cd "<some-path>" && ...)

1.  Allow
2.  Always Allow
3.  Reject

Rejecting the command (option 3) currently offers no way to provide feedback or instructions for alternative actions.
This is limiting when explaining the rejection (e.g., suggesting a safer command or clarifying intent) is critical to avoid loops or miscommunication.
At least mistral-vibe and claude do provide options for this.

[carlos-algms]

ACP schema doesn't support it. RequestPermissionOutcome is cancelled | selected { optionId }. No reason field. See schema.

Maintainers don't seem close to adding it:

• Discussion #221 raised the same gap a year ago. 0 replies.
• PR #895 adds feedback only for file writes, not permissions. Still open.

Zed (lead ACP editor, same authors as Claude and Codex ACP adapters) doesn't have this either. Not even a custom extension.

I'm afraid we won't be able to implement this as well.

[chancez]

The way I handle this today is to send a reply via prompt, then navigate the chat buffer and reject. Perhaps this could be streamlined in some way? Maybe even just a mapping that you can press from the prompt buffer to "send current prompt and reject" or similar.

[carlos-algms]

@chancez, Agree, sounds reasonable.

You submit a new prompt, it rejects the permission request queue, and sends rejections. 👍🏻