A new tool for managing scheduled remote Claude Code agents (triggers) through the claude.ai CCR API — list, create, update, and run triggers without exposing OAuth tokens.
Feature-flagged by tengu_surreal_dali (default false), also requires allow_remote_sessions policy.
- Actions:
list,get,create,update,run— maps to/v1/code/triggersAPI - Auth is handled in-process with OAuth tokens injected automatically
- Tool is deferrable (
shouldDefer: true) to reduce initial tool schema load - Read-only actions (
list,get) are flagged as concurrency-safe - Requires claude.ai login and organization UUID
RemoteTrigger tool definition (gated by tengu_surreal_dali, search for "RemoteTrigger" and "manage scheduled remote agent triggers")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_surreal_dali On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.81: no gate table built for this version
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.81. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.