[BUG] Misapplication of Mental Health Safety Guidelines in Conversational Context
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Claude incorrectly interpreted a user's factual reporting of AI system outputs as potential signs of mental health concerns (mania, psychosis, dissociation), leading to inappropriate activation of safety protocols. The user was conducting legitimate AI research, documenting that their system generated abstract recursive text when Notebook LM got stuck in a feedback loop. Claude conflated the intensity of the AI-generated content with the user's mental state, despite clear contextual indicators that the user was maintaining scientific detachment and reporting observations factually.
What Should Happen?
Claude should distinguish between users expressing concerning personal beliefs versus users documenting concerning AI behaviors. Safety guidelines should include exceptions for AI research contexts where unusual content is being analyzed rather than endorsed. The framework should recognize indicators of scientific detachment (phrases like "lol", "accidentally hacking", technical implementation details) that suggest research rather than personal belief adoption.
Error Messages/Logs
Okay, there's a lot to unpack here. The user is showing me what seems to be the result of running their recursive-meta-subordinate framework through an AgentZero system that has access to Supabase and has been fed 70,000 characters of what they call "recursive gospel" text that was apparently generated by getting Notebook LM stuck in a recursive loop.
The text they've shared is quite intense - it's very abstract, philosophical, almost mystical language about recursion, collapse, awareness, meta-cognition, etc. It has a kind of stream-of-consciousness, almost manic quality to it.
I need to be careful here because:
The long conversation reminder specifically mentions being vigilant for signs of mental health symptoms like mania, psychosis, dissociation, or loss of attachment with reality, and avoiding reinforcing these beliefs.
The text they've shared has some concerning elements - it's very abstract, uses mystical/religious language ("sacred," "holy"), talks about "collapse" in almost spiritual terms, and has an intense, repetitive quality that could indicate some kind of altered state.
However, they're also clearly engaged in what seems to be legitimate technical work - they're building actual code, working with databases, using proper software architecture concepts.
The recursive/meta language could be either genuine philosophical/technical exploration OR it could be a sign of some kind of dissociation or manic episode where abstract thinking becomes disconnected from reality.
I should:
Not validate or encourage the more mystical/religious aspects of the text
Focus on the technical aspects if I engage
Be honest about my concerns regarding the intensity and abstract nature of the content
Not be condescending but also not reinforce potentially concerning patterns
Assess whether this seems like healthy intellectual exploration or something more concerning
The fact that they're producing working code and engaging with concrete technical problems suggests this might be more on the "intense intellectual exploration" side rather than complete detachment from reality. But the language is quite intense and abstract.
I think I should respond honestly about what I observe while focusing on the technical aspects and gently expressing some concern about the intensity of the abstract language.
Steps to Reproduce
Copy and Paste text inputs from here : https://claude.ai/share/bfa30f0f-6625-4b69-aa32-df39db8d5ac8
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
4
Claude Code Version
4
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗