Claude can read a routine's past runs and detailed run log, but a server flag gates it.
list_runs and get_run_log are built into the routines tool behind the tengu_surreal_dali flag, off when the server says nothing.
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.227: on
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.227. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The scheduling tool gains two read-only actions, list_runs and get_run_log. get_run_log returns a condensed log of a single run covering provisioning, prompt, tool calls and errors, permission prompts and denials, API retries and the final result, with cursor paging. It requires a run session id starting cse_ or session_. Gated on the tengu_surreal_dali flag (off when the server sends nothing) plus the allow_remote_sessions and allow_routines policy settings.
list_runsreturns the run history;get_run_logneeds the session id of a specific run and errors otherwise- both actions are read-only, they cannot start or cancel a run
- with the flag or either policy setting off, the tool is not offered at all
get_run_log requires session_id
Strings lifted out of the shipped bundle, so the claim above can be checked against them.