DETAIL PANEL · DEMO

Sample project review

Keep your context while reviewing the details.

Ready for review
Template route
/pulsefit/workflow-progress
Project
Riverside workspace (fictitious)
Owner
Morgan Lee (fictitious)

Summary

This is an original example. The underlying page stays visible while the panel holds the details. No account, payment or external service is connected.

Review note

Skip to content

Workflow progress (PulseFit) ​

A vertical workflow progress list in the PulseFit design language, inspired by the agent work components in this post: a connector line that is progressively drawn toward the active step, a pulsing marker and a subtle shimmer on the working label, sub-steps under the active step, and distinct pending, completed and approval states. Warm off-white with the PulseFit gold. Reinterpreted, not a copy. All names and data are fictitious.

Fee review report ​

An agent prepares a fee review: it collects data, compares validators, drafts the report with visible sub-steps, checks the numbers, and asks before sending. Use Run simulation to watch the connector draw itself from step to step; the last step waits for a simulated approval. This is a local animation. No agent runs and nothing is sent.

AGENT RUNFee review reportDraft
  1. Collect fee data
  2. Compare validators
  3. Draft the report
    1. Pulled 24 sources
    2. Wrote fee overview
    3. Writing validator section
  4. Check every number
  5. Send to teamAsks first

Ready. Local simulation only - nothing runs or sends.

Demo only. The run is a local animation; no agent executes and nothing leaves this page.

How to use it ​

Use workflow progress when a run has ordered stages and a user benefits from seeing work advance: agent runs, ingestion pipelines, review checklists. For free-form branching, use the node flow builder instead.

  1. One node per stage. Pending stages are hollow, the active stage pulses, completed stages fill with a check, and a stage that needs a person shows a lock with an "Asks first" chip.
  2. Draw the path, do not march it. The connector is drawn progressively toward the active step, so the line itself communicates progress.
  3. Show sub-steps under the active stage. Fine-grained work ("Writing validator section") belongs nested, with its own working state.
  4. Say the state in text. Durations, the working label and the status line carry the same information as color and motion.
  5. Honor reduced motion. With reduced motion, the line fills instantly and nothing pulses or shimmers; states still change.

Lateral detail drawer

Open a detail panel without losing the page behind it. This shared pattern follows the current template's colors. Fictitious data; actions stay local.