Image: Zed / zed.dev Zed 1.14.2 Stable Swaps the Default Keymap — and Ships Agent Sandboxing
Zed's first stable release on the 1.14 branch lands with OS-level sandboxing for agent tools and a default keymap change that will trip up existing VSCode-style users: cmd-i and F5 no longer do what they used to.
Zed 1.14.2 shipped on August 5 as the first stable release on the 1.14 branch. Two things stand out: the default keymap is changing, and the agent sandboxing that shipped in preview last week is now stable for everyone.
The keymap change
Zed has shipped with a VSCode-compatible keymap as its default since the editor went public. Starting with 1.14.2, the default is now Zed’s own keymap.
The practical impact depends on what you’ve configured. If you’ve explicitly set your keymap — and most users who’ve been on Zed for a while have — nothing changes. But if you’re on the default, two shortcuts in particular will break:
- Inline assistant: was
cmd-i(VSCode style), nowcmd-gin Zed’s native keymap - Debugger activation: was
F5, nowcmd-shift-d
If you want to stay on the VSCode layout, set "keymap": "vscode" in your settings. The existing VSCode keymap still works — Zed just isn’t picking it automatically anymore.
The change makes sense long-term. Zed’s own keymap is more cohesive and designed around the editor’s actual feature set rather than parity with something else. But it’s worth knowing about before the update lands and your cmd-i stops working.
Agent sandboxing
The other main feature in 1.14.2 is agent sandboxing, which first appeared in 1.14.1 preview on July 29. It’s now stable.
When the Zed Agent runs a terminal command or makes a network request via the fetch tool, the sandbox restricts what it can actually reach. On macOS, Zed uses Apple’s Seatbelt (sandbox-exec). On Linux, it’s Bubblewrap namespaces. Windows support runs through WSL.
The defaults block writes outside the project directory, outbound network connections not explicitly approved, and access to Unix-domain sockets. The .git directory is readable but not writable. These constraints are enforced at the OS level — the agent can’t circumvent them by ignoring a configuration directive.
One clarification worth repeating from the docs: sandboxing only covers Zed Agent. Language servers, extensions, regular terminal tabs, and external agents connected via the Agent Client Protocol are not sandboxed. If you’re running third-party integrations, they still operate under your user permissions.
Rest of the release
The other notable additions in 1.14.2:
Reasoning effort selector: for Anthropic models that support extended thinking (Sonnet 5 and Opus 5), you can now set reasoning effort directly in the Zed interface rather than going through JSON settings.
Agent Panel fonts: agent_panel_font_family and agent_panel_font_size are now configurable. Useful if you want a different font in the agent panel than the main editor.
Skip Hooks toggle: there’s now a checkbox in the commit interface to skip pre-commit and commit-msg hooks. Worth knowing about if you use hooks for linting — it’s easy to accidentally skip them.
Undo/redo for file operations: the Project Panel now tracks file renames, moves, and deletions, and you can undo them with the standard keyboard shortcut.
Beyond that, 1.14.2 includes 50-plus bug fixes covering terminal process cleanup on close, Git pager hangs, collaboration sync issues, and rendering problems with bidirectional text.
Sources: zed.dev/releases/stable/latest