CLAUDE_CODE_HOST_SCHEDULED_RUN
A Claude Code environment variable, read out of the shipped bundle. It has been in the build since v2.1.280, including the newest one read.
Scheduled-run tasks can now report why they fired, but only if the host explicitly opts in via CLAUDE_CODE_HOST_SCHEDULED_RUN=1
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.280.
In the changelogs
2Releases whose published page names CLAUDE_CODE_HOST_SCHEDULED_RUN.
-
v2.1.280
New CLAUDE_CODE_HOST_SCHEDULED_RUN env var gates a local host's scheduled-run claims
Scheduled-run tasks can now report why they fired, but only if the host explicitly opts in via CLAUDE_CODE_HOST_SCHEDULED_RUN=1
found in this entry's text, named in this entry
-
v2.1.280
New env-derived telemetry flag: CLAUDE_CODE_HOST_SCHEDULED_RUN
Session telemetry now records whether a run was started by a host via a new CLAUDE_CODE_HOST_SCHEDULED_RUN environment variable
found in this entry's text, named in this entry
First cited
4The earliest release whose published evidence quoted CLAUDE_CODE_HOST_SCHEDULED_RUN was v2.1.280, 22 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
4One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the environment variable does. All environment variables.