[hsaliak]

I find parallel agents to be an exception rather than a norm. Maybe I’m the problem? For those exceptional cases, opening a few more terminals gets the job done. It’s unclear to me if this needs to be the primary workflow. My brain naturally does better on deep work on one problem..

[hedgehog]

I have historically not used them but I want to start so that some of the spin up / tear down work of doing any particular task can happen in isolation. For example, drafting a change before I start editing, checking out and setting up code from a branch before I do a review, etc.

[caterama]

I am exactly the same, except I am really excited about this update! It’s not so much “in parallel” but being able to easily jump between threads. It allows me to dive into misc investigations in a side thread without derailing some main context where I’m doing the main editing.

[hsaliak]

I have a coding agent https://github.com/hsaliak/std_slop where the sessions are in SQL ledger. So /session [new, clone, deletes, undo] are supported and all sessions are persistent. Cloning lets you 'fork' the context and undo lets you roll back, basically solving the problem you state above.

Sessions are linear though, so you cant do this _while_ an existing session is cooking.

That said, I am excited about this update too, I've been playing with ACP support and Zed's UX was bare bones. I want to run my agent with multiple workers now, and see what happens.

[a012]

I also have this workflow, it’s like you’re on the side quests or on the main story; those are not necessarily in parallel