If Tesseract restarts mid-task, your task carries on

An update, a restart or a fresh framework session, and the agent's work carries on. What Tesseract does when it restarts in the middle of a task, and what you do.

A Tesseract conversation with a five-step plan for a bakery's holiday season, every step ticked and the Approve & continue button below

Your agent is three steps into a five-step plan when the app restarts, say after an update. In Tesseract the task carries on. Type continue and the agent picks up the same task, on every framework. A question it asked you before the restart is still waiting in the chat, and Tesseract keeps its own copy of every conversation, so the conversation carries on whatever happens on the framework’s side.

This came in over the last two releases, 0.11.35 and 0.11.38. Here is how it works, and the one word you type.

”Continue” means the same task

If the app restarts while the agent is working on your message, or while it is waiting on a question it asked partway through, the continue you type afterwards belongs to that same task, on every framework. The review that checks the agent’s work then judges it against the whole of what you first asked for.

A question to you stays a question to you

Since 0.11.38, when the agent asks you something, the question stays in the chat until you answer. It stays with you rather than going off as a background job, and whatever you type there answers it for good. After a restart, it is still your question to answer.

When the framework starts a fresh session

Tesseract keeps its own copy of every conversation. When Claude Code or Codex starts fresh on its side, the conversation continues from Tesseract’s copy, in a new session. You keep the conversation you were in; the framework simply starts a new session behind it.

Reopening a conversation says what it is doing

A conversation you reopen shows it coming back to life, in plain words, so you see it resuming.

What happens to everything else

  • Servers it started stop with it. Since 0.11.35, everything a framework starts, such as a dev server, goes when it goes, on Mac, Windows and Linux.
  • On Windows, the app comes back. If Tesseract closes during the day, a small watcher starts it again within a minute, and stands aside while an update installs.
  • Updates wait for a good moment. A downloaded update installs when the computer is idle with its screen locked, as it does when you step away. Since 0.11.38 that works on Linux too.
  • Linux .deb installs update cleanly. An install from the .deb installs the update itself when it is allowed to, and otherwise keeps running its version and leaves the update to you.

What you do

Type continue once the app is back. That one word joins the task back up.

For work that carries on while you are away from the computer entirely, put it on a machine that stays on, as in run AI agents on your own server, or let an assistant work through the night with a cost cap.

Try it

Download Tesseract, or update from Settings → About → Check for updates, and a restart costs you one word.

مطالب بیشتر از وبلاگ