Users struggle with the disjointed experience of switching between Chat and Work applications, leading to inefficiencies in project development

Signals over time

2 observed signals across 1 sources, tracked for 7 days. Confidence: low.

What people are saying Observed

• “Product UX Feedback: Distinguish Chat and Work Conversations Inside Project Folders. Product UX Feedback: Distinguish Chat and Work Conversations Inside Project Folders Category: ChatGPT Projects — Navigation / UI / UX Priority recommendation: High Issue: ChatGPT currently allows Chat and Work conversations to coexist within the same Project folder, but provides no clear visual indicator in the Project conversation list to distinguish between them. For users managing multiple client projects and ongoing creative workflows, this creates unnecessary confusion. Why this matters: Work and Chat have different capabilities, workflows, and usage allowances. Users cannot immediately identify which existing conversations were started in Work. Returning to an established Project requires opening individual conversations to establish their mode. This becomes particularly problematic for professionals managing numerous conversations within multiple Project folders. Recommended UI improvements: Introduce distinct, persistent Chat and Work icons beside conversation titles within every Project folder. Maintain these indicators when conversations are reopened, renamed, or moved between Projects. C”

  RSS Feeds · complaint

• “Switching Chat to Work Shouldn’t be a thing. Feature Request: Make Chat the Home Base and Let Users Send Tasks to Work I use ChatGPT to design and build real projects, and I think Chat and Work should operate as one continuous experience rather than requiring the user to move between separate screens/modes. I would like to stay in a normal Chat conversation while developing an idea. Once the idea is ready, I should be able to simply say “Send that to Work” or “Build that.” Work would then take the approved plan from the conversation, execute the task, and return the completed result to the same Chat conversation for review. The workflow would be: Chat → Plan → Approve → Send to Work → Work Executes → Return to Chat → Review → Send Revisions to Work The user shouldn’t need to decide beforehand whether a conversation belongs in Chat or Work. Chat should be the control center, while Work operates as the execution engine behind it when needed. This is particularly important because Work has a weekly usage allowance. I recently used a significant amount of my Work allowance while discussing and designing a software project. Most of that planning could have happened in regular Chat, with”

  RSS Feeds · request