[PiquelChips]

While piquelctl waits for a deployment, it shows one spinner line with the operation's current phase. You can't tell what already ran, what is left, or how long it will take, and in CI you get a line per phase change and nothing else.

Every command that waits for a deployment (deploy, apply/save/create that deploy, promote, restore, preview create/deploy, operation, env wait, preview wait) now follows the operation's timeline stream from #412 and draws its steps live:

⠹ Deploying 019a6f3e-…  ▕████████░░░░▏ 6/9  48.2 s  ~30.0 s left
  ✓ Fetch manifest  412 ms
  ✓ Build api       38.2 s  (usual 25.0 s)
  ⠹ Update api      3.2 s
  ○ Wait for api    ~30.0 s
  ○ Update web

• Done steps show how long they took, plus "(usual …)" only when that is far off the usual. Steps left show ~usual. Failed steps show their diagnostic summary, and retrying steps show which retry they're waiting for.
• The row redraws every 100 ms from the latest timeline. Running times and the time left are computed locally, so nothing is fetched per frame.
• At the end it prints how long the deployment took and, after a clean run, how long its steps usually take, then the final tree.
• Without a terminal, each step prints one line when it starts or changes. With --json, each change is a {"step":{…}} event on stderr. Results on stdout are unchanged. Ctrl-C still only stops watching.
• piqueld-client gains operation_timeline and operation_timeline_stream, with a small SSE reader. Streams have no per-request deadline; --wait-timeout bounds the wait, as for every other wait since fix(cli): keep waiting through daemon restarts and retried failures #418.
• Waiting follows fix(cli): keep waiting through daemon restarts and retried failures #418's rules through its Wait: once the daemon answered, a dropped stream, a restart or a busy daemon is retried with backoff, a failed attempt the daemon retries keeps the wait going, and --wait-timeout bounds it all. 45 s without a keep-alive counts as a drop, and a 503 refusing the stream switches to polling the timeline. Wait reports through the tree, so there is never a spinner as well.
• Phase::label() in piqueld-core names each step for people, so the dashboard can use the same labels.

Proved on a real dev instance: piquelctl held one timeline stream through a 79 s silent job step (counted with strace), and reruns print only the new run's steps; plus CLI and transport tests.

Reviewed with review-loop: 3 rounds with 3× Claude Opus 5.5 (GPT 6.1 Sol was out of credits; a Sol pass is still owed). Verdict: approved

Note

Written by Claude Opus 5.5 in Claude Code and reviewed by Claude Opus 5.5 (via T3 Code)

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: c485d6e4-113b-4954-9b70-907fa5b3d86e

Commits

Reviewing files that changed from the base of the PR and between eaabac1 and 7e27229.

Files selected for processing: 13

• apps/piquelctl/src/commands.rs
• apps/piquelctl/src/environments.rs
• apps/piquelctl/src/output/mod.rs
• apps/piquelctl/src/output/progress.rs
• apps/piquelctl/src/output/timeline.rs
• apps/piquelctl/tests/cli.rs
• crates/piqueld-client/src/client.rs
• crates/piqueld-client/src/lib.rs
• crates/piqueld-client/src/operations.rs
• crates/piqueld-client/src/sse.rs
• crates/piqueld-client/tests/transports.rs
• crates/piqueld-core/src/timeline.rs
• docs/user/reference/cli.md

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn