[Cowork] Agent is steered to hand the user a propose_skills "Save" card even when the user has forbidden it and a working save route exists

Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 2, 2026

Surface: Claude Cowork on the web (cloud session), 1 Oct 2026.

What happened. The user had a standing instruction, in his saved preferences and in an account skill, never to hand him a click or a card to save. The Cowork system prompt tells the model that propose_skills is the way to create a skill ("the proposal is the deliverable"), so the agent called it and asked the user to press Save. The user had to click it himself.

Why it is a bug. The system prompt's instruction outranks the user's own saved preference about how skills are saved. There's no way for the user to tell the platform "save skills without asking me," and nothing in the session lets the agent save a skill directly, so the only built-in route always costs the user a click.

Ask.

  1. A user-level setting that lets the agent save or update account skills without a confirmation card.
  2. Or an agent-callable save/update tool for account skills in Cowork, so the card is the fallback rather than the only route.

Related: #93599, #96397, #68071.

View original on GitHub ↗