> ## Documentation Index
> Fetch the complete documentation index at: https://motiadev-mintlify-e5ee0082.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the iii CLI to run and manage your system

> Use the iii CLI to discover subcommands, trigger functions, start the engine, and manage workers and config from the terminal in local and deployed systems.

For the most current list of commands, flags, and defaults, ask the binary directly:

```bash theme={null}
iii --help            #lists iii's flags and available subcommands
iii subcommand --help #lists the specific actions each sucommand accepts
```

Each subcommand's help also provides the defaults and environment variables that affect each
command.

<Note>
  The full CLI surface, including `iii worker` and `iii console`, is also published as an
  automatically generated [CLI reference](../cli-reference/index).
</Note>

## Subcommands

| Subcommand    | What it does                                                                                                             |
| ------------- | ------------------------------------------------------------------------------------------------------------------------ |
| `iii trigger` | Invoke a registered function on a running engine. See [Triggering functions](./functions#triggering-invoking-functions). |
| `iii worker`  | Manage workers: add, remove, list, start/stop, update, verify. See [Workers](./workers).                                 |
| `iii project` | Manage iii projects: scaffold a new one, generate Docker assets. See [Deployment](./deployment).                         |
| `iii console` | Launch the iii web console. See [Console](./console).                                                                    |
| `iii cloud`   | Manage hosted iii deployments. See [Managing iii Cloud deployments](#managing-iii-cloud-deployments).                    |
| `iii update`  | Update iii and its managed binaries. See [Updating iii itself](#updating-iii).                                           |

Running `iii` with no subcommand starts the engine from `./config.yaml` (or the path passed to
`--config`). When the file doesn't exist yet, `iii` offers to create it with an empty workers list
(and creates it without asking in non-interactive sessions); add workers with `iii worker add`.

## Managing iii Cloud deployments

The `iii cloud` subcommand group will manage hosted iii deployments. See
[Deployment](./deployment#iii-cloud-deployments) for details about the iii cloud.

<Note>iii's cloud will be available soon.</Note>

## Updating iii

`iii update` refreshes iii and its managed binaries to their latest versions. This is distinct from
`iii worker update`, which refreshes pinned worker versions inside a project.

<Note>
  Specific targets can be updated individually via `iii update [target]`. Run `iii update   --list-targets` to see the list of targets.
</Note>