Agents Can Now Call Step Functions—but They Still Can't Improvise the Workflow

AWS now allows Step Functions workflows to be treated as a tool for an Agent. The Agent decides when to call it and what parameters to pass, and the workflow executes the pre-defined steps.

The key to this change is the boundary. The Agent is responsible for judging context, while the workflow is responsible for reliable execution. Retries, exception branches, and state transitions in Step Functions will not change just because the model temporarily changes its mind.

You can think of it as a fixed route map. The Agent is the driver, deciding when to set off and what cargo to carry. The route itself cannot be changed on the fly.

This matters for high-risk operations. Starting machines, issuing refunds, data pipelines, and approval chains are all suitable for letting the model choose the timing, but not for letting the model improvise every step. Process definitions, permissions, and auditing stay in the state machine; the model only touches the entry point it is supposed to touch.

Developer William Geronco offered a judgment on X: let the model choose the timing, don't let it improvise changes to the workflow. That's very accurate. The value of an Agent lies in judgment, not in replacing orchestration.

Original message: William Geronco's X post