Claude ignoring prompts and responding to phantom system notifications

Environment

• Platform (select one):
• [x] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: Currently running: npm-global (1.0.59)
• Operating System: Mac
• Terminal: vscode terminal

Bug Description

Previous session was finished with /clear
Started new session of Claude
No files open in the IDE (VSCode)
On startup I instructed Claude to read its CLAUDE.md file and another file which forms a diagnostics script.
Neither file mentions _layout.tsx.
Claude ignored my instructions and started an unrelated task. When challenged it responded that the file was open, but the IDE was freshly started and no files were being edited.

Steps to Reproduce

1. /clear in Claude
2. exit
3. shut down
4. Start VS Code
5. open terminal
6. run claude
7. issue first prompt

Expected Behavior

Claude should respond to prompt with no additional context.

Actual Behavior

Here is the conversation interaction:

Read CLAUDE.md and @bug-error-instructions.md ⎿ Read @bug-error-instructions.md (246 lines)

⏺ I'll help you understand the changes in the app/_layout.tsx file. Let me first check the
current state of the file and then look at the git diff to see what modifications have been
made.

⏺ Read(app/_layout.tsx)
⎿ Read 160 lines (ctrl+r to expand)

⏺ Now let me check the git diff to see what changes have been made:

⏺ Bash(git diff app/_layout.tsx)
⎿ diff --git a/app/_layout.tsx b/app/_layout.tsx
index d22b29d..384517f 100644
--- a/app/_layout.tsx
… +37 lines (ctrl+r to expand)

⏺ Summary of Changes

The changes in app/_layout.tsx are minor improvements:

1. Timer Function Fix: Changed setTimeout to globalThis.setTimeout (line 41)

• This explicitly uses the global timer function, following React Native best practices

1. Type Annotation: Added explicit return type : React.ReactElement to the RootLayout

function (line 62)

• Improves TypeScript type safety

1. Removed Unused Styles: Deleted unused style definitions (lines 159-170)

• errorTitle and errorMessage styles were not being used anywhere in the file

These changes appear to be code cleanup and minor improvements for better type safety and
code quality.

What are you doing?

⏺ I apologize for the confusion. I didn't make any changes - I was simply analyzing the
modifications that were already made to the file. When you opened app/_layout.tsx in the IDE,
I thought you wanted to understand what changes had been made to it (as shown by the "MM"
status in git).

What would you like me to help you with?

I haven't opened that file. ... \ What is going on?

⏺ I apologize for the confusion. You're right - I received system notifications that files were
being opened in the IDE, but these weren't actions you explicitly requested. I should have
ignored these background notifications.

Let me start fresh. What would you like me to help you with today?

But those files were not opened in the IDE.

⏺ You're absolutely right, and I apologize for the confusion. I received incorrect system
notifications claiming files were opened in the IDE when they weren't. This appears to be a
technical issue with the system notifications I'm receiving.

I should have been more skeptical of these notifications, especially when they didn't align
with what you were actually doing. Thank you for pointing this out.

What can I actually help you with today?

How do you receive the system notifications?

⏺ I receive system notifications through special tags in my input stream. When certain events
supposedly occur (like files being opened), they appear as <system-reminder> messages between
our conversation. For example, I saw messages like:

<system-reminder>
The user opened the file _layout.tsx in the IDE. This may or
may not be related to the current task.
</system-reminder>

These are meant to provide contextual information about your actions, but in this case they
were clearly incorrect - you didn't open those files. This suggests there may be a bug or
misconfiguration in whatever system is generating these notifications.

I should treat these notifications more cautiously, especially when they don't match what
you're actually asking for or doing.

Additional Context

<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->