Skip to main content
Answer one question in one call: is my commit live on dev? If it isn’t, floo status says why and prints the next command.
Requires floo CLI v2026.11.09 or later (floo update). --wait replaced deploys watch.

Flags

What it says

When the commit isn’t live, a last line names the commit dev serves now. A commit that went out inside a later deploy (several pushes close together build once) counts as that deploy. A newer redeploy of the commit dev serves still counts as live, and the answer names its state.

Previews

floo status --preview feat/foo shows a preview: its latest deploy and status, its URL, when it expires, and its preview-owned Postgres, Redis and Storage branches. It replaced previews status, previews resources list and previews resources show, which fail and name it.
With --json, managed_resource_branches holds every branch with its resource_key, status, hydration mode, provider ID and reset_blocked_reason, never a credential. Reset one with floo previews reset.

Examples

API

floo status reads GET /v1/apps/{app_id}/status?commit=<sha>, which takes a full 40-character SHA. The answer has live, summary, next_step, the app’s source, the deploy of that commit, the deploy dev is serving, and the last_push floo received. It also has next: the same step as next_step, written as the call to make from the CLI (next.cli), over HTTP (next.api) and from a chat connector (next.mcp). next is null when nothing is needed or the step is a person’s to take.