Add components to a plugin changedplugins/components
Upstream edited this page at 24 Oct 2026 23:06 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 24 Oct 2026 23:07 UTC.
Upstream edited
Recorded here
Lines+2added
Lines−1removed
From line
580
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits18to this page, all time
The whole hunk
from line 580, old and new numbered
/
from line 580
580580
581581A monitor's command is limited in where it starts and what it can reference:
582582
583* **Interactive sessions only**: plugin monitors start in an interactive session and never in non-interactive mode with the `-p` flag. They also don't start in sessions where the API provider or telemetry settings make the [Monitor tool](https://code.claude.com/docs/en/tools-reference.md#monitor-tool) unavailable
583* **Interactive sessions**: plugin monitors don't start in non-interactive mode with the `-p` flag
584* **Minimum version**: on Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry, or with `DISABLE_TELEMETRY` or `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` set, monitors require Claude Code v2.1.310 or later. The requirement applies when [feature-flag fetching](https://code.claude.com/docs/en/env-vars.md#features-that-need-feature-flag-fetching) is off
584585* **No user configuration**: `command` gets the [path variables](#path-variables-and-persistent-data) and `${ENV_VAR}` from the environment, but never `${user_config.*}`. A monitor that references one doesn't start, and monitor processes don't receive `CLAUDE_PLUGIN_OPTION_<KEY>` either
585586* **Disabling mid-session**: if you disable a plugin mid-session, Claude Code doesn't stop monitors that are already running. They stop when the session ends
586587
No line in this hunk matches that.