Option to restore separate Chat/Composer panels from pre-0.46.x

While 0.46.x brings many great improvements, the merging of Chat and Composer into a single interface has created some workflow challenges for users who heavily relied on having separate contexts.

Current Issues:

  • When using Ask mode for general queries, it pollutes the Agent/Composer context
  • Need to create new chats specifically for composer-unrelated questions, then switch back to the main Agent chat
  • Switching between different chats is now more cumbersome

Proposed Solution:

  • Add a toggle in settings to restore the pre-0.46.x behavior of separate panels.
5 Likes

I second this not just for the reason OP requested. Sometimes the agent might be working for a bit and I want to plan out my next steps in chat panel while it’s working. I love the addition of being able to switch between modes as there are legitimate times where I just want to ask a question and don’t want the agent to start coding, but by taking away the separate chat panel I can’t multitask anymore. I mean if you could run 2x agents at the same time I’d say just put a second panel with the dropdown of options, but if that’s problematic having two agents editing the codebase at the same time, chat isn’t, so give us the option to chat on an unrelated context while another agent is working.

2 Likes

i third this

1 Like

100% Vote here for separate processes and panels for chat vs composer. I also would love to be able to adjust the Ask Temperature (strict, creative, lots of freedom) like in pic and even adjust the persona

1 Like

We need multi+head && infinite headless OBJECTS that we can speak to via N screens…