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
- Open the Web or Desktop UI
- Go to Pipelines in the sidebar
- Click + to create a new pipeline
- Set a name, description, and trigger type
- In the flow editor, click + step to add agent steps
- Drag handles between steps to create connections
- 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
- Pipeline executes agent steps normally
- When an approval gate is reached, the step turns purple in the UI
- A notification is sent to the configured channel (optional)
- The pipeline polls every 2 seconds waiting for a decision
- On approve — the pipeline continues with the next step, passing through the original context
- On reject — the pipeline stops with an error
- On timeout — the pipeline stops with a timeout error
