feat(zed): add per-project attribution - #939
Open
Vlaaaaaaad wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TL;DR: add best-effort per-project attribution to Zed. Proof-of-concept follow-up to #480 / #594
Warning
This code was written by LLMs, under the supervision of a so-called developer that spends more time in Pages&Keynote than in an IDE!
Zed Agent Threads can happen in 2 types of workspaces:
codeburnandhomebrew-codeburnandagentsealin the same Zed window. In this case, the project name in Codeburn output will beagentseal, codeburn, homebrew-codeburn(folder names, sorted lexicographically)This LLM-written, human-validated (beware: dumb human) pull request implements the above. Zed Agent Threads without folder metadata remain in the legacy catch-all
zedbucket.Testing
I tested this on one of my devices and I can confirm the single
zedis split into multiple projects:Before:
After (keep in mind I also did a bunch of work in
zedsince I do have some tiny contributions to Zed):This was not a complex setup and I did not have a bunch of work on this machine (no ACP threads, relatively low number of sessions, minimal worktree usage, etc). More testing would be a very good idea!
Notes
Since I am not at all familiar with the
codeburncodebase and patterns, this is more of a proof-of-concept than an actual PR. Please feel free to close this or just treat it as somewhat-relevant-documentation/example for a real implementation — I will not be offended in any way, shape, or form!Relevant Zed references:
PathListserialization format