Skip to main content
ComponentsFeedback

Component · Feedback

Progress Steps

Pipeline/phase progress for builds and agent plans: queued→running→complete with waiting/skipped/warning/failed/retrying/cancelled; passive or interactive; narrow summary; Timeline/TaskRail projections.

Kind
widget
Input
interactive
Canvas
120×40

Live preview

Loading terminal preview.

Static terminal poster. Choose Run live to start the Rust demo.

Ghosttyprogress-steps/pipeline
Loading terminal poster…
○ loading posterNo input — rendered state only
Progress Steps · exact mounted Rust story

01 · Purpose

What it is for

Pipeline/phase progress for builds and agent plans: queued→running→complete with waiting/skipped/warning/failed/retrying/cancelled; passive or interactive; narrow summary; Timeline/TaskRail projections.

Best fit: Feedback · feedback · widget

02 · Behavior

What the mounted story proves

  1. 01

    ProgressSteps

    Representative 120×40 terminal state.

  2. 02

    Passive paint

    No keyboard or pointer action is claimed by this representative story.

  3. 03

    Evidence stays explicit

    10 covered · 6 partial · 0 missing axes.

03 · Implement

Install, then start from exact code

Install

cargo add termrock --git https://github.com/tailrocks/termrock.git --rev 5283c2acf9154d0cfcd37b1ffe821c00faf90ea2

Add TermRock once. Keep domain effects in the host application.

Minimal implementation

Exact Rust setup used by progress-steps/pipeline.

Open to load code.

04 · Adapt

Variants and composition

Variants

Use the preview Variant menu when alternate registered stories exist. Each selection mounts a fresh configuration.

Composition

Feedback · feedback · widget

05 · Reference

API, tokens, accessibility

API

ProgressStepsOpen source ↗

Tokens

DesignSystemInspect exact story code for roles and capability projection.

Accessibility

Input contract mountedNo input claim in the representative story.

Contract

Evidence in progress10/23 axes covered

06 · Go deeper

Advanced guidance

Ownership boundary

TermRock owns reusable terminal rendering and interaction state. The host owns domain data, policy, persistence, authorization, and side effects.

Evidence status

10 covered, 6 partial, and 0 missing contract axes. Missing evidence is not a behavior claim.