# Edit tool debugging \(\#26637\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/606aa7a78c978967f1a39b0fb0674fc42e1fa41e)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 606aa7a78c978967f1a39b0fb0674fc42e1fa41e

Requested commit: 606aa7a78c978967f1a39b0fb0674fc42e1fa41e

Commit: 606aa7a78c978967f1a39b0fb0674fc42e1fa41e

Tree: 8834c0422cd51cedf9fa5b5a82ff868c5dd3d48c

Author: Agus Zubiaga

Committer: GitHub

## Message

```
Edit tool debugging (#26637)

Adds an `debug: edit tool` action that opens a new view which will help
us debug the edit tool internals. As the edit tool runs, the log
displays:

- Instructions provided by the main model
- Response stream from the editor model
- Parsed edit blocks
- Tool output provided back to main model

The log automatically records all edit tool interactions for staff, so
if you notice something weird, you can debug it retroactively without
having to open the debug tool first. We may want to limit the number of
recorded requests later.

I have a few more ideas for it, but this seems like a good starting
point.


https://github.com/user-attachments/assets/c61f5ce8-08b1-4500-accb-db2a480eb3ab


Release Notes:

- N/A
```

## Parents

- [0081b816fecf59ae7351a14eb7249e600389d508](https://git.cafe/gitcafe/zed/commit/0081b816fecf59ae7351a14eb7249e600389d508?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/606aa7a78c978967f1a39b0fb0674fc42e1fa41e?format=markdown)