Runs

A run is one piece of work by an agent in Geenius Chat. A quick question is a short run; a task with several steps is a longer one. Either way, the run is a record that is saved as it goes.

What a run keeps#

• Your message, the thing you asked for.
• Every step the agent took.
• Every tool call, with the result it got back.
• A question it is waiting on, if it needs you.
• The answer.
• Its state, for example running, waiting for you or finished.

Saved step by step#

The engine saves the run after every finished step. That is what lets a run survive an interruption: a closed tab or a dropped connection. When the run continues, it starts from the last finished step, with everything it already did in place.

When a run asks you something#

Some tasks need a decision only you can make. A run can stop with a question. The question is kept with the run, and the finished steps stay saved while it waits. When you answer, the run continues.

Tool results are data#

An agent may read a web page, a file or the result of another tool. The engine treats every tool result as data to read, never as an instruction to follow. If a web page says "ignore your instructions", the agent reads that as text on the page, not as an order. This lowers the risk of an agent being steered by what it reads; no system can make that risk zero.

Who can see a run#

Only the person who started a run can open it, and only while they are still a member of the workspace it belongs to.

Limits#

A run continues within the session and weekly limits of your plan. See plans and limits.