01 / AI · Analysis
Copilot CLI fixes parallel approvals and task stopping
The update changes approval handling for parallel requests and which shells stop with an agent, while Adobe’s Firefly plan review addresses control before execution.

GitHub announced a fix in Copilot CLI 1.0.109 for repeated approval prompts affecting users who choose to skip further prompts for parallel file operations.
The release notes cover requests included in that approval choice. They also specify changes to stopping attached background shells, addressing what continues running after a user stops an agent.
Adobe announced a way to review an agent’s plan before execution in Firefly. Together, the updates address separate control points: reviewing a plan before work starts, and handling approvals or stopping tasks during execution.
Approval choices across parallel requests
GitHub said the option to skip further approval prompts now approves all requests covered by that choice. The fix addresses parallel file operations that prompted users again despite their earlier selection.
The release notes also list a fix for duplicate shell commands left waiting for approval when parallel subagents—agents handling delegated tasks—request permission. The fix includes cases arising after a session resumes.
Shells that stop with a background agent
GitHub said stopping a background agent through /tasks now also stops attached background shells started by that agent and its subagents. Detached shells continue running.
The release notes also describe a Windows memory fix. Memory freed by the runtime after a turn, a session resume or a session closure now returns to the operating system instead of remaining committed to the process.
Plan review before execution
Adobe said Firefly’s Plan Mode lets users review, edit and approve an agent’s plan before it starts. Users can also let the agent proceed on its own, making plan review a choice before execution.
Adobe’s announcement labels always-on agents for recurring work as a preview and gives no date for general availability. Plan approval and stopping an active task remain separate points of control: the former governs the proposed work before it begins, while the latter governs work already running.