Zed's Terminal Threads Let Claude Code Users Dodge a 30x Price Hike
Zed v1.3.5 lets you run Claude Code, Amp, and any CLI agent as a managed thread in the editor sidebar, a timely escape hatch from Anthropic's new ACP pricing.
Takeaways
- Terminal Threads are live in Zed v1.3.5: Run any CLI agent (
claude,amp,codex) as a managed thread in the editor sidebar. - Key escape hatch from ACP pricing: Running Claude Code via the CLI (not ACP) still draws from your existing Claude subscription, avoiding Anthropic's new metered credit system.
- Anthropic billing change (June 15): ACP-routed Claude usage now draws from a separate $20–$200/month credit pool at full API rates, not your flat subscription.
- Unified workspace: Terminal threads appear alongside Zed Agent and ACP threads in the same sidebar, with auto-updating titles and shared keyboard navigation.
- Works for non-agent tasks too: Long compiles, eval runs, or any process you want to keep visible and organized can live in a terminal thread.
- Free and available now: Download Zed or update to v1.3.5+; no additional cost beyond your existing plan.
Terminal Threads are Zed's answer to a problem that has been quietly frustrating agentic developers for months: you can run powerful CLI agents like Claude Code or Amp, or you can have a clean, organized workspace. Until now, you couldn't easily have both. With the release of Zed v1.3.5, that tradeoff is gone.
The Problem With Terminals and Agents
When Zed launched Parallel Agents last month, many users started running multiple agents at once in the same window. But Parallel Agents only worked with Zed's built-in agent and external agents connected through ACP (Agent Client Protocol, Zed's standard for integrating external AI tools). Many developers prefer working with agents in the terminal, and some were already making it work with the existing terminal pane, even though that pane was never designed for managing parallel agent sessions.
Terminal Threads bring those sessions into the same sidebar where Zed already tracks agent work. The result is a unified control plane for every kind of agent work happening in your editor, regardless of whether the agent speaks ACP or just runs in a shell.
How It Works
Open the "New Thread" menu from the + icon in the Agent Panel toolbar and choose Terminal. A new terminal opens in the panel body and appears as its own entry in the Threads Sidebar, just like any other thread. From there, you launch whatever CLI tool you want.
Each terminal is scoped to your project and worktree. Run claude, amp, pi, or any other process you want. The terminal title in the sidebar updates automatically to reflect whatever is running, so you can tell your threads apart at a glance. You get the same keyboard navigation you use for agent threads, and the same notifications when a process needs your attention.
The key behaviors that make this feel native rather than bolted-on:
- Unlimited threads: You can open as many terminal threads as you like, and mix them freely with Zed Agent threads, ACP threads, or both.
- Auto-updating titles: The sidebar entry reflects the running process name in real time, so you always know which thread is which at a glance.
- Notifications: Configure alerts so Zed pings you when a long-running process finishes, without having to watch the terminal. For Amp users, setting the environment variable
AMP_FORCE_BEL=1enables this out of the box. - Non-agent use cases: Terminal Threads are also useful for non-agent work, like keeping long compiles or eval runs visible alongside the rest of your workspace.
The Claude Code Pricing Angle
The timing of this release is not accidental. There is a real economic reason this feature matters right now, and it has to do with how Anthropic is restructuring access to Claude through third-party tools.
On June 15, 2026, Anthropic moved Claude Agent SDK, claude -p, Claude Code GitHub Actions, and third-party agents off the Claude subscription limit onto a separate monthly credit ($20 Pro / $100 Max 5x / $200 Max 20x) metered at full API rates, with no rollover. That includes any Claude Code usage routed through ACP, which is exactly how Zed was previously integrating it.
Before June 15, Claude Agent SDK calls, the claude -p command, Claude Code GitHub Actions, and third-party apps authenticating with a Claude subscription via ACP all drew from the same usage pool as interactive conversations. Zed's AI features that use ACP moved to the Agent SDK credit after June 15. Zed published a transparent post on May 14 documenting the change and noting the workaround: running Anthropic's official claude CLI in a terminal (not via ACP) continues to use subscription limits.
That workaround is exactly what Terminal Threads enable. The new separate monthly credit is sized between $20 and $200 depending on the plan, billed at standard API list rates. For heavy Claude Code users, that could represent a 15-30x cost increase for heavy usage compared to running the CLI directly. Terminal Threads let you keep using the CLI path, and therefore keep drawing from your existing subscription, without giving up the organized sidebar experience.
ACP Is Not Going Away
It would be easy to read this as Zed stepping back from ACP, but the team is explicit that it is not. Agents connected through ACP still offer tighter integration with Zed's editing and review workflows. Terminal Threads give you flexibility. The two are not mutually exclusive.
The honest framing from Zed is that they built Terminal Threads because the editor should work with tools developers already use, not only the ones that speak a specific protocol. Amp's rebuilt CLI is a good example: there is no ACP equivalent of it, so Terminal Threads give Amp and Zed users a much cleaner integration than running them side by side in separate windows.
What It Does Not Do (Yet)
Terminal Threads are a v1 feature. The team is explicit about what is missing. A notable early bug was that Add to Agent Thread did not work when a terminal thread was the active conversation in the panel, though this was patched quickly. More broadly, the feature starts with the core workflow and leaves room for deeper integration later, things like passing terminal output directly into an agent thread context, or richer process management controls.
Terminal Threads are available now in Zed v1.3.5 and later, free to download on macOS, Windows, and Linux. There is no additional cost beyond your existing Zed plan. If you want to share feedback or request features, the team is tracking it in GitHub Discussions.