More seamless AI edit application

[nickelser]

It seems that through the /workflow command I can enable a somewhat limited (limited in that it fails to apply about 80% of the time) system where I can directly apply edits from the assistant.

I'd rather not have to do a special command, and instead just take the patches that Claude gives me, which are always in the format of:

# path/to/file
class AddFooBar < ActiveRecord::Migration[7.2]
  def change
    ...

and Zed could figure out if it was a new file, or existing file (ideally matching by name since sometimes it gets the path wrong), and have a button to just apply the changes (sometimes after I've edited them, since I love that I can edit the assistant responses).

My workaround right now is I just navigate to the file, select all, inline assistant, and tell it to "apply the changes we discussed." This has the benefit of being able to describe changes to the assistant output right there (if I need to say, e.g., apply the patch but remove the logging you added), but ideally I would be able to do that in another way (or I could just give the feedback in the assistant panel and then apply).

[nickelser]

to fix your trouble try download this fix

how does github have spam this bad, what on earth

[iamnbutler]

and Zed could figure out if it was a new file, or existing file (ideally matching by name since sometimes it gets the path wrong), and have a button to just apply the changes (sometimes after I've edited them, since I love that I can edit the assistant responses).

This is exactly what /workflow attempts to do. It is a harder problem than it seems on the surface, especially for multiple sequential edits.

We are working on improving it. Rust performs significantly better than other languages for performing workflow edits right now - we are working on improving it beyond that. Thanks for trying it!

[sagarspatil]

and Zed could figure out if it was a new file, or existing file (ideally matching by name since sometimes it gets the path wrong), and have a button to just apply the changes (sometimes after I've edited them, since I love that I can edit the assistant responses).

This is exactly what /workflow attempts to do. It is a harder problem than it seems on the surface, especially for multiple sequential edits.

We are working on improving it. Rust performs significantly better than other languages for performing workflow edits right now - we are working on improving it beyond that. Thanks for trying it!

@iamnbutler /workflow is broken for python.
Are you aware of this?
#16894

[aguynamedben]

+1. I'm trying Zed for the first time and can't figure out how to get it to apply any type of diff the Assistant generates. I'm able to use the /file command but /workflow isn't autocompleting for me in Python or Rust.

[elidickinson]

The ‘/workflow’ command was removed. Apparently it was never intended for general release. There appears to be an experimental feature flag to enable a different way to apply changes from the AI assistant. See #19900 (comment)

[danielytics]

/workflow is still documented as existing here: https://zed.dev/docs/assistant/commands#workflow

This confused the hell out of me, until I searched the issues to see that it was removed.