Skip to content

1.0.84-2

Pre-release
Pre-release

Choose a tag to compare

@copilot-cli-release-app copilot-cli-release-app released this 08 Sep 13:50
6785561

New

  • Vim mode is now available to everyone. Turn it on with /vim or by setting editorMode to vim for modal editing in the composer, with the current mode shown while you type.

Improved

  • On supported Windows sandbox policies, interactive shell commands now record blocked accesses. One approved escalation retries with file and process restrictions recording instead of blocking while network policy remains active, then falls back to the disclosed full bypass only if still blocked
  • Speed up startup when resuming an existing local session by its exact UUID with --resume

Fixed

  • ctrl+h no longer deletes a whole word in tmux, screen, and remote sessions that carry a Windows Terminal WT_SESSION from elsewhere. As an accepted tradeoff, ctrl+backspace now deletes a single character in those sessions — including a genuinely local Windows tmux or screen pane — where ctrl+w still deletes a word
  • MCP servers now see the same copilot-cli client identity when you add a server and when a session connects, carrying the shipped CLI version instead of 0.0.0
  • Interactive mode starts and submits the initial prompt when using --auth-token-env
  • Use /settings taskbarPresence false to disable Windows taskbar session status. Loader-managed sessions restart immediately; standalone sessions require a manual restart.
  • Pressing Escape once cancels MCP inference approval prompts once
  • MCP reload summary shows servers still starting after timeout
  • Initial prompts start immediately for Entra-authenticated sessions while token refresh runs in the background.
  • Choosing approve-for-location now persists tool approval to avoid repeat prompts
  • Large sessions resume without freezing the interface during context token counting
  • Configured hooks keep running after an extension restarts instead of silently stopping and later denying every tool call; the extension's own callback hooks resume once it re-registers
  • The allowManagedHooksOnly policy now also blocks extension-registered preToolUse, postToolUse and postToolUseFailure callbacks, which previously bypassed the managed-only lockdown that every other hook event already applied