Do you have plan to add/open Editing Tool?

[yunfan]

thanks for this powerful implementation, i used to had such idea too and had build a ts prototype cowork with google's ai , from my view, there should be another tool also follow this pattern, that is editing the repo by tree-sitter based path, so it will made AI code editing more precise and auditable.

it was understandable that you choose not open this tool for enterprise decision, if the tool was released or developed, i think the whole developing style should turned to view based solution, especially a touch screen friendly device, for eg, as developer, we could use finger to choose some leaf of the big-tree of the whole project, and unfold it nestly, until match the desired level, and choose this , ask Agent to change, the message would include the choosing path which might be a mixture of file path and in-file path

[thegdsks]

Interesting idea. Tree-sitter paths for editing is something I've thought about too. The hard part is making the edit operations reliable enough that you'd trust them in a real workflow. Parsing is solved, but writing back to the right location without breaking surrounding code is a different problem. he touch/visual tree navigation concept is cool. If you have that TS prototype anywhere I'd be curious to see it.

Short, shows you read it carefully, invites continued conversation without committing to anything.

[yunfan]

my prototype has not done editing stage too, it was a very primitive prototype which i had done with the help of google search's ai mode , if you want to check the code here is the link https://cnb.cool/geek42.info/asttools

and according to my further conversation with google, there were some tool could allow it, so its possible to implement , that's why i guess you guys had that at the beginning, and if you look at how modern editor use the lsp feature, you could see they can locate the code block precisely in the file, that means they could also replace them into another generated code block, in our case , that's the patching tree

google told me that its called Structured Editing, not new concept

[thegdsks]

thanks for sharing the repo. opened an issue to track this as a potential feature: #25

cross-file editing with tree-sitter paths would pair well with the dependency graph stacklit already generates. no timeline but worth scoping out.