Add support for queued messages

[kevinvandijk]

Description

We now keep the focus in the chat when making changes so you can start typing while Kilo is working. A next logical step is to make it so that messages are queued up and will be send as soon as the LLM is ready to accept more input.

Criteria:

• User can start typing a message whenever, even if Kilo is working
• The message can be sent whenever and will end up in a queue
• Whenever the LLM is ready to accept more input, the next message will be sent to it

[nicekate]

It would be great to have editing capabilities for previously uncompleted tasks

[hassoncs]

I have an experimental branch with queuing enabled here:

Queuing (queued send)

Interjection (cancel, then send)

I think the UX feels pretty good, but I'm very open to feedback of any kind!

[UltronOne]

Is there any update on the feature? I love it in cursor to be able to just brain dump and fill the time the model is working with new commands. Especially for multiple small tasks on the ui this is extremly useful.

[hassoncs]

Hey @UltronOne ! Thank you for asking! I'd really like this feature too

I was making good progress on it, but then Roo launched their Todo List feature which made me pause to make sure the features work well together. Queued messages act similarly to having an item on the todo list, but I think they serve different purposes. I'm thinking:

Todos are for the LLM
Queued messages are for You

[avineshwar]

the queue should accept more than one message

in the same fashion, it should be consumed as well that is one at a time