claude-code - 💡(How to fix) Fix Cowork plugin context files not accessible to global CLAUDE.md imports [2 comments, 2 participants]

When a Cowork plugin includes context files (e.g. brand-guidelines.md, writing-standards.md), those files are stored in a session-specific path under local-agent-mode-sessions/. That path changes per session, so there's no stable location to reference with an @ import in ~/.claude/CLAUDE.md.

Expected behavior: Installing a Cowork plugin should make its context files available at a stable, predictable path — or automatically register them for global import — so users can load them without manual intervention.

Current workaround: Manually copy the context files to ~/.claude/context/ and add @ imports to ~/.claude/CLAUDE.md. This works but breaks whenever the plugin updates, requiring the user to re-copy manually.

Why this matters

Claude Code is where power users live — and not all of them are writing code. For some users, it's the primary environment for knowledge work: documents, policy drafts, communications, research. Cowork plugins that carry organizational standards — voice guidelines, writing norms, working agreements — are exactly what make that work coherent across sessions.

The users most likely to want this are also the ones least likely to stay in Cowork. Claude Code attracts people who want to build and refine their own AI workflows. Cowork is where plugins originate, but Code is where the people with the most capability to use them have ended up. If the two products don't share a stable path for plugin context, the gap falls hardest on the users who've invested the most in the ecosystem.

This isn't a niche developer request. It's a knowledge worker who built a workflow across two Anthropic products and hit a seam.