An approval pauses the run, not a workerA paused run releases its lease and holds no worker. It waits until someone decides, then the approval node returns the decision and the run continues from that step.Why every execution is pinned to one versionAn execution records its workflow version once, when it starts, and never follows a live pointer. That is why resume and replay still mean something weeks after a graph has changed.Memory has a subject, a namespace, and an expiryEvery memory fact lives under a key, a subject and a namespace, and it always expires: 90 days by default, one year at most. Here is how writes, reads and sharing work.What happens when a worker dies mid-runA worker holds a 30 second lease and renews it every 10 seconds. If it dies, the lease expires, another worker claims the run, and the run resumes from the last checkpoint.Which Linea client to use, and which key goes whereThe TypeScript SDK has a server client, an environment client for production starts, an end-user client for browsers, and a webhook verifier. Each one takes a different credential.Linea Labs is not Consensys LineaLinea Labs builds Linea, an open-source AI agent runtime at getlinea.app. It is not the Consensys Linea blockchain, and not the Linea Sketch iPad app.What is an AI agent runtime?A framework gives you the agent loop. A runtime runs it in production: durable steps, checkpoints, approvals, crash recovery, and replaying one failed step.Why replay needs the checkpointYou cannot re-run step four without the exact input it saw. That input only exists if the host executed the run and kept the checkpoint.One graph, not two productsThe canvas, the workflow JSON, and the node registry describe one thing. A second editor is fine. A second graph is a second product.The half frameworks do not shipFrameworks solve the loop. You still host it, retry it, store its memory, and keep its checkpoints. That second half is the product.Memory is not a side questFacts have to survive the run. If you stand up the store yourself, you are still doing the ops half. We think the graph should ask for memory and the host should keep it.Sandbox the code nodeA code node is an escape hatch. It still has to run somewhere that cannot take down the host. Linea does not ship one yet, and this is why.Triggers are not the productStarting a graph is a solved problem. The product is what has to stay up after it starts: the worker, the checkpoint, the wait, and the memory.
Toggle menu

Getting started

Publish a graph, then run it.

You do not assemble workers, queues, and a checkpoint store first. Draw the workflow, publish a version, and start an execution. The host keeps the record.

Linea builder with a workflow on the canvas
draw the graph, publish a version, start an execution
3 movesdraw the graph, publish a version, start an execution
to start a run: by hand, a webhook, a schedule, or the TypeScript SDK
4 waysto start a run: by hand, a webhook, a schedule, or the TypeScript SDK
writes a checkpoint, so the host keeps the record of the run
Every nodewrites a checkpoint, so the host keeps the record of the run

First run

Three moves, then the host takes the graph.

The agent is what you ship. The workflow is the versioned graph behind it.

  1. 01

    Draw the graph

    Author the workflow on the canvas: a trigger, nodes, and the edges between them. Prompts, tools, and business logic stay yours.

  2. 02

    Publish a version

    Publish freezes that graph. The host runs the version you published, so the canvas you reviewed is the execution that starts.

  3. 03

    Start an execution

    Run it by hand, from a webhook, on a schedule, or from your app with the TypeScript SDK. Each start is one run of that version.

Questions

Questions about this page.

Do I have to use the visual builder?

No. Every published version is a JSON graph the host runs exactly as published. You can author that graph in the visual builder, or create workflows and save drafts and versions through the TypeScript SDK with a workspace API key. Publishing a version and binding it to an environment need a signed-in admin in the dashboard. The SDK also starts executions, reads their results, and verifies webhooks.

What is Linea?

Linea is an agentic runtime and control plane. You ship an agent to your users. Linea executes the workflow graph behind it — model calls, tools, waits, approvals, and memory — and keeps the records around the run: checkpoints, signals, approvals, and regressions.

You write the agent.
We execute the graph.

The Linea newsletter

What we learn from every run.

New releases and field notes on running agents in production.

One email when something ships. Unsubscribe anytime.