See how part of a task can be reused.
Choose a situation to compare result reuse, action execution, and fallback after an environment change.
One task, four situations
Interactive exampleTurn a web page's schedule into a table.
Tech meetupNovember 3
Layout update: time and topic positions have changed
Waiting to read the page
The execution pathReady
Press play to see how the task completes.
The model plans a new path
Structured outputWaiting to execute
Your schedule will appear here
Run the example to see the structured table.
schedule.csv
| Date | Time | Topic |
|---|
Uses preset sample data. Planning and fallback are simulated.
See what happens at each step
Explore the initial execution path
Reuse checksEnvironment —Cache —Execution —
How it works
- PATH
- Execution path to be built
- Node A
- Node B
- Execution method
Results as state
Structured Markdown, cleaned tables, and read-only tool results can all be saved as intermediate state. Under the same conditions, reading that artifact takes execution to node B.
Paths as programs
A different date introduces new parameters; editing a file or clicking an interface changes external state. These cases require actions to run again, rather than reusing a past success response.
Reuse goes beyond a single tool call.
Explore the runtime behavioral cache layer Tool combinations, loops, and conditional branches can also become parts of reusable paths.