[FEATURE] Context-aware Cowork suggestion notices in Claude Projects

Resolved 💬 2 comments Opened Mar 12, 2026 by smpallen99 Closed Mar 15, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

The Claude desktop app surfaces inline notifications suggesting users try Cowork. These appear to be triggered by heuristics (e.g., thread length) rather than by whether Cowork would provide genuine value in context. This creates noise and misleads users into unnecessary context switches.

Example: During a long project planning thread with a simple outcome (generate a CLAUDE.md and a starter Code prompt), a "Try Cowork" notification appeared. Clicking it opened Cowork with no context from the Project thread. Cowork provided no benefit for this scenario, and re-establishing context manually wasted both time and credits.

Proposed Solution

  • Base Cowork suggestions on the nature of the task, not thread length alone
  • When a suggestion is shown, briefly explain why Cowork is recommended for that specific scenario
  • Suppress suggestions for workflows that are purely generative/conversational with simple file-output outcomes
  • When a user accepts the suggestion, carry relevant Project context into the new Cowork session automatically rather than starting blank

Alternative Solutions

Manually dismissing notices and ignoring them. No way to configure suggestion sensitivity or opt out. The core issue requires changes to the suggestion logic on Anthropic's side.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

  1. Working in a Claude Project on architecture planning — a long thread but with a simple outcome: generate a CLAUDE.md and a starter Code prompt
  2. An inline "Try Cowork" notification appears mid-thread
  3. User clicks it, Cowork opens with no context from the Project thread
  4. User spends time re-establishing context in Cowork
  5. Realizes the task didn't warrant Cowork at all — the outcome was a simple file write
  6. Result: wasted time and credits with no productivity gain

Expected behaviour: the suggestion either doesn't appear for this type of task, or if it does appear, it explains the specific reason why Cowork would help (e.g. "This looks like a multi-file automation task — Cowork can handle that directly").

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗