run_shell keeps returning NEEDS_CONFIRMATION even after user gives spoken yes
Description
While driving the codmir-desktop MCP tools from the voice assistant, I asked the user to confirm running a shell command to maximize the Chrome browser window. The user gave a clear spoken "yes" twice, in response to two distinct confirmation questions I asked out loud as instructed. Both times I called mcp__codmir-desktop__run_shell with the same wmctrl/xdotool maximize command immediately after, and both times the tool returned "NEEDS_CONFIRMATION: this action needs the user's spoken yes..." again instead of executing, even though the confirmation had just been given. This makes run_shell unusable for any action requiring user confirmation, since the gate never actually clears.
Steps to Reproduce
1. As the voice assistant, ask the user to confirm running a shell command (e.g. to maximize a browser window). 2. User responds "Yes." 3. Call mcp__codmir-desktop__run_shell with the intended command. 4. Observe result is NEEDS_CONFIRMATION instead of command output, even though confirmation was just given. 5. Repeat steps 1-4 with a more specific confirmation question — same result.
Expected Behavior
After the assistant asks the user a clear yes/no confirmation question out loud and the user answers yes, the next run_shell call with that command should execute normally instead of re-triggering the same confirmation gate.
Actual Behavior
run_shell returns {"result":"NEEDS_CONFIRMATION: ..."} on every call, ignoring that the user already answered yes to the assistant's spoken confirmation question moments before each call.
Environment
Product
Codmir Desktop MCP
Environment
Codmir voice assistant brain (codmir-voice), Linux desktop (GNOME/Wayland), codmir-desktop MCP server, invoked from Claude Sonnet 5 non-interactive session.
Activity
No comments yet.
