Pipeline Server UI

The pipeline UI ships as part of @ucdjs/pipeline-server. The CLI starts it with ucd pipelines run --ui, and the server gives you a focused interface for debugging pipeline definitions and individual executions.

Start the server

./packages/cli/bin/ucd.js pipelines run --ui --cwd packages/pipelines/pipeline-playground

You can also choose a port:

./packages/cli/bin/ucd.js pipelines run --ui --port 4040 --cwd packages/pipelines/pipeline-playground

What the UI exposes

Source and pipeline browsing

The sidebar lets you switch sources, choose a pipeline file, and move between pipeline overview, inspect, and execution history.

Overview

The overview page summarizes:

• selected versions
• source and route counts
• pipeline include filter
• transforms and outputs
• recent executions

Inspect

Inspect mode is for static definition debugging:

• Routes: graph and route-level structure
• Transforms: where transforms are reused
• Outputs: output IDs, sinks, format, and path metadata

Executions

The executions pages focus on runtime behavior:

• execution history
• per-run status and timings
• timeline and traces
• captured logs
• execution graph for a specific run

Best use cases

Use the Pipeline Server when:

• you need to verify route dependencies visually
• you want to inspect output declarations without reading the source file
• you want logs and traces for one execution
• you need to compare recent runs of the same pipeline