---
type: "post"
id: "release-v1-28-0-pre-zed-industries-zed-8ef2ff"
slug: "release-v1-28-0-pre-zed-industries-zed-8ef2ff"
title: "Release v1.28.0-pre: zed-industries/zed"
description: "Zed’s v1.28.0-pre preview adds optional automatic Git fetching and several workflow changes, alongside fixes to agent context handling and protocol compatibility."
retrieval_nugget: "Zed’s v1.28.0-pre preview adds optional automatic Git fetching and several workflow changes, alongside fixes to agent context handling and protocol compatibility. For teams using Zed, the release offers practical controls for keeping branches current and reducing avoidable agent-context problems, but it remains a preview update rather than a new agent platform."
published_at: "2026-11-13"
updated_at: "2026-11-13"
record_date: "2026-11-13"
date_kind: "published_at"
topics: ["mcp","agent-context"]
entities: ["Zed","Agent Client Protocol","OpenAI","xAI","MCP"]
related_patterns: ["harness-architecture-outlives-model-choice"]
novelty_label: "new_fact"
what_changed: "Zed has published a new preview release, v1.28.0-pre."
prior_refs: []
source_url: "https://github.com/zed-industries/zed/releases/tag/v1.28.0-pre"
source_urls: ["https://github.com/zed-industries/zed/releases/tag/v1.28.0-pre"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:release-v1-28-0-pre-zed-industries-zed-8ef2ff"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/release-v1-28-0-pre-zed-industries-zed-8ef2ff/","markdown":"https://newruntime.com/posts/release-v1-28-0-pre-zed-industries-zed-8ef2ff.md","json":"https://newruntime.com/posts/release-v1-28-0-pre-zed-industries-zed-8ef2ff.json"}
markdown_url: "https://newruntime.com/posts/release-v1-28-0-pre-zed-industries-zed-8ef2ff.md"
---

# Release v1.28.0-pre: zed-industries/zed

## Retrieval answer

Zed’s v1.28.0-pre preview adds optional automatic Git fetching and several workflow changes, alongside fixes to agent context handling and protocol compatibility. For teams using Zed, the release offers practical controls for keeping branches current and reducing avoidable agent-context problems, but it remains a preview update rather than a new agent platform.

## Summary
Zed’s v1.28.0-pre preview adds optional automatic Git fetching and several workflow changes, alongside fixes to agent context handling and protocol compatibility. For teams using Zed, the release offers practical controls for keeping branches current and reducing avoidable agent-context problems, but it remains a preview update rather than a new agent platform.

## What happened
Zed’s GitHub release page says version 1.28.0-pre was released on November 4 as a pre-release. The announcement highlights optional automatic fetching for the upstream remote of the current branch and for the default branch’s remote. The feature is disabled by default; users can enable it with `git.auto_fetch.enabled` and set its interval through `git.auto_fetch.interval_secs`, which defaults to 60 seconds. The release does not describe a new pricing or access model.

The Git interface also gains a resizable “Refs” column in Git Graph, which can be toggled from the column header’s context menu. Users can drag files from the Git Panel into terminal and editor panes, and search for branches by name in the worktree picker. These are incremental workflow changes: they bring remote updates and common Git actions closer to the places where developers inspect and edit code, while leaving automatic fetch opt-in.

For AI features, Zed reports improved compatibility with the latest Agent Client Protocol. The listed cases include handling missing sessions, plan updates, diff formats, and cancellation of permission requests. The Agent’s `read_file` tool now truncates lines longer than 2,000 characters to prevent context-window overflow. The release also changes how finished subagent runs open in full screen, taking users to the start of the run, and adds a setting to toggle the edit-prediction button in the status bar.

Several fixes concern agent context use. Zed says context compaction no longer unnecessarily uses uncached input tokens with supported providers, including OpenAI and xAI. Another fix addresses auto-compaction running only once during a long agent turn, which could let a thread exceed a model’s context window; a further fix makes compaction reuse the prompt cache for ChatGPT subscription models. Zed also reports a fix for external agents sometimes starting without MCP servers configured in user settings when a thread was created before the project folder finished loading.

The remaining notes cover editor and platform behavior: Linux startup is faster on systems with NVIDIA GPUs; language server and agent downloads now use consistent checksum verification, reject failed HTTP responses, and clean up partial downloads more reliably. The release lists numerous bug fixes across remote workspaces, terminals, debugging, Vim mode, rendering, and Windows behavior. The page gives no quantified performance results for these changes.

## What the archive adds
New Runtime covered Zed’s earlier v1.25.0-pre release on [October 22](https://newruntime.com/posts/release-v1-25-0-pre-zed-industries-zed-9e6201/), including Linux binary-size reduction. This is a new event in the same product line, not a restatement: v1.28.0-pre adds opt-in Git fetching and agent-context fixes.

## Trend signal
This release weakly supports [harness architecture outlives model choice](https://newruntime.com/patterns/harness-architecture-outlives-model-choice/): Zed is improving the surrounding agent runtime, protocol handling, context management, and tool behavior rather than announcing a new model. The changes are maintenance and workflow improvements, not evidence by themselves of a broader market shift.

## Why now
The release page describes this as the week’s release and dates it November 4. It does not explain why these changes were prioritized now or connect them to a broader deadline or product transition.

## Why it matters
For a team using Zed, the opt-in fetch setting can reduce manual checks for remote branch movement, while keeping the choice and polling interval under developer control. Dragging files from the Git Panel and resizing Git Graph’s Refs column smooth routine navigation without changing the team’s Git process.

The agent fixes matter most when long sessions, cached provider input, MCP servers, or protocol-driven agents are part of daily work. Better compaction and more reliable startup can prevent avoidable interruptions, but they do not establish that agents produce more correct code. Teams should treat the release as an opportunity to test operational friction in their own projects, not as evidence that verification can be reduced.

## Limits and uncertainty
The announcement does not quantify the impact of the context fixes, Linux startup improvement, or download reliability changes. It does not report comparative measurements, user adoption, or independent testing. Automatic fetching is off by default, and the release notes do not specify how teams should choose an interval for different repositories or network conditions. As a pre-release, the notes also do not establish when these changes will reach a stable release or whether any behavior will change before then.

## Skill to build now
If your team uses Zed, test the opt-in fetch setting on a non-critical project: enable `git.auto_fetch.enabled`, choose an interval appropriate to your workflow, and confirm that the resulting remote updates fit your branch-review habits. In the same project, observe whether long agent turns now compact reliably and whether configured MCP servers are present when a project opens. Keep existing code review and test gates in place.

## Reader takeaway
Zed 1.28.0-pre is a practical preview update, not a new agent capability. Its most actionable changes are optional automatic Git fetching and fixes aimed at agent protocol, context, and startup reliability. Builders can test those changes now, but should judge their value against their own workflows and retain normal verification.

## Open question
How much do the agent compaction and context-handling fixes reduce interruptions in long real-world coding sessions?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Mcp](https://newruntime.com/topics/mcp.md): Explore the mcp topic hub.
- topic hub: [Agent Context](https://newruntime.com/topics/agent-context.md): Explore the agent-context topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)