{"version":"2.1.200","anchor":"remote-workflow-via-environment-variables","canonical_anchor":"remote-workflow-via-environment-variables","heading":"Remote Workflow via Environment Variables","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.200\/e\/remote-workflow-via-environment-variables","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.200","markdown":"### Remote Workflow via Environment Variables\n\n**What**\n\nServer-launched remote sessions (CCR) can now receive and execute a workflow script delivered through environment variables, enabling fully server-initiated workflow runs without interactive invocation.\n\n**Details**\n\n- `CLAUDE_REMOTE_WORKFLOW_SCRIPT`: The workflow script content (as a string)\n- `CLAUDE_REMOTE_WORKFLOW_ARGS`: Optional JSON-encoded args to pass to the script\n- `CLAUDE_WORKFLOW_NAME_ONLY`: Restricts workflow execution to named bundled workflows only\n- Gated to sessions where `CLAUDE_CODE_REMOTE` is set; emits an error if called in a local session\n- Validates the script is deterministic (no `Date.now()`, `Math.random()`, or `new Date()`)\n- Compiles and runs via the same workflow engine as the interactive `Workflow` tool\n- Returns JSON-encoded results or structured error codes back through the session\n\n**Status**\n\nOnly active in remote CCR sessions; the internal slash command is hidden with no interactive use.\n\n**Evidence**\n\nRemote workflow handler (search for `\"CLAUDE_REMOTE_WORKFLOW_SCRIPT\"`, `\"this command only runs inside a remote (CCR) session\"`, `\"workflow scripts must be deterministic\"`)"}