Runtime
The host
runs the graph.
You write the agent. Linea executes every step of it.
- Checkpoint after every step
- Automatic retries on failure
- Resume where a crash left off
The runtime and control plane for production agents
Build and operate
production agents.
You ship the agent. Linea executes the graph, holds the checkpoint, and gives you the loop to replay a failure and publish a fix.
Durable execution
Every step is checkpointed, failures retry, and an interrupted run resumes from the last successful node.
The fix loop
Replay the failing step against the exact input it saw, freeze it as a case, and publish the fix.
Memory on the host
Facts and workspace knowledge live with the run, so the next execution reads what the last one learned.
The host
Replay
Replay the step
that failed.
We ran it, so we kept the exact input every step saw.
- Rerun one node, not the whole run
- Swap the prompt or model and compare
- Freeze the fix as a regression case
Memory
Memory that
survives the run.
The next run reads what the last one learned.
- Facts and workspace knowledge on the host
- No vector store to wire up per graph
- Shared across every run of the agent
Built for the people
who operate the run.
Technical builders first. You write the agent. We execute the graph and keep the records that let you diagnose, replay, and ship a fix.
Technical founders
Would have assembled this stack
Durable execution, an agent framework, observability, evals, and a memory store are five products you would otherwise wire yourself. Linea is those on one data model.
AI engineers
Fix the step that failed
A flag fires on an execution. Replay that node against the input it originally saw. Freeze it as a regression case, publish, and check you did not break the rest.
Builders who operate the run
The framework is not the host
LangGraph writes the loop. You still host it. Linea executes the graph and keeps the control plane: checkpoints, signals, approvals, and the records around the run.
From the Linea team
Notes on the host, the checkpoint, and the loop after a failure.
Linea Labs is not Consensys Linea
Linea 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.
Linea Labs
Nov 12, 2026
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.
Linea Labs
Nov 12, 2026
Why replay needs the checkpoint
You cannot re-run step four without the exact input it saw. That input only exists if the host executed the run.
Linea Labs
Aug 18, 2026
Questions
Everything you need to know.
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, memory, and sandboxed code — and keeps the records around the run: checkpoints, signals, approvals, and regressions.
Is this a workflow-automation tool?
No. Workflow is the precise name for the executable graph, not the product category. An agent may use several workflows; some graphs are intentionally non-agentic. External positioning is build and operate production agents. Workflow terminology stays underneath where it is technically accurate.
How is this different from n8n or Zapier?
Those products execute automations and compete on visual simplicity. They get thin when a step needs real code or an agent loop, and they have no signal or regression layer. Linea executes the graph so it can hold the checkpoint, replay one step, and keep the control plane around the run.
How is this different from LangGraph?
A framework helps you write the loop. You still host the process, store checkpoints, keep memory, and operate the result. Linea is that host and control plane. Keep the prompts and tools you already have; we execute the graph.
What is step-level replay?
Because Linea executes the graph, it holds the checkpoint: the exact input a node received. Replay runs that one step again against that input. No deploy, no reproducing state, no re-running the steps before it. An observability vendor can show the failure; it never ran the graph, so it has no checkpoint to replay from.
Do I have to use the visual builder?
No. The builder and the TypeScript SDK are two views of the same workflow definition. Pick the surface. Do not pick a second product.
