alan 3704d98d4d Search field in the bar, refresh and Back as bar pieces, even Cupertino actions (F8/F28/F10/F11/F20/F1)
- Search: field, compact Kind menu and syntax help in the bar's actions pill;
  bounds shown only when truncated; rows with bold title, kind tag and one
  muted line; results run behind the bar in a start-aligned 840 column.
- AppSearchField: one search field per platform (Search, Schedules, Runs filter).
- BarIconButton: whole 44pt/48dp bar actions; Runs, bell and Pipelines icons
  use the same 44pt targets on Cupertino.
- Templates and Schedules pages put Refresh in the bar and use the shared
  round SegmentedBackButton; Templates shows one Back at a time.
- PipelineBackButton is the round segmented Back.
- notes/pages-fixes.md records the batch, tests and evidence.
2026-10-31 03:31:25 +00:00

Pipelines

Small, reusable AI workflows for coding, research, and everyday project work. Run them in your browser or terminal using your existing configured harnesses. Inspect each stage's output, file changes, artifacts, and recorded session.

Alpha: single-user, supervised work. Models can make mistakes and editing workflows can change files and run commands. Start in a disposable project; review results before trusting them. Provider charges may apply.

Install on macOS or Linux

Use a Git checkout and an already configured OpenCode installation. You also need Go 1.27+, Python 3.9+, Git, curl, a C compiler, and Node.js 18+. The installer checks prerequisites; it does not replace your harness or provider credentials. Pi can also be used when configured.

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

Native installation is the default: Pipelines runs on your host and reuses your existing harness setup. Follow the installer's connection details to open the web app (default http://localhost:8082/). Setup creates or reuses its private web sign-in credentials and enables startup at login. Run as your normal user in a working macOS launchd or Linux systemd user session. If no usable model default is configured, setup asks you to select one inside ./install; no separate configuration command or test generation is required.

For optional terminal commands, select the installation and add its binaries to PATH (use your custom prefix if you changed it):

export PATH="$HOME/.local/share/pipelines/bin:$PATH"
pipelines service enable
pipelines service status
pipelines doctor

See installation for autostart controls, custom ports, data locations, and troubleshooting. No sudo is needed. Keep the raw Pipelines and harness APIs private. Use the authenticated web proxy for browser access; do not expose the control APIs to the Internet.

Prefer Docker?

./install --docker

Docker remains optional, not the default. It uses its own persistent harness credentials and needs Docker Compose and Python 3. Do not start a second native server alongside it. Docker setup and migration.

Try a starter

In the web app, open Settings → Templates, select a starter, and create a pipeline. In the terminal, run pipelines and use :templates.

Choose a small code change, a read-only review, research, or a document utility. Starters use your task and selected project—not this repository's paths, stack, or accounts. They inherit configured model defaults. Templates are available immediately but are never published or run without your choice.

  1. Select the project directory on the server machine.
  2. Give the pipeline a specific task and run it.
  3. Inspect the report, stage visits, and any changed files.

For terminal use, launch from your project directory:

cd /path/to/your/project
pipelines
# After creating a pipeline:
pipelines run "your pipeline name" "Describe a small task"
pipelines runs
pipelines inspect 1

A browser on another machine does not upload that machine's project files. Recurring work uses separate saved run schedules, not workflow definitions. Reuse one pipeline with different prompts and timers; filter both Pipelines and Runs by scheduling state. For editing work, use version control and keep a backup. Cancellation and retries are not rollback; a new execution can repeat side effects.

Sessions and notifications

Pipelines records and exports stage sessions itself. A model stage cannot hand its result to the next stage until its session is settled and its export is verified. If export fails, the computed output is retained while export-only recovery waits; this is not a request to rerun the agent or make a human decision. See session capture.

Notifications have separate channels:

  • Web alerts: require the page to be open and browser permission where supported. Closed-app browser push is not implemented.
  • ntfy: optional phone notifications, independent of the Pipelines app. Removing the app does not unsubscribe an ntfy client.

See notification setup. The installer checks publishing, not actual delivery to your phone.

More

When reporting a problem, include your OS, install mode, reproduction steps, pipelines version --json, and pipelines ping --json. Redact credentials and private task/file content; do not post your database or native session storage.

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%