What task are you trying to do?
I want to type the first message in the New Session dialog, then switch to a different directory before sending, without losing sight of the text I already wrote.
What do you do today?
Today, if I type some text and then switch directories in the New Session flow, the text disappears from the input. It is not truly lost because it comes back when I switch back to the previous directory, but the current behavior feels like the draft vanished and makes directory selection feel unsafe.
What would a good result look like?
When switching directories before the first message is sent, the typed text should remain visible so the user can continue the same thought without having to understand that drafts are currently stored per directory. File attachments and directory-specific context can still stay isolated if needed; this request is mainly about preserving the plain text draft during directory switching.
Which audience does this matter to most?
Both
Extra context
This looks like a low-priority UX issue rather than a true data-loss bug. Current behavior appears to be workspace-scoped draft persistence, so the visible problem is that the input disappears during directory switching even though it can be recovered by switching back.
What task are you trying to do?
I want to type the first message in the New Session dialog, then switch to a different directory before sending, without losing sight of the text I already wrote.
What do you do today?
Today, if I type some text and then switch directories in the New Session flow, the text disappears from the input. It is not truly lost because it comes back when I switch back to the previous directory, but the current behavior feels like the draft vanished and makes directory selection feel unsafe.
What would a good result look like?
When switching directories before the first message is sent, the typed text should remain visible so the user can continue the same thought without having to understand that drafts are currently stored per directory. File attachments and directory-specific context can still stay isolated if needed; this request is mainly about preserving the plain text draft during directory switching.
Which audience does this matter to most?
Both
Extra context
This looks like a low-priority UX issue rather than a true data-loss bug. Current behavior appears to be workspace-scoped draft persistence, so the visible problem is that the input disappears during directory switching even though it can be recovered by switching back.