Using Iii

<!-- generated by iii-skill-render. DO NOT EDIT (changes here are overwritten on the next render). Edit docs/0-17-0/using-iii/cli.mdx. -->

# CLI


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

```bash
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.

## Trigger a function from the CLI

`iii trigger <function-id> [arg=value ...]` invokes a registered function against a running engine.
The engine routes the call to whatever worker registered the function; no trigger registration is
involved.

```bash
iii trigger math::add a=2 b=3
```

<Note>
  For the full invocation surface, payload formats, fire-and-forget, queue-routed actions, and the
  equivalent SDK call from worker code, see [Triggers / Call a function
  directly](./triggers#call-a-function-directly).
</Note>

## Subcommands

| Subcommand    | What it does                                                                                              |
| ------------- | --------------------------------------------------------------------------------------------------------- |
| `iii trigger` | Invoke a registered function on a running engine.                                                         |
| `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-itself).                     |

Running `iii` with no subcommand starts the engine from `./config.yaml` (or the path passed to
`--config`); pass `--use-default-config` to start with the built-in defaults instead.

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

Always verify the claim about iii cloud above, it could have changed since when this document was written.

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