mixa/zed

Files

gcp-cherry-pick-bot[bot] f3d84f0bc9 Include EditAgent's raw output when inspecting thread (cherry-pick #30337 ) (#30341 )

Cherry-picked Include `EditAgent`'s raw output when inspecting thread
(#30337)

This allows us to debug the raw edits that were generated when people
report feedback, when running evals and when opening the thread as
Markdown.

Release Notes:

- Improved debug output for agent threads.

Co-authored-by: Antonio Scandurra <me@as-cii.com>

2025-05-09 12:02:17 +02:00

docs

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

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

src

Include EditAgent's raw output when inspecting thread (cherry-pick #30337 ) (#30341 )

2025-05-09 12:02:17 +02:00

.gitignore

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

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

Cargo.toml

context_store: Refactor state management (#29910 )

2025-05-05 21:36:12 +02: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

Introduce a new StreamingEditFileTool (#29733 )

2025-05-01 17:37:43 +02: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