@github/copilot 1.0.79

on Node.js NPM

2026-08-10

• The /sandbox configuration dialog shows where sandbox settings are stored in settings.json
• Add support for enterprise allow-auto-only policy so /allow-all auto works while full allow-all remains blocked.
• Allow enterprise-managed sandbox policy to enforce a proxy URL while credentials remain user-controlled
• A tool directory inside your workspace that is on PATH (.venv/bin, node_modules/.bin, an in-repo GOPATH) no longer turns that part of the workspace read-only in the sandbox
• The /sandbox configuration dialog groups the git, gh, and (on macOS) keychain settings under a new Auth tab, and the settings keys moved from sandbox.gitAuth/sandbox.ghAuth to sandbox.auth.git/sandbox.auth.gh. There is no migration: the old keys are ignored in settings files, and SDK requests that still send them are rejected as invalid rather than ignored
• Added a worktreeBaseRef setting that controls whether /worktree, /worktree new, and --worktree start from HEAD or the remote default branch. All three now default to HEAD; previously --worktree started from the remote default branch.
• Model picker groups models into Recent, Recommended, New, and other sections, and Shift+Tab switches grouping views.
• Large monorepos now use tgrep (trigram-indexed grep for fast regex search in large codebases) instead of ripgrep
• Agent Plugins spec plugins can now ship extensions under a com.github.copilot/extensions/ directory
• Add support for the kimi-k3 model
• Combine --plan with --mode autopilot to plan first and then implement without waiting for approval
• The /app command now opens the current session in the GitHub Copilot desktop app instead of landing on Home with the wrong folder (requires GitHub Copilot app 1.1.3 or later)
• On macOS, a sandbox read-only path nested inside a writable one now stays read-only instead of inheriting the write permission from the wider path
• On macOS, sandboxed commands can use UNIX-domain sockets again, so tools that talk over a local IPC pipe (tsx, vite, esbuild, jest workers) no longer fail with listen EPERM
• Sandboxed commands work when the working directory lives on a Windows Dev Drive
• /theme now only shows its deprecation notice for a valid color mode, so a mistyped mode no longer suggests an invalid command or hides the notice from your next valid /theme.
• Sandboxed git now authenticates to Azure DevOps, GitHub Enterprise Server, GitLab, and other non-GitHub remotes you have stored HTTPS credentials for
• Ask user multi-select prompts include an Other option for free-text answers
• Improve teleported subagent /tasks navigation with nested tree browsing, current/all and finished-task filters, and a live timeline you can steer
• A rare internal delay no longer prints a diagnostic warning on top of the interactive UI
• A failed session-history load no longer leaves the timeline permanently empty: the failure was silently discarded, so the transcript stayed blank for the rest of the session with nothing logged. It is now retried, and reported in the transcript and the log if it still fails
• Resuming a long session no longer collapses the timeline's scroll range while history renders in the background: entries that had not finished rendering were published as if they did not exist, so the scrollbar and scroll position jumped until the background render caught up
• Manage multiple concurrent sessions from the Sessions tab and sidebar
• Sandboxed wrapper builds (make and friends) get the dev tool caches their recipes need, based on the build manifests in the working directory
• Prompt pinning is off by default; set pinnedPrompts to true to enable it.
• Sandboxed commands can reach the network again on recent Windows builds, where every outbound connection was blocked even with outbound access enabled and no proxy configured
• Plugin custom agents honor deferred-tool-loading frontmatter
• Use /worktree new to start a new session in a new worktree
• A sandbox that cannot start an MCP server now fails in seconds instead of stalling the session, and sandbox startup failures for both MCP and language servers now say the sandbox was at fault and how to fix or opt out of it
• Login links are clickable during web and device-code sign-in
• Pin the current prompt one row higher, in the row the tab bar already reserves, so it keeps the shape of the prompt it copies while costing the timeline one row less
• Leave the pinned prompt off by default on terminals under 30 rows, where it would crowd the output; set pinnedPrompts explicitly to override at any size
• Compute /context attribution against the Auto-resolved model so token totals are accurate for Free/Student users
• Disabling an extension no longer breaks elicitation, canvases, or tool permission prompts for other extensions
• A prompt stashed with ctrl+s now stays with the session it was typed for, so switching away and back and pressing ctrl+s restores it instead of finding it gone
• On Linux, searches and most shell commands blocked by the sandbox now offer to re-run outside it
• BREAKING: the sandbox setting allowDevToolCaches is renamed allowDevToolAccess, since it grants dev-tool config and registries too, not just caches. The old key is no longer read and is ignored silently, so an existing false opt-out reverts to the default (on). Rename it in settings.json and in any managed/MDM policy.
• Add /sandbox policy to show effective sandbox paths, denials, and network access
• Queue prompts, shell commands, and supported slash commands in local sessions to run in order after the current task finishes
• Set "autoUpdate": true on an extraKnownMarketplaces entry in your user settings to auto-update its plugins at session start
• /sandbox tags inactive settings as (disabled) and explains why they are locked, and documents dev tool caches in copilot help sandbox
• Show "pending · ctrl+c to cancel" for in-flight steering prompts
• Make /model session-scoped by default, and use /config model to set defaults for future sessions.
• Pin the current prompt as a single line instead of a three-row framed block, so it reads as chrome and returns rows to the timeline; with the tab bar on it sits directly below the tabs and costs the timeline nothing