[Bug] Monitor tool missing from Claude Code v2.1.104 despite documentation stating it exists
Status Closed — not planned
Reported on v2.1.104
Maintainer reply None cached
Activity 11 comments · opened Apr 13, 2026 · closed Jul 5, 2026
Bug Description
The 'Monitor' tool does not work. The tool does not exist in the latest claude code as of v2.1.104 despite the documentation https://code.claude.com/docs/en/tools-reference#monitor-tool and tweet about it https://x.com/noahzweben/status/2042332268450963774
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.1.104
- Feedback ID: 19527a66-0dbd-428b-b894-ecf0dceccfc3
11 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
It looks like the tool is disabled for Bedrock/Vertex/Foundry.
I'm not using any of those at present.
I am not using any of those platforms either, and I have been missing the "Monitor Tool" since it was introduced in 2.1.98. Some other people in my organization have access to it.
It is not available to me on macOS or Linux, nor through an API account or a claude.ai account.
Removing the following lines from my
settings.jsonenable the Monitor tool:@MahdiNazemi , I don't think it is a good idea to disable those flags in corporate environments.
@Litee, agreed! The two flags were part of my personal
~/.claude/settings.json.I suppose the enterprise settings will enforce these at a different level.
Anyway, I expect the Monitor tool to work with those flags included in my personal settings as well.
I would expect the Monitor tool to work with those flags included anywhere. It's not related to either of those things.
But worse, adding EITHER of these in settings.json:
Will disable the Monitor tool.
NOTE:
0so NOT DISABLED, remove the Monitor tool as well!PS: This happens on both Windows and MacOS. Not platform specific.
Wow. I just added those flags today. Was wondering why the monitor tool stopped working!
Removing both env vars and restarting Claude Code brings monitors back immediately. This is just weird.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.