Forumics logo Forumics
Issue 01

Forumics ยท Browse by tool

Zed known issues

13 verified issues published.

CLAIM C158 Supported 2026-11-18

GitHub issue #56747 in zed-industries/zed, opened 2026-05-14 by SkeLLLa, records a report that archived ACP sessions keep their MCP server processes alive: after a thread is archived in the Agent Panel, every previously-archived session still has its agent process and all of its MCP child processes running, each holding its own RSS, so memory usage grows monotonically with the number of archived sessions until Zed is fully restarted or each session is explicitly killed; the report was filed against Zed 1.2.3 on Linux.

CLAIM C152 Supported 2026-11-17

GitHub issue #59000 in zed-industries/zed, opened 2026-06-10 by strangemonad, records a report that when a standalone uv project contains an independent inner uv project with its own pyproject.toml, uv.lock and .venv, and the inner project is not a member of the outer one because the outer pyproject.toml has no [tool.uv.workspace] table, uv itself resolves the inner project to its own .venv while Zed selects the outer .venv instead, so Pyright reports Import "cowsay" could not be resolved for packages/inner/main.py; the report was filed against Zed v1.5.5 stable on macOS 26.5.

CLAIM C154 Supported 2026-11-17

GitHub issue #44855 in zed-industries/zed, opened 2025-12-15 by valderman, records a report that when remote editing, Zed is unable to format a buffer that has not been saved to file: opening a new unsaved file, pasting [1,2,3], setting the language to JSON and formatting leaves the file unchanged instead of formatting it to [1, 2, 3], and the report says this is not exclusive to JSON but also happens with at least Python, SQL and Rust; the report was filed against Zed v0.216.0 stable on Linux Wayland Fedora 43.

CLAIM C147 Supported 2026-11-16

GitHub issue #66523 in zed-industries/zed, opened 2026-11-04 by stefano-scarpone-bluvacanze, records a report that when an external agent session (claude-acp) is resumed with session/load after approving a plan with "clear context and use auto mode", Zed reopens the original session only, and the messages after approval are not shown, because the approval creates a new Claude session and the work done after approval lives in that new session, which Zed does not load; the reporter measured the original session with 100 transcript lines and 12 user messages and the new session with 95 transcript lines and 9 user messages; the report was filed against Zed 1.26.2 and 1.27.0 on Windows 11 Enterprise with claude-acp adapter 0.100.0.

CLAIM C136 Supported 2026-11-15

GitHub issue #59159 in zed-industries/zed, opened 2026-06-11 by EV4g, records a report that continuously adding non git-ignored files to a git-synced project, in the reporter's case 200 33 MB .fits files, made Zed start trying to look through the files and use an additional 2 GB of RAM per second, filling up 64 GB of RAM and 64 GB of swap before crashing; memory increased even when the Git window was not open, and after the reporter edited the .gitignore file in a different program Zed stopped requesting 2 GB/s and memory usage went back to normal; the report was filed against Zed 1.6.3 on Pop-OS Cosmic with 64 GB of memory and an AMD HX370 CPU.

CLAIM C103 Supported 2026-11-12

GitHub issue #55200 in zed-industries/zed, opened 2026-04-29 by jakeleventhal, records a report that after uninstalling an external agent (OpenCode / opencode), Zed still opens a new agent thread with opencode selected in the agent picker, though the picker only shows Zed Agent and Codex CLI as available options, and the thread fails immediately with "Failed to Launch / Custom agent server `opencode` is not registered"; the report was filed against Zed 0.233.10 on macOS 26.5.

CLAIM C107 Supported 2026-11-12

GitHub issue #53015 in zed-industries/zed, opened 2026-04-02 by m-ar-c, records a report that exporting a 468 MB SQL file at the root of a project caused Zed to use a huge amount of RAM and crash the reporter's GNOME session, reproduced as soon as Zed opened because the Uncommitted Changes tab was restored, and reproducible just by opening that tab, with RAM continuing to grow after closing it, and the problem gone if the file is removed; the report was filed against Zed v0.230.0 on Linux Wayland Debian sid with 15.3 GiB of memory.

CLAIM C101 Supported 2026-11-11

GitHub issue #59955 in zed-industries/zed, opened 2026-06-26 by lixiaoyan, records a report that Zed always displays stale cached content for files under .git instead of the version on disk, demonstrated by writing "a" to .git/COMMIT_EDITMSG, opening it in Zed, closing the tab, writing "b" to the same file, and reopening it in Zed; that the issue significantly affects users who configured VISUAL="zed --wait", since every commit or interactive rebase can potentially show stale file content; and that Zed should always display files under .git using the latest content. The report was filed against Zed v1.9.0+preview on macOS 26.5.1.

CLAIM C077 Supported 2026-11-09

GitHub issue #59401 in zed-industries/zed, opened 2026-06-16 by chrrity, records a report that large tool outputs from grep and read_file are sent without truncation in Zed agent threads, that accumulated raw tool outputs exceeded 1M tokens by the fourth or fifth user message in the reported thread, that the thread JSON was 13.3 MB uncompressed with 99.7 percent raw tool execution output, and that a single grep call returned 5.2 million characters which gets stored and re-sent on every subsequent request. yeskunall replied in the thread that a lot of what was identified had actually been addressed since version 1.6.3, and the author clarified in a comment the same day that the source code analysis was on a stale local checkout, while stating the crash itself is real and the remaining gap is grep and read_file lacking output truncation.

CLAIM C043 Supported 2026-11-07

GitHub issue #58190 in zed-industries/zed, opened 2026-05-31 by martin-c, records a report that on a 64 GB M1 Max Mac Studio running Zed 1.4.4 stable on macOS 15.6.1, a single Zed process grew to 391 GB resident and drove the whole system into terminal memory pressure, that the growth coincided with a continuous main-thread hang lasting at least about 2 hours, and that the reporter argues no single subsystem should be able to consume several times physical RAM and take down the OS.

CLAIM C050 Supported 2026-11-07

GitHub issue #62716 in zed-industries/zed, opened 2026-08-16 by ahjota, records a report that starting a Factory Droid thread from the Agent Panel in Zed v1.15.0 on macOS 14.7.2 (arm64) exits with status 1, that the package bin resolves to a 120MB Mach-O native binary after a postinstall step replaces the JS shim with a hardlink to the native platform binary, and that running the bin directly works while launching it through Node fails, with the expected behavior that Zed execute the resolved bin path directly.