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

# Niblet CLI overview

> Use one local tool for authoring, rendering, device pushes, and hosted app revisions.

The Niblet CLI is the branded Pixlet-compatible runtime. The primary command is `niblet`; an optional `pixlet` symlink preserves common upstream workflows.

## Main command groups

| Area                  | Commands                                                                              | Purpose                                            |
| --------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Local app work        | `serve`, `render`, `check`, `format`, `lint`, `profile`                               | Build and inspect Starlark on your computer        |
| Hosted apps           | `apps init`, `apps validate`, `apps preview`, `apps push`, `apps submit`, `apps list` | Create immutable developer releases                |
| Account               | `auth login`, `auth logout`                                                           | Manage the CLI OAuth session                       |
| Displays              | `devices`, `push`, `list`, `delete`                                                   | Work with account-owned displays and pushed images |
| Catalog compatibility | `community`, `create`, `schema`                                                       | Maintain compatible app projects and schemas       |

Run `niblet --help` or append `--help` to any command for the exact options in your installed release.

## Local and cloud boundaries

The CLI executes Starlark and creates images locally. Cloud endpoints store account state, display state, project metadata, and explicitly uploaded review artifacts. The developer dashboard is not a source editor or remote render farm.