Features · Runs
Long tasks that survive a break.
A run is saved after every step.
A run is a record.
A run keeps what you asked, every step the agent took, the tools it called, any question it is waiting on and its answer. Because each step is saved, a closed tab or a dropped connection does not lose the work: the run continues from the last finished step, within the limits of your plan.
- Saved after every step
- Waits for your answer when it asks
- Continues from the last finished step
Read as data, never as orders.
An agent reads things: a web page, a file, the result of a tool. The engine treats all of it as data to read and never as an instruction to follow. That is a rule of the engine, not a setting.
Where it stands
In the engine, next in the app.
- Pre-betaSaving and resuming runs
Built and tested in the engine.
- PlannedRuns in the app
Coming soon.
Questions
About runs.
What is a run?
One piece of work by an agent: your message, the steps it takes, the tools it calls and its answer. Chat saves a run step by step, so it can continue after an interruption.
What happens if I close the tab during a long task?
The run is saved step by step, so it can pick up from the last finished step instead of starting again. This is built in the engine; long tasks in the app come next, within the limits of your plan.
Can an agent stop and ask me something?
Yes, a run can wait for your answer and continue when you give it. The engine keeps the waiting question with the run.
Can a web page trick the agent?
The engine treats every tool result, such as the text of a web page, as data to read and never as an instruction to follow. That lowers the risk; no system can promise it is zero.
What exactly is saved in a run?
Your message, every step, every tool call with its result, a question the run is waiting on, and the answer. See runs.
What happens when I reach a limit?
The finished steps of a run stay saved. How much is left of the session and weekly limit will be shown in the app.
Hand it a longer task.
In early access.