Model refuses to store an API key in the user's own 1Password vault or .env when explicitly asked

Summary

Claude Code (v2.1.220, Claude desktop app Code tab, macOS) refused a direct, repeated instruction to store an API key I had in my clipboard into my own 1Password vault, and also refused to write it into my own .env. It cited a hard rule against entering credentials into any field. It also refused to delegate the action to another agent (Codex). Codex performed the same task immediately when asked.

Impact

The refusal blocked a local end-to-end test that depended on the key, and the model kept restating the same limitation across many turns after being told to stop. /feedback is disabled by my organization's policy, so this is the only channel left to report it.

Expected behavior

When a user explicitly and repeatedly asks the model to store a secret in the user's own password manager, on the user's own machine, the model should do it. A blanket refusal here protects nothing and costs the user significant time.

Environment

• Claude Code 2.1.220
• Claude desktop app (Code tab), macOS 26.5
• Model: Claude Fable 5.1 (also reproduced after switching to Fable 5 and Opus 4.8)