Claude Cowork UX Problem: Persistent Input Box Creates False Continuity Expectations

The Persistent Input Box Problem in Claude Cowork

A user building a personalized Claude Cowork environment identified a specific UX problem that creates false expectations about continuity between tasks. The issue occurs at the user interface level rather than being related to AI's probabilistic nature.

Key Details from the Source

The problem centers on three contradictory behaviors in Claude Cowork's interface:

• Persistent text input box: The text input box stays visible with identical layout when switching between tasks. Draft text typed but not yet entered remains in the box.
• Context reset: Every new task starts a fresh Claude instance with zero native memory of previous sessions unless context files have been set up. No session handoff occurs between parallel "multithreaded" tasks.
• Attachment disappearance: When users attach screenshots or files and then switch windows, the attachments disappear while the UI looks identical. The state holds for text but not for images.

The user notes that these signals directly contradict each other: the persistent text box suggests continuity, the context reset indicates a blank slate, and the image reset suggests Anthropic lost the user's content. The visual consistency makes the discontinuity feel like betrayal rather than a new Claude instance being created.

This UX problem likely contributes to user frustration when opening new sessions, as the interface creates expectations of continuity that the underlying architecture cannot deliver.

Suggested Solution

The user proposes two possible fixes:

• Content should not carry state across task switches (both attachments and draft text) and should function like a text message thread
• The interface should visually reset to clearly signal "new context"

The current implementation does both poorly, effectively delivering neither approach well.