{"version":"2.1.227","anchor":"routines-tool-can-list-past-runs-and-fetch-a-run-log","canonical_anchor":"routines-tool-can-list-past-runs-and-fetch-a-run-log","heading":"Routines tool can list past runs and fetch a run log","tier":"soon","area":"Cloud Routines","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/routines-tool-can-list-past-runs-and-fetch-a-run-log","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Routines tool can list past runs and fetch a run log\n\nClaude can read a routine's past runs and detailed run log, but a server flag gates it.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- `list_runs` returns the run history; `get_run_log` needs the session id of a specific run and errors otherwise\n- both actions are read-only, they cannot start or cancel a run\n- with the flag or either policy setting off, the tool is not offered at all\n\n**Evidence**\n\n`get_run_log requires session_id`\n\n- Flag `tengu_surreal_dali`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.227; this account: on, anonymous baseline: on, compiled default: off) 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.\n- Area: Cloud Routines\n- Names: `list_runs`, `get_run_log`, `allow_remote_sessions`, `allow_routines`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}