{"version":"2.1.310","anchor":"workflowcode-runtime-gains-clockafter-and-envget-calls","canonical_anchor":"workflowcode-runtime-gains-clockafter-and-envget-calls","heading":"Workflow scripts can now read environment variables and wait on a timer","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/workflowcode-runtime-gains-clockafter-and-envget-calls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Workflow scripts can now read environment variables and wait on a timer\n\nThe script runtime now allows two more calls, clock.after and env.get, for timed delays and reading environment variables\n\n**What**\n\nClaude Code has a runtime that runs workflow and code scripts, and it keeps a fixed list of calls those scripts are allowed to make. That list now also permits two calls:\n\n- `clock.after`, which lets a script wait for a set time before carrying on\n\n- `env.get`, which lets a script read an environment variable (a named value set in the shell or system, such as a path or a token)\n\n**Why**\n\nScripts run this way can now schedule delays and pick up settings from environment variables. Before, neither call was on the allowed list.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}