Zed v0.229.0: 1M Context Windows Are Now Live for Builders

Here at industry sources, we tracked Zed's latest pre-release, and the headline feature is clear: full support for Claude's new 1M context window via bring-your-own-key (BYOK) authentication. This applies to both Claude Opus and Sonnet models. For builders, this means you can now feed entire codebases or complex documentation into your AI assistant without token fragmentation.

Beyond the Claude integration, Zed v0.229.0-pre ships meaningful git panel improvements. You now get uncommitted change count badges at a glance, file type icons for faster visual parsing, and a multi-cursor alignment action that addresses a long-standing friction point in multi-line editing. The image viewer also gained pinch-to-zoom support - a smaller feature, but useful if you're reviewing designs or screenshots embedded in your project.

• Claude Opus and Sonnet 1M context window available via BYOK (no API cost gatekeeping)
• Git panel now displays uncommitted change counts without requiring panel expansion
• File type icons reduce cognitive load when scanning uncommitted changes
• Multi-cursor alignment action simplifies coordinated edits across lines
• Image viewer pinch-to-zoom improves touchpad and trackpad workflows

The 1M context window is not incremental. At this scale, you can load an entire small-to-medium codebase, related documentation, and architectural context into a single conversation. For builders working on code generation, refactoring, or documentation tasks, this eliminates the context window roulette that has defined recent AI-assisted development.

Zed's BYOK implementation is the right move. It means no quota limits, no rate-limiting surprises, and predictable costs if you're already paying for Claude API access. Developers who've been frustrated with context fragmentation across multiple tool switches now have a unified, high-context environment. The friction of 'should I use Claude in VSCode, or Zed, or the web UI' resolves in Zed's favor if you're willing to standardize there.

The git improvements signal that Zed is maturing as a primary editor, not a specialized AI tool. Uncommitted change badges and multi-cursor alignment are the kinds of quality-of-life improvements that compound. Builders who've maintained VSCode as their primary because 'Zed isn't quite there yet' now have fewer objections.

• 1M context eliminates token budgeting within a single conversation
• BYOK removes vendor lock-in and cost surprises
• Git improvements address editor-level workflow pain, not just AI features
• Unified high-context environment reduces tool-switching overhead

If you're already using Zed: test the 1M context with a real codebase section. Load your project's core module plus related tests, plus the relevant docs, and observe the difference in AI response quality. You'll likely find that Claude can now provide more contextually accurate refactoring suggestions and generate code that doesn't contradict patterns elsewhere in your codebase.

If you're still primarily in VSCode: this update deserves a migration assessment. Zed's performance on large files, its GPU-accelerated rendering, and now its native high-context AI support stack up against VSCode's plugin ecosystem. For teams considering a standardization move, v0.229.0-pre is a good checkpoint - the editor is genuinely ready for production workflows.

Regardless of editor: if you have Claude API access and haven't yet, set up BYOK credentials wherever you're using Claude. The 1M context window is the next frontier in AI-assisted development. Token limits have been the bottleneck; that constraint is now lifted for builders who take the step.

• Test 1M context with a real multi-file refactoring task
• Assess Zed migration cost vs. VSCode if you're managing large teams
• Set up BYOK for Claude access to avoid context window gatekeeping

Zed's focus on 1M context support underscores a shift in how editors compete. Raw editing performance and plugin ecosystems are table stakes; the differentiator is now AI integration depth. Zed is betting that builders will standardize on an editor that makes high-context AI workflows frictionless. This isn't a standalone strategy - it's Zed positioning itself as the IDE for AI-augmented development.

The git panel improvements are equally significant as a signal. They show Zed recognizing that AI features alone don't replace editor maturity. Builders won't switch to an editor for a feature; they'll switch if the entire workflow feels native. Uncommitted change badges and alignment actions are mundane, but they're the foundation that makes an editor sticky. The momentum in this space continues to accelerate.

• High-context AI integration is becoming a primary editor differentiator
• Zed is positioning as the native environment for AI-augmented workflows
• Maturity signals matter: git improvements show Zed building for retention, not just adoption