Choose which steps are deterministic

A Factory Line defines how work starts, which agents run, and how one stage leads to the next. Use an agent where the work needs judgment, and a script, a rule, or a decision where it needs to be exact.

Build your first factory line →
For agents
$npx skills add islo-labs/skills

What is a Factory Line?

A Line is a repeatable engineering process that goes through stages like implement, verify, review, and risk check. Each stage runs in its own Machine, with its own instructions, inputs, and outputs.

Run triggers

Triggers kick off a run of Factory Line

Trigger a Line to run from Linear, Slack, GitHub, on a schedule, or from your own agent.

Step through stages

Run through stages

Every Line is made up of stages, each with its own instructions, inputs, and outputs. Every stage runs in its own Machine.

Verify work

Verifiers check work

Reviewer agents check the output of coding agents. Scripts run tests, builds, linters, and checks. Same input, same result, every run.

Retry, next, page a dev

Rules kick work back, let it merge, or page a responsible dev

Rules and decision models follow conditions you set to score PRs, retry stages, merge, or route to a human approver.

PRs with evidence

PRs come with evidence

PRs comes with tests, recordings, and logs. You can watch any run live, steer or stop it, and own the merge.

Two ways to build a Line

Agent build
Describe a line in plain English from Claude Code or Cursor via the Islo MCP server, from in-app chat, or start from a template.
Hand build
Use the Islo UI to place all the stages on a line, create Machines, connect repos, specify triggers, declare rules and tests and routing behavior and passing criteria.

Turning work into Lines

Bug fixing

Agents pick up an issue, reproduce it, write new tests if needed, develop a fix that passes, then open a PR.

INIssue labeled for an agent
factory line
OUTReproduced, tested, fixed, PR opened
“The moment I could trust that what comes back actually works and my only job was merging the PR, that was a huge change for us.”
Matan Kleyman · CEO, Obert
Explore Bug fixing →

Build Safe Software Factories