runsengine

A long task that survives a closed tab

How Geenius Chat saves an agent run step by step, what happens when a run is interrupted, and what a run can and cannot do yet.

Everybody has lost work to a closed tab. With a chat app the loss is quieter but just as real: you asked for something that took a while, you switched away, and when you came back the answer was half finished or gone. In Geenius Chat we want that to stop happening. This post explains how, in plain terms, and where it stands today.

What a run keeps#

In Chat, every piece of work by an agent is a run. A run is a record, not a moment. It keeps:

  • what you asked,
  • every step the agent took,
  • every tool it called, with the result it got back,
  • a question it is waiting on, if it needs you,
  • and the answer.

The important word is every. The engine saves the run after each step, not only at the end.

What happens when a run is interrupted#

Say an agent is working through four steps and the connection drops after step two. Because steps one and two were saved when they finished, the run does not start again from nothing. It picks up at step three, with everything it already learned. You see the same thread, with the finished steps in place.

There are limits: a run continues within the session and weekly limits of your plan, and what is saved is each finished step.

When an agent needs you#

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

Your threads, newest first#

Runs belong to threads, the conversations in your list. The list shows your threads newest first, one row per thread, with when it last moved and where it stands. It loads a page at a time, so a long history stays quick. You see only your own threads, and only in a workspace you are a member of.

Where it stands#

Saving and resuming runs, waiting questions and the list of threads are built and tested in the engine. They are not live: there is no public app yet. When Chat opens, they open with it.

If long tasks are the reason you want Chat, join the waitlist and say so in the form. It tells us which parts to open first.