What happened

A Claude Code user authenticated on an enterprise workspace reported on July 4, 2026 that the agent suddenly started talking about building a temple in Minecraft—a project never mentioned in their session. The user rules out that anyone on their team is working on that project and suspects a cache leak between workspaces or even between enterprise and consumer accounts.

Why this matters

If you’re using Claude Code with sensitive information (proprietary code, business data, internal configurations), this report raises an urgent question: is the session cache truly isolated between workspaces? A leak like this would mean fragments of your conversation could end up in someone else’s session, and vice versa.

The case is still unconfirmed: the user notes their setup was unusual (agent launched from a directory different from their working directory). But the type of “contamination” they describe—a foreign project appearing out of nowhere—doesn’t explain itself with a wrong directory.

What to do now. Follow the issue on GitHub to see if Anthropic can reproduce the problem. If you work with sensitive data, consider temporarily suspending Claude Code sessions until an official response arrives. And in general: always review what you share with an agent that might be caching context in opaque ways.