Report · marked 26 Aug 2026
zed-industries/zed
An agent can work here, but it will waste turns finding its footing.
Rust · 89,208 stars · 4,265 files · branch main
60
/100
B-
Instructions
15/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup
10/20Whether an agent can install the project and get it running without a human. Losing marks on discoverable commands and environment config.Verification loop
18/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist.Context economy
9/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability
7/10How quickly anything new can orient itself. Losing marks on license.
Higher is better. Accent marks what is costing you most.
Fix these first
01
Instruction quality
Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.
02
Discoverable commands
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
03
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
The full marking
Every deduction below names the file or setting it came from.
Instructions 15/27 B-
Whether the repo tells an agent how to behave before it starts guessing.
✓Agent instruction file
12/12
AGENTS.md is present, which is the format the most tools read.
Also found: CLAUDE.md
✗Instruction quality
0/12
Present but too thin to change an agent's behavior.
Worth fixing: it's under 200 characters, which is closer to a placeholder than instructions; it never states a build, test, or run command; has no headings to structure it; has no code blocks.
✓README as an entry point
3/3
README has a clear getting-started section.
Setup 10/20 C+
Whether an agent can install the project and get it running without a human.
✓Deterministic install
6/6
cargo.lock pins the dependency tree.
Found cargo.lock
✗Discoverable commands
0/6
No declared commands. An agent has to infer how to build and run this from the file tree.
Declare the handful of commands that matter in package.json scripts, a Makefile, or a justfile. Naming them turns guesswork into a lookup.
✗Environment config
0/4
Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
✓Pinned runtime version
2/2
The language runtime version is pinned.
Found rust-toolchain.toml
✓Reproducible environment
2/2
compose.yml gives a known-good environment.
Verification loop 18/22 A-
Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.
✗Tests exist
4/8
97 test files against 1964 source files.
Coverage is thin enough that an agent can break real behavior and still see green.
e.g. crates/agent/src/tests/mod.rs, crates/agent/src/tests/test_tools.rs, crates/agent/src/tools/evals/fixtures/zode/react_test.py
✓Test command is discoverable
7/7
An agent can find and run `cargo test`.
✓Continuous integration
4/4
46 GitHub Actions workflows define what "passing" means.
✓Lint and format rules
3/3
clippy.toml encodes the house style.
–Static type checking
n/a
Not applicable — the Rust compiler type checks every build.
Context economy 9/20 C
Whether the repo fits in a context window, or fights it.
✓No committed build output
6/6
No generated directories committed.
✓.gitignore hygiene
3/3
.gitignore covers 49 patterns.
✗File sizes fit in context
0/6
104 source files are over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
crates/editor/src/editor_tests.rs — 1362KB
crates/agent/src/tools/evals/fixtures/disable_cursor_blinking/before.rs — 774KB
crates/workspace/src/workspace.rs — 697KB
✗Repository weight
0/5
About 508MB checked out. Large enough that cloning and searching are both slow.
Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.
Here is your AGENTS.md
Drafted from what is actually in this repository: the install
command from your lockfile, the commands you already declare, your real directory layout. Anything
marked TODO needs a person. Save it at the root as AGENTS.md.
# AGENTS.md Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter. ## Setup ``` cargo build ``` ## Commands ``` cargo test # run the test suite ``` ## Layout - `crates/` 1860 source files - `tooling/` 63 source files - `script/` 22 source files - `extensions/` 9 source files - `docs/` 5 source files - `nix/` 3 source files ## Conventions - Tests live alongside the code they cover, following `crates/agent/src/tests/mod.rs`. - CI defines what passing means. See `.github/workflows/add_commented_closed_issue_to_project.yml`, and keep it green. - TODO: add the two or three conventions a newcomer always gets wrong here. ## Gotchas - `crates/editor/src/editor_tests.rs` is 1362KB. It will not fit comfortably in context, so read it in parts. --- Drafted by agentreadme.com from what is in this repository. Everything marked TODO needs a human. Check it in as AGENTS.md at the root.
Open the raw markdown
or
curl -o AGENTS.md agentreadme.com/draft/zed-industries/zed.md
Show the mark
The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.
[](https://agentreadme.com/zed-industries/zed)Other Rust repositories, marked
Think this mark is wrong?
Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.