Comment by d4rkp4ttern

Comment by d4rkp4ttern 19 hours ago

2 replies

A CLI chat interface seems ideal for when you keep code "at a distance", i.e. if you hardly/infrequently/never want to peek at your code.

But for writing prose, I don't think chat-to-prose is ideal, i.e. most people would not want the keep prose "at a distance".

I bet most people want to be immersed in an editor where they are seeing how the text is evolving. Something like Zed's inline assistant, which I found myself using quite a lot when working on documents.

I was hoping that Cowork might have some elements of an immersive editor, but it's essentially transplanting the CLI chat experience to an ostensibly "less scary" interface, i.e., keeping the philosophy of artifacts separate from your chat.

wek 16 hours ago

I agree that for writing documents and for a lot of other things like editing csv files or mockups, I want to be immersed in the editor together with Claude Code, not in a chat separated from my editors

  • d4rkp4ttern 15 hours ago

    I was hoping that zed’s inline assistant could make use of the CC subscription but sadly not; you have to pay for metered API usage. But for simple writing tasks, I hooked up Zed’s inline assistant to use Qwen3-30B-A3B running on my Mac via llama-server, and it works surprisingly well.