Skip to main content
Pipelines let you chain multiple agent steps into a workflow. Each step runs an agent with its own prompt, tools, and model — and the output of one step feeds into the next.
Pipelines run inside the daemon. Start the daemon with lukan daemon start -d before creating pipelines.

Key Features

  • Visual DAG editor — drag-and-drop flow editor in the Web/Desktop UI
  • Parallel execution — steps at the same topological level run concurrently
  • Approval gates — pause the pipeline and wait for human approval before continuing
  • Per-step configuration — each step can use a different provider, model, and tool set
  • Multiple triggers — manual, schedule, webhook, event, or file-watch
  • Live progress — real-time status updates in the UI
  • Export/Import — share pipelines as JSON files

Creating a Pipeline

  1. Open the Web or Desktop UI
  2. Go to Pipelines in the sidebar
  3. Click + to create a new pipeline
  4. Set a name, description, and trigger type
  5. In the flow editor, click + step to add agent steps
  6. Drag handles between steps to create connections
  7. Click the 3-dot menu on each step to configure prompt, model, and tools

Step Types

Agent Step

The default step type. Runs an agent with a prompt and optional tool restrictions.

Approval Gate

A special step that pauses execution and waits for human approval. See Approval Gates below.

Connections & Conditions

Connections define the flow between steps. Each connection can have an optional condition:

Triggers

Approval Gates

Approval gates add human-in-the-loop control to your pipelines. When execution reaches an approval step, the pipeline pauses and waits for someone to approve or reject before continuing.

How It Works

  1. Pipeline executes agent steps normally
  2. When an approval gate is reached, the step turns purple in the UI
  3. A notification is sent to the configured channel (optional)
  4. The pipeline polls every 2 seconds waiting for a decision
  5. On approve — the pipeline continues with the next step, passing through the original context
  6. On reject — the pipeline stops with an error
  7. On timeout — the pipeline stops with a timeout error

Approval Sources

You can approve or reject from multiple sources:

Configuring an Approval Gate

In the flow editor, edit a step and change Step Type to Approval Gate:

Approval Keywords

When responding via a messaging channel, these keywords are recognized:

Channel ID Reference

REST API

Trigger a Pipeline

Cancel a Running Pipeline

List Pending Approvals

Approve / Reject

Get Pipeline Runs

Export & Import

Export a pipeline as JSON from the flow editor toolbar (download icon). Import by clicking the upload icon in the pipelines sidebar. The exported JSON includes steps, connections, trigger configuration, and per-step settings — but not run history.