Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.237 ·

Poll tool drains queued harness events and reports who sent them

Claude can pull in queued messages from other sessions, stamped with who sent them, but only behind an env var.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.237
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
SessionsArea: what it touches
In DevelopmentKind: in v2.1.237,
What probably matters to youSection of the release

A Poll tool that drains queued harness events with sender provenance exists only when CLAUDE_CODE_POLL_EVENTS is true and the session is in remote mode.

What

A new Poll tool lets the model pull in events that the surrounding harness has queued for the session, returning the rendered messages along with how many events arrived and how many wake signals are still outstanding. Each queued event can now carry provenance saying who it came from, so a notice relayed from another Claude session arrives stamped as coming from a peer agent with that session's ID and text. None of this is reachable in a normal local run: the tool and the fields appear only when the CLAUDE_CODE_POLL_EVENTS environment variable is true and the session is in remote mode, meaning CLAUDE_CODE_REMOTE set to true with CLAUDE_CODE_ENVIRONMENT_KIND unset. Without that combination the tool is absent entirely and the session behaves as in previous builds, where it did not exist at all.

Details
  • Poll is registered both in the main tool list and in the reduced list used for simple mode, is read-only, is safe to run concurrently with other tools, and refuses to run inside a subagent with the message Poll is available on the main thread only.
  • The poll_event request that feeds the queue accepts optional authority, sender_id and sender_text alongside its existing fields, validated as poll_event: kind and event must be strings; wake, when present, a boolean; authority, when present, one of human-principal|human-other|peer-agent|world-event; sender_id and sender_text, when present, strings.
  • Sender text is capped at 49152 bytes and sender ID at 1024.
  • Accepted provenance travels from the event queue through the turn options into the Poll tool's output schema as an optional provenance array, and onto the poll-event attachment, so the model sees the origin of each event it drains.
  • A relayed cross-session notice is tagged authority: "peer-agent" carrying the originating session's identifier and text.
Evidence

poll_event: kind and event must be strings; wake, when present, a boolean; authority, when present, one of human-principal|human-other|peer-agent|world-event; sender_id and sender_text, when present, strings, authority: "peer-agent", Poll is available on the main thread only

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Configure cloud environments touched a line naming CLAUDE_CODE_REMOTE after this was published. * **No cloud-only scoping**: hooks run in both local and cloud sessions. To skip local execution, exit early unless the `CLAUDE_CODE_REMOTE` environment variable is `true`, the way the [dependency install script](#install-dependencies-with… cloud-environments see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesA small documentation edit on Configure cloud environments touched a line naming CLAUDE_CODE_REMOTE after this was published.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_POLL_EVENTS

See this entry in the whole of v2.1.237 →

Feedback