> ## 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.

# commands and docs

> CLI reference: floo commands and floo docs, the machine-readable command tree and topic index.

Two commands describe the CLI to an agent. Both are version-matched to the
installed binary, so they answer for the surface you actually have rather than
the surface this site documents.

Neither needs authentication.

## commands

Print the full command tree. In `--json` mode it is the canonical capability
list for an agent deciding what floo can do.

```bash theme={null}
floo commands
floo commands --json
```

### JSON output

```json theme={null}
{
  "success": true,
  "data": {
    "version": "2026.09.01.1",
    "commands": [
      {
        "name": "analytics",
        "usage": "floo analytics [APP]",
        "description": "View traffic analytics for an app or org",
        "requires_auth": true
      }
    ]
  }
}
```

`requires_auth` is `false` for the commands that work before `floo auth login`,
such as `init`, `preflight`, and `docs`. `version` is the installed CLI version,
which is what makes this list authoritative for the binary in front of you.

```bash theme={null}
# Commands an agent can run before the user has logged in
floo commands --json 2>/dev/null | jq -r '.data.commands[] | select(.requires_auth == false) | .name'
```

## docs

Print the topic index, or resolve one topic to its canonical URL on this site.
The CLI routes to the docs rather than carrying an offline copy, so a topic
never goes stale against the site.

```bash theme={null}
floo docs                  # every topic with a one-line summary
floo docs quickstart       # one topic: summary and URL
floo docs quickstart --json
```

### Arguments

| Argument | Description                                |
| -------- | ------------------------------------------ |
| `TOPIC`  | Topic to resolve. Omit for the full index. |

### JSON output

```json theme={null}
{
  "success": true,
  "data": {
    "topic": "quickstart",
    "summary": "End-to-end setup and first deploy",
    "url": "https://getfloo.com/docs/introduction",
    "cli_version": "2026.09.01.1",
    "schema_version": 2
  }
}
```

Without a topic, `--json` returns a `topics` array of `{name, aliases, summary,
url}`. Append `.md` to any returned URL for the Markdown source, which is the
form to hand an agent.

## Discovery order

When an agent needs to find the right command, this order gets there in the
fewest calls and never guesses at a flag:

1. `floo commands --json` for the capability list.
2. `floo <command> --help` for exact arguments and flags.
3. `floo docs <topic> --json` for the concept behind the command.

The shipped command tree is the source of truth. A command that exists in the
binary but not on this site is still real; the reverse is not.

## Related

* [CLI overview](/docs/cli/overview), the output contract and app inference shared by every command
* [Agent setup](/docs/guides/agent-setup), permissions and the JSON parsing contract