Zed 1.25.2 landed on October 21 with three things worth your attention: the macOS binary is 33% smaller, a security bug that exposed API keys through your machine’s process list is patched, and external agents running over ACP now get context compaction so long sessions stop turning your machine into a space heater. If you’re passing API keys through Zed’s environment variables to external agents, updating isn’t optional.
The Security Fix You Actually Need to Care About #
When developers pass environment variables — API keys, secrets, tokens — to external agents or MCP servers in remote projects, those variables were showing up in the local machine’s process list. Any process with sufficient permissions could read them. A simple ps aux would do it.
This matters more than it sounds. If you’re using Zed’s ACP integration to run Claude Code, Codex CLI, Gemini CLI, or OpenCode in an overnight session, and you’re passing API keys through env vars, those keys were sitting in your process table until the session ended. The fix (tracked as issue #65174) stops Zed from leaking env vars into the local process list when handing off to agents or MCP servers.
This fix lands in a rough week for AI tooling security. If you run overnight agentic pipelines, now is a good time to audit what your tools do with your credentials.
Smaller Binaries Across Every Platform #
The release ships smaller on all three platforms: 33% on macOS, 28% on Windows, and 7% on Linux. The macOS and Windows reductions come from stripping debug symbols from release builds. The Linux reduction builds on the 23% shrink that already shipped in 1.24.2, which used safe identical-code folding and symbol stripping to cut the x86_64 binary from 317 MB to 226 MB.
For most developers, this means a faster download and less disk space. For teams distributing Zed through CI/CD pipelines or containerized dev environments, a 33% smaller binary propagates through every layer of your toolchain.
Context Compaction for Long-Running Agents #
The third change signals where Zed is headed. External agents connecting over ACP now get session notices and automatic context compaction. When a long conversation thread hits the configured token threshold — 90% of the context window by default — Zed summarizes earlier messages and keeps going. A “Context Compacted” entry marks where the rollup happened so you can inspect it. You can also trigger it manually with /compact.
Before this, running an external agent through an overnight session meant watching memory and CPU climb until something broke or you killed the session. Now it does not. This is a direct requirement for any editor that wants to be viable for autonomous agent workflows — not just interactive assistance.
New Models and Quality-of-Life Changes #
Zed added GPT-6 Astra, Claude Opus 5.5, and Claude Fable 5.1 to the Amazon Bedrock provider. Google AI integration now retries automatically when a model is overloaded — useful for anyone hitting rate limits during peak hours. Smaller additions include double-clickable inlay hints and faster SSH connections for remote development.
Why This Release Matters Beyond the Changelog #
Zed is the only major code editor not built on Electron. It renders at 120fps through a custom GPU framework called GPUI, cold-starts in under a second, and uses roughly 280 MB of RAM at idle — compared to 420 MB for Cursor and 3.5 GB for VS Code. The Agent Client Protocol (ACP), co-developed with JetBrains and Apache-licensed, lets any external agent connect to Zed with full multi-file editing and codebase context.
1.25.2 is not a feature release. It is a maintenance release that fixes a real security problem, ships a long-overdue binary optimization, and extends the agent infrastructure. That combination — unglamorous, practical, and executed well — is how you close the gap on Cursor. Full release notes are on zed.dev.