Pipelines

Reusable, sequential workflows for your repositories. A Go CLI/TUI and native server reuse your OpenCode login; Docker ntfy handles phone notifications.

Install

Requires Go 1.27+ to install. Use your existing OpenCode for model stages; Docker/ntfy notifications are optional.

git clone https://git.a-wan.net/alan/pipelines.git
cd pipelines
go install ./cmd/...
pipelines help

Go uses GOBIN or its normal GOPATH/bin default; put that directory on PATH. ./install.sh runs the same installation. It installs binaries only—no login checks, dependency installers, hardcoded install paths, or automatic services. For system-wide use, install the binaries into your chosen system bin directory with the appropriate permissions. Configuration and data remain per-user.

Start explicitly; fresh databases contain no pipelines:

pipelines serve -workspace-root "$HOME"   # foreground server
# In another terminal:
pipelines

Optional autostart at login (starts the server now):

pipelines service enable --workspace-root "$HOME"
pipelines service status

Uses user-level systemd on Linux or launchd on macOS; no sudo. Prefer a narrower trusted repository root where possible. Preview with --print. Stop any existing foreground/legacy server first. Disable with pipelines service disable before uninstalling. See installation for environment and boot options.

Uninstall

pipelines uninstall          # remove Go binaries; keep history, drafts, and ntfy data

A three-stage pipeline

Plan → Implement → Review. Each stage receives the previous stage's output; the first receives your task prompt. One outcome selects the next stage—no parallel branches. Definitions use Markdown output, prompt, tools, configs, and edges blocks. For example:

# stage planner

```output
{ task, plan, acceptance_checks }
```

```prompt
Turn input.prompt into a focused plan and acceptance checks.
```

```tools
```

```configs
provider=opencode-go
model=deepseek-v4.1-flash
retries=0
```

```edges
success -> implementer
error -> #failure
```

The complete three-stage example adds the implementer and reviewer. Review and explicitly submit it:

pipelines validate examples/three-stage.md
pipelines submit examples/three-stage.md --name "three stage" --create-only
pipelines run "three stage"

Every submission is validated and creates an immutable version. Examples are optional; nothing is imported automatically. Go-file edits require explicit runtime tool approval and exact allowed paths.

Useful commands

pipelines                                  # dashboard; b browses templates
pipelines list
pipelines run                              # fuzzy selection + multiline prompt
pipelines run "bug fix" "Fix the layout"     # run in the current repository
pipelines new "daily digest" "Summarize changes"
pipelines edit "bug fix" "Add a review step"
pipelines drafts --json
pipelines validate /path/to/draft.md
pipelines submit /path/to/draft.md           # explicit publication
pipelines runs
pipelines inspect 1
pipelines serve                            # foreground server; Ctrl+C stops it
pipelines ping
pipelines help edit

new/edit open OpenCode with a preloaded pipeline-authoring skill. Changes stay as drafts by default; CLI and TUI share validation and draft storage. Most commands support --json for agents and scripts.

More: CLI · installation · pipeline format.

S
Description
No description provided
Readme 78 MiB
Languages
Dart 51.6%
Go 36.7%
JavaScript 7.6%
Python 3.4%
Kotlin 0.4%
Other 0.1%