claude-code - 💡(How to fix) Fix "Cowork" naming sets expectations the feature can't yet deliver [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46734Fetched 2026-04-12 13:34:28
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

The "cowork" label in Claude Desktop implies partnership — two agents contributing, creating, deciding together with shared ownership of output.

The actual experience is passive observation with reactive suggestions: screenshot → analyze → suggest → user applies manually. This creates a gap between expectation and delivery that leaves users underwhelmed.

The naming problem

  • "Cowork" implies mutual agency and contribution
  • The feature delivers observation + commentary
  • More accurate names: "Watch mode", "Screen advisor", "Observe & suggest"

What real cowork feels like (e.g. Claude Code CLI)

  • User says "refactor auth" → agent reads files, plans, edits, tests, commits
  • User builds frontend → agent builds backend in parallel
  • Agent notices pattern drift → flags it proactively, before being asked
  • Persistent memory, tools, execution — both sides produce output

Suggestion

Either evolve the feature toward actual co-creation (tool access, file editing, proactive contributions), or rename it to set accurate expectations. The feature itself isn't bad — the promise just overshoots the architecture.


Feedback from a daily Claude Code CLI user who tried Desktop cowork and felt the gap immediately.

extent analysis

TL;DR

Renaming the "cowork" feature to something like "Watch mode" or "Screen advisor" could help set accurate expectations for users.

Guidance

  • Review the current feature's capabilities and compare them to the implied promise of "cowork" to identify the gap in user expectations.
  • Consider renaming the feature to better reflect its actual functionality, such as "Watch mode", "Screen advisor", or "Observe & suggest".
  • Evaluate the possibility of evolving the feature to support actual co-creation, including tool access, file editing, and proactive contributions, to better align with user expectations.
  • Gather feedback from more users to validate the perceived gap in expectations and potential solutions.

Example

No code snippet is provided as the issue is focused on the feature's naming and functionality rather than specific code implementation.

Notes

The suggested rename is based on the implied discrepancy between the feature's name and its actual functionality. Evolving the feature to support co-creation would require significant changes to its architecture and capabilities.

Recommendation

Apply workaround: Rename the feature to set accurate expectations, as evolving the feature to support co-creation might require significant development efforts and may not be feasible in the short term.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING