For the most current list of commands, flags, and defaults, ask the binary directly:Documentation Index
Fetch the complete documentation index at: https://iii.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
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.
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.
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. |
iii project | Manage iii projects: scaffold a new one, generate Docker assets. See Deployment. |
iii console | Launch the iii web console. See Console. |
iii cloud | Manage hosted iii deployments. See Managing iii Cloud deployments. |
iii update | Update iii and its managed binaries. See Updating iii itself. |
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
Theiii cloud subcommand group will manage hosted iii deployments. See
Deployment for details about the iii cloud.
iii’s cloud will be available soon.
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.
Specific targets can be updated individually via
iii update [target]. Run iii update --list-targets to see the list of targets.