Workflow Engine

Releases, reviews, agents.One engine.

Define workflows as code. Run them from CLI, CI, or Studio. Every step logged, every run observable, every policy enforced.

Install Read the docs

Terminal

built-in step types

execution modes

local execution

cloud dependency

Mental model

Workflows are code. Not config.

A workflow is a YAML file that lives in your repo, gets reviewed in PRs, and ships in the same release as the rest of your code. No GUI-only logic, no hidden state.

Steps declare dependencies. The engine resolves them, runs what can run in parallel, and waits for what needs to wait. You write what, not how.

Every run is fully observable. Trace the entire execution graph with kb workflow runs watch

Real workflows

Workflows we ship on ourselves.

✓

Release pipeline

lint → type-check → test → AI review → QA gate → build → publish. Every step traced.

✓

AI code review

On every commit or PR: diff → LLM review → inline comments → approval gate.

✓

QA regression tracker

Recurring checks on every change. Surfaces trend degradation before it ships.

✓

Agent workflow

Autonomous agents as first-class steps. Same permissions model, same observability.

pr-review-gate.yamlyaml

name: pr-review-gate
on:
  github:
    event: pull_request.opened

jobs:
  validate:
    steps:
      - id: run-tests
        run: builtin:shell
        with:
          cmd: pnpm test --coverage

      - id: ai-review
        run: plugin:@kb-labs/review#run
        with:
          pr: ${{ inputs.PR_NUMBER }}
          model: claude-sonnet-4-6

      - id: gate
        run: builtin:gate
        with:
          condition: ${{ steps.ai-review.score >= 7 }}

Primitives

Three building blocks.

Every workflow — from a two-step script to a multi-day process — is built from these three primitives.

builtin:shell

Runs any shell command — scripts, CLI tools, your own binaries. Output is logged and available to downstream steps.

runwithenvartifacts

builtin:gate

Conditional routing with named routes and iteration limits. Directs the workflow to a branch or restarts a step with fresh context.

routesmaxIterationsrestartFrom

builtin:approval

Pauses the workflow and waits for a human decision. Supports approve/reject with an optional comment.

approverejectcomment

Triggers

Start from anything.

Workflows trigger on schedules, webhooks, API calls, or manually from the CLI.

CLI

Studio

Schedule

API callbeta

Git pushsoon

Pull requestsoon

+ custom trigger

Use cases

What teams use workflows for.

Release automation

Declarative release pipeline that runs every time. No scripts to remember.

AI-assisted review

LLM review as a gated step — runs after lint, blocks merge on issues.

QA trend tracking

Recurring quality checks that surface regression signals before they ship.

Agent orchestration

Autonomous agents as workflow steps with sandboxed permissions.

Deploy coordination

Build → push → pull → restart — orchestrated with health verification.

Custom automation

Any engineering process that runs more than once belongs in a workflow.

Get started

Replace your script chaos with workflows.

Install KB Labs and run your first workflow in under an hour. No cloud dependency, no sign-up.

Install Read the docs