yenru0/zed

0 Fork 0

Files

T

Ben Brandt 8efa7fdcde agent: Use default tool behavior for subagents (#49706 )

Looking at this more, the map of tools is just for what is available and
all of the filtering happens at runtime. So we can just rely on the
current behavior for the list of tools (it was already a matching set)
and we can simplify all of the code paths again where we were adding
this filtered list.

Release Notes:

- N/A

2026-02-20 11:07:03 +00:00

docs

eval: Add HTML overview for evaluation runs (#29413 )

2025-04-25 17:49:05 +03:00

src

agent: Use default tool behavior for subagents (#49706 )

2026-02-20 11:07:03 +00:00

.gitignore

Add judge to new eval + provide LSP diagnostics (#28713 )

2025-04-14 20:18:47 +00:00

build.rs

Use distinct user agents in agent eval and zeta-cli (#35897 )

2025-08-08 23:26:38 +00:00

Cargo.toml

gpui: Extract gpui_platform out of gpui (#49277 )

2026-02-19 18:57:49 +01:00

LICENSE-GPL

Lay the groundwork for a Rust-based eval (#28488 )

2025-04-10 04:45:27 +00:00

README.md

eval: Add support for reading from a .env file (#29426 )

2025-04-25 15:53:02 +00:00

runner_settings.json

Replace always_allow_tool_actions with tool_permissions.default (#48553 )

2026-02-10 18:57:31 -05:00

README.md

Eval

This eval assumes the working directory is the root of the repository. Run it with:

cargo run -p eval

The eval will optionally read a .env file in crates/eval if you need it to set environment variables, such as API keys.

Explorer Tool

The explorer tool generates a self-contained HTML view from one or more thread JSON file. It provides a visual interface to explore the agent thread, including tool calls and results. See ./docs/explorer.md for more details.

Usage

cargo run -p eval --bin explorer -- --input <path-to-json-files> --output <output-html-path>

Example:

cargo run -p eval --bin explorer -- --input ./runs/2025-04-23_15-53-30/fastmcp_bugifx/*/last.messages.json --output /tmp/explorer.html