> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.islo.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.islo.dev/_mcp/server.

# Lines

> Define stages, transitions, and versions for repeatable factory work.

A Line describes how work starts, which Agents run, and how one stage leads to another. The Islo skill generates its `line.toml` definition when you build with a local agent. In the dashboard, start from a template or ask the agent to build a Line. The Line belongs to one factory.

## In the dashboard

1. Open **Lines** for your factory ([factories](https://app.islo.dev/factories) → your factory → **Lines**, or **factory → Lines** for the default factory).
2. Select **New line**. Choose a template and review its trigger, stages, required integrations, and inputs. To make a custom Line, describe the work to the agent on this page and approve its proposed manifest.
3. Enter the template's required inputs and deploy it. The template flow also starts the first run. To change its stages, trigger, or transitions later, ask a local agent using the [Islo skill](/concepts/custom-lines) to update, validate, and redeploy the Line.
4. Open **Runs** to watch stages, events, and the run conversation. Use steer, stop, and retry when you need to intervene. You can start another manual run from the Line page.

For a catalog Line with less authoring, see [Suggested Lines](/concepts/suggested-lines) and deploy from the suggestion flow when your factory provides it. To design your own with the dashboard or a local agent, see [Build a custom Line](/concepts/custom-lines).

## Build with a local agent

[Install the Islo skill](/concepts/custom-lines) in your local coding agent. Describe the result, repository, trigger, inputs, and any review or verification stages. Ask the agent to prepare the Machines and Agents, generate the Line, run schema validation, and show you the deployment plan before deploying.

The agent uses the installed `islo schema factory --short` and `islo schema agent` definitions. An Agent stage uses its Agent's default `input` parameter and `output` result unless the generated Line replaces that contract. Reserved stage IDs are `trigger`, `done`, and `wait`.

## Run and version a Line

From the CLI:

```bash
islo factory line run review-line --param input="Review pull request 123"
islo factory line runs review-line
islo factory line-run status <run-id>
```

A deploy creates a Line version. Ask the agent to validate and redeploy after changing stages, the trigger, or transitions. [Operate a run](/concepts/runs) covers events and intervention for both dashboard and CLI workflows.

A schedule belongs on the Line trigger when the whole Line repeats. See [triggers](/concepts/triggers).