Terminal safety denial turns session recovery into a dead end #5123

After a Windows restart, I asked Copilot CLI to restore my existing sessions in named Terminal tabs. Instead, the interaction became a lengthy loop of refusals and manual instructions. This is unacceptable friction for a basic recovery task.

Observed on October 12, 2026, with Copilot CLI 1.0.95 on Windows ARM64: Computer Use rejected even a read-only get_window_state request for Windows Terminal with: "actions are blocked for this application by built-in safety policy."

Previous restores succeeded through native PowerShell scripts. That does not prove the UI policy recently changed or that native restoration is blocked. The assistant nevertheless repeatedly treated the UI denial as a blanket restoration ban. Both the recovery experience and that misleading explanation need attention.

Please route this to the Computer Use safety and CLI session-recovery owners. Explain the restriction and provide a clearly supported, consent-based recovery path that preserves sessions, tab identity, and a short status recap. Improve tool guidance so assistants distinguish a UI-tool restriction from native CLI capabilities without bypassing safeguards.

Please test the actual restart-to-recovery workflow before shipping changes around it. Users should not have to reverse-engineer tool boundaries while urgently recovering their work.