> ## Documentation Index
> Fetch the complete documentation index at: https://getfloo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# status

> floo status: is this folder's commit live on dev, and if not, why and what to run next.

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.

```text theme={null}
floo status [--app <name>] [--commit <sha>] [--wait]
floo status --preview <preview> [--app <name>]
```

Requires floo CLI v2026.11.09 or later (`floo update`). `--wait` replaced `deploys watch`.

## Flags

| Flag | Description |
| - | - |
| `--app APP` | App name or UUID. Without it, the app comes from `floo.app.toml` in the current folder |
| `--commit SHA` | The commit to ask about. A short SHA is expanded with git. Without `--app`, the default is the folder's `HEAD`; with `--app`, the newest dev deploy |
| `--wait` | Follow the commit's deploy until it finishes, then answer. It streams build output, so give agents `floo status --json` without it |
| `--preview PREVIEW` | A preview instead of dev: its slug, source branch, preview URL, or `#123`. See [Previews](#previews). Cannot combine with `--commit` or `--wait` |
| `--json` | Print the API's answer as JSON |

## What it says

| State | Example |
| - | - |
| Live | `The dev deploy of 4f2a9c1 is live at https://shop.getfloo.app.` |
| Building or deploying | `The dev deploy of 4f2a9c1 is building.` Next: wait, then run `floo status` again, or follow it with `floo status --wait --commit <sha>` |
| Failed | `The dev deploy of 4f2a9c1 failed: npm ci exited 1.` Next: fix it, commit, and run `floo deploy` again |
| Pushed to a branch dev doesn't deploy | The reason floo recorded for that push, for example to merge it into `main` |
| Never seen by floo | `floo has no dev deploy of 4f2a9c1.` Next: push it to the app's branch; `floo deploy` does this |

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.

```bash theme={null}
floo status --preview feat/foo --app my-app
floo status --preview https://my-app-preview-feat-foo-abcde.getfloo.app --json
```

```text theme={null}
  Resource     Type   Source  Status  Hydration  Provider ID  Expires  Reset
  redis:cache  redis  dev     ready   clone-dev  db_123       -        eligible
```

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`](https://getfloo.com/docs/cli/previews#reset).

## Examples

```bash theme={null}
# Is the folder's HEAD live on dev?
floo status

# Ask about another commit
floo status --commit 4f2a9c1

# Another app, newest dev deploy
floo status --app my-app

# Agent workflow: branch on the answer
floo status --json 2>/dev/null | jq '.data | {live, summary, next_step}'
```

## API

`floo status` reads [`GET /v1/apps/{app_id}/status?commit=<sha>`](https://api.getfloo.com/openapi.json), 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.