~“In 2.0 this server now automatically runs as a single background process on your machine.”
?“All MCP servers in 2.0 are opted into code mode by default.”
?“First, we've added background subagents.”
Day 7Users report · 14
›v2 releases shipped without published release notes: the changelog stopped at v1 and the v2 changelog page returned 404, so users had to diff tags. Maintainers closed it on 20 Oct, saying v2 notes are now on the website changelog and in the repository.
›The v2 TUI sometimes ate 24–28 GB of memory in under a minute and was killed; the reporter never saw this on v1.
›The automatic v1-to-v2 migration silently dropped 6,238 older assistant messages across 92 sessions; the reporter recovered them with their own fix.
~“Enabled automatic background-server startup for eligible interactive sessions, with recovery choices when server settings are incompatible.”
?“Added GPT-6 Sol and Luna, including Amazon Bedrock support and migration prompts for older models.”
?“Fixed configured proxy routing for realtime connections and standalone web search, including search redirects.”
Day 7Users report · 6
›A CLI user documents that opening a session now starts a persistent background daemon that keeps running after every window closes, copies a ~374 MB package into the Codex folder and runs an hourly self-updater. They ask for it to be opt-in and share the steps they used to switch it off.
›0.157.0 refuses to start on Windows with a daemon privilege error that says to use a non-elevated terminal or --no-daemon; the reporter says 0.156.1 works.
›0.157.0 would not start on some Windows machines. Maintainers reproduced it and published 0.157.1 as a hotfix.
?“In the Artificial Analysis Coding Agent Index, Copilot Fusion Max scored 60, within two points of Claude Code with Opus 5.5 Max.”
~“GitHub Copilot Fusion is generally available.”
~“Copilot Fusion is available on all Copilot plans in Visual Studio Code, the GitHub Copilot app, GitHub Copilot CLI, and JetBrains IDEs.”
Day 7Users report · 2
›In IntelliJ, Copilot Fusion Standard shows as selected and available, but sending a prompt fails with an unsupported-model error, while a non-Fusion model works. The reporter also saw the CLI say the Fusion alias needs dynamic Auto tiers.
›The Copilot CLI documentation describes a flag for setting the Fusion tier, but the latest public CLI release rejects it as an unexpected argument. A commenter says a feature flag for dynamic Auto tiers resolved their issue and asks where it is documented.