[FEATURE] Add workflow tool to cloud scheduled tasks

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Cloud Routines / scheduled tasks should expose the same workflow execution tool available in interactive Claude Code, or document why it is intentionally unavailable. Current mismatch prevents unattended reuse of tested workflows in scheduled cloud.

I just tried to launch workflow as a part of scheduled routine and agent coudln't handle it:

I'll check whether a Workflow tool is available in this environment before doing anything else.

Used ToolSearch
No Workflow tool surfaced. Let me search more specifically.

Used ToolSearch
There is no Workflow tool in this environment.

I searched the deferred-tool registry for it (both by keyword and by exact name select:Workflow) and it does not exist. The tools available here are Agent, Bash, Edit, Read, SendUserFile, Skill, ToolSearch, Write, plus deferred Monitor, WebFetch/WebSearch, Context7, Linear, and GitHub MCP tools. None of them is a Workflow invoker.

Note: there is a knowledgeExtraction entry exposed as a Skill (in the user-invocable skills list), but that is not the same as the Workflow tool the task requires, and the instructions are explicit:

If the Workflow tool is not available in this environment, STOP and report that it is unavailable — do NOT fall back to running the extraction manually.

Per those instructions, I'm stopping here rather than running the extraction by hand or substituting the Skill.

Result: The Workflow tool is unavailable in this cloud environment. The knowledgeExtraction workflow could not be launched. This appears to answer the test question: workflows are not supported (or at least not exposed as an invocable tool) in this remote execution environment.

Same workflow laucnhed fine locally for me - which proves my approach makes sense - but it's not isolated safe environment, and I can't let agents just go yolo.

Proposed Solution

Just allow same "workflow" tool in cloud routines environment.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_