You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Edit a command in the permission card before approving it #509
Devin's permission cards let you click the command to edit it before approving, plus a "wand" action that takes a plain-language change request and has a fast model rewrite the command for your review.
Why this matters for Solenta: today the answer set is approve / reject / allow-always (#477, #479). Real-world approvals are often "yes, but": the agent proposed rm -rf dist && npm build and you want to approve only npm build. Editing in place is faster than rejecting and re-prompting, and it teaches the adapter nothing spurious.
Scope:
Permission card: make the proposed command an editable text field; approving runs the edited command, not the original.
Implemented on coder/fork-edit-a-command-in-the-permission-ca-0b8a50.
v1 (no wand):
Bash/shell permission cards show the proposed command in an editable field. Accept / Accept all run whatever is in the field.
threads.respondPermission takes updatedCommand. The runner merges it into command/cmd/script only, so Edit/Write cannot grow a command by accident. Empty edits throw without consuming the prompt.
Transcript event records both sides: Allowed (edited): rm -rf dist && npm build → npm build.
Allow-always after an edit keys Claude addRules.ruleContent on the edited prefix (npm build:*), never the original and never whole-tool. Unedited Accept all is still whole-tool — that's Allow-always is a command prefix, not the whole tool #479.
Inbox (#291) should call the same IPC with threadId + updatedCommand; PermissionPrompt in ThreadView is the card to extract.
Shipped in this thread: editable command on the permission card, original+edited audit event, allow-always after edit keys the edited prefix. Wand rewrite left for a follow-up.
Activity
currentbits commentedon Aug 20, 2026
Implemented on
coder/fork-edit-a-command-in-the-permission-ca-0b8a50.v1 (no wand):
threads.respondPermissiontakesupdatedCommand. The runner merges it intocommand/cmd/scriptonly, so Edit/Write cannot grow a command by accident. Empty edits throw without consuming the prompt.Allowed (edited): rm -rf dist && npm build → npm build.addRules.ruleContenton the edited prefix (npm build:*), never the original and never whole-tool. Unedited Accept all is still whole-tool — that's Allow-always is a command prefix, not the whole tool #479.Inbox (#291) should call the same IPC with
threadId+updatedCommand;PermissionPromptin ThreadView is the card to extract.currentbits commentedon Aug 20, 2026
Shipped in this thread: editable command on the permission card, original+edited audit event, allow-always after edit keys the edited prefix. Wand rewrite left for a follow-up.
Untrack core/dist symlink swept in by the #509 merge