Skip to content
Auteryn

Background & Long-Horizon Execution

Background & Long-Horizon Execution

Section titled “Background & Long-Horizon Execution”

Not every task fits in a single synchronous reply. Auteryn agents can take on long, autonomous work that runs in the background — kicked off, worked on over time, and picked back up if interrupted — instead of blocking on one request/response turn.

Start a task, walk away, and come back to the result. Background runs execute asynchronously, can schedule their own follow-ups, and are resilient to interruptions.

What “long-horizon” means

Section titled “What “long-horizon” means”

Asynchronous runs

Queue a task to run in the background and get results when it’s done — no need to keep a connection open.

Self-scheduled follow-ups

An agent can schedule a follow-up run for later — for example, to check back on something or continue after a wait.

Resilience & resume

If a long run is interrupted, the agent can resume with its prior plan, recent results, and working notes intact.

Beyond one reply

Multi-step research, coding, and workflow tasks that span far more than a single chat turn.

Running a task in the background

Section titled “Running a task in the background”

You can start a background run in two ways:

  • In the workspace — kick off a Deep task and let it run while you do other things; results stream into the conversation as they complete.
  • Via the API — submit a run asynchronously and poll for progress and results.

The asynchronous run API returns run and task IDs immediately while execution continues server-side. See Run an Agent — set stream: false to queue the run and poll GET /api/tasks/{task_id}/stream for progress.

Recovery & continuation

Section titled “Recovery & continuation”

If a long run is interrupted — a timeout, a cancellation, or a restart — the next message can carry recovery context: the previous plan, recent tool results, and scratchpad notes. This is within-conversation continuation, so the agent doesn’t start over from scratch. See Autonomous execution for execution modes and timeouts.

When to use it

Section titled “When to use it”
  • Deep research that reads and synthesizes many sources
  • Multi-step coding in a sandbox
  • Scheduled or recurring work driven by Flows
  • Anything that takes longer than a quick, interactive reply
Section titled “Related”