{"version":"2.1.229","anchor":"readnotifications-tool-reachable-only-in-remote-non-interact","canonical_anchor":"readnotifications-tool-reachable-only-in-remote-non-interact","heading":"ReadNotifications tool, reachable only in remote non-interactive runs","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/readnotifications-tool-reachable-only-in-remote-non-interact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### ReadNotifications tool, reachable only in remote non-interactive runs\n\nA new tool lets Claude pull queued notifications, but only in remote non-interactive runs.\n\n**What**\n\nA new read-only tool called ReadNotifications lets the model pull notifications the server has queued for a session (GitHub activity, scheduled triggers and messages from other agents), oldest first, marking them delivered and reporting how many are left. It is only offered when the `CLAUDE_CODE_REMOTE` environment variable is set and the session is non-interactive, so it does not appear in an ordinary terminal session.\n\n**Details**\n\n- Each notification carries an id, an origin, a queue timestamp and its content, plus a count of those still waiting.\n- Subagents are refused: \"ReadNotifications can only be called from the main conversation \u2014 subagents must not drain the session notification buffer.\"\n- This replaces injecting webhook and trigger activity into the conversation as if you had typed it.\n\n**Evidence**\n\n`ReadNotifications can only be called from the main conversation \u2014 subagents must not drain the session notification buffer.`, `Read the notifications queued for this session`\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}