Computer Use tasks should enter temporary auto mode and avoid repeated orchestration delays #668

Computer Use requests activate the native control skill but leave the CLI in its previous interaction mode. In default mode, ordinary native actions can stop at approval prompts; in plan mode, input tools can be unavailable. This interrupts a multi-step native task.

Expected behavior: enter the existing auto mode while a Computer Use task runs, then restore the previous mode after success, failure, cancellation, or provider recovery. Preserve explicit restricted/dry-run flags, denied tools, hooks, OS permissions, and deliberate mode selections made during the task. Cover native actions discovered after the first model request as well as explicit GUI intent. Apply the same CLI contract on macOS, Windows, and Linux.

Implementation and evidence scope:

• Add failing regressions before changing the shared instruction/mode and tool-authorization paths.
• Verify real built-terminal startup, task completion, mode restoration and interruption.
• Measure managed MCP startup, warm round trips, observation, input and verification independently; implement measured orchestration improvements without changing the driver protocol.
• Keep native driver optimization proposals separate from implemented CLI changes and distinguish hosted cross-platform CLI coverage from native desktop evidence.

The installed native engine is currently pinned to 0.28.2. This issue does not authorize an unqualified engine replacement or claim that a Weka controller already exists.