I would like to suggest a relatively small UI/UX change that could make a significant difference for users who regularly use both Chat and Work.
The problem
Chat and Work serve meaningfully different purposes.
In my own workflow:
- Chat is where I discuss, plan, reason, draft, revise, and work iteratively with ChatGPT.
- Work is where I hand off substantial execution-heavy tasks, such as remediating PDF and PowerPoint files for accessibility, processing multiple files, performing multi-step QC, and producing finished deliverables.
Work also has a separate limited usage allowance.
That makes it important to know immediately and continuously whether I am in Chat or Work.
On the web interface, however, once I am inside a conversation, the visual distinction is not obvious enough.
I experienced the practical consequence of this today: after using Work for several substantial PDF and PowerPoint accessibility-remediation tasks, I reached my Work usage limit. That made me realize how easy it would be to remain in Work and start doing ordinary drafting, discussion, or other tasks that could have been handled perfectly well in Chat—simply because the interface does not make the active mode sufficiently conspicuous.
This creates an avoidable opportunity for accidental quota consumption.
Proposed solution
Please make Chat and Work visually unmistakable while a conversation is open.
For example:
- Display a persistent, clearly visible CHAT or WORK label in the conversation interface.
- Give the Work input field a subtly different border, background treatment, or other visual styling.
- Change the placeholder in Work from a generic prompt to something mode-specific, such as “Assign a task to Work…”
- Include a distinct Work icon or other non-color indicator.
- Do not rely on color alone; the distinction should remain accessible for users with color-vision differences.
- Consider displaying a small Work-usage/quota indicator near the input field so users understand that actions in this mode consume a separate limited resource.
An optional safeguard could also warn users when a lightweight conversational request is being submitted in Work:
“This task may not require Work. Continue in Work or switch to Chat?”
The goal would not be to prevent users from using Work however they choose. It would simply make that choice intentional rather than accidental.
Why this matters
This is not merely cosmetic.
Chat and Work have different capabilities, different ideal use cases, and different usage constraints. The interface should communicate that distinction through persistent system-state visibility—a basic UX principle.
A user should never have to stop and think:
“Wait—am I currently spending my Work quota?”
The interface should make the answer obvious at a glance.
This would be particularly valuable for professional, academic, accessibility, research, and document-heavy workflows where users may move repeatedly between conversational reasoning and substantial execution tasks.
Related issue: switching between Chat and Work
I am aware that there are already Community feature requests asking for the ability to switch between Chat and Work within the same conversation or use a “Continue in Work” option. I support those ideas as well.
This request is deliberately narrower: even before changing how switching works, please make the currently active mode unmistakably visible.
Real-world context
This suggestion came out of an actual ChatGPT conversation after I exhausted my Work allowance while performing accessibility remediation on PDFs and a PowerPoint presentation. We ended up developing a simple workflow rule:
Chat for thinking, discussing, designing, drafting, and iterating.
Work for substantial execution-heavy tasks.
The product interface should help users follow that distinction.
For anyone interested, the conversation that led to this suggestion is here:
Thank you for considering it.