Commands

Every command works in the workspace of the folder it runs in: the nearest folder upwards with an itero.config.json. itero help <command> shows a command’s options.

Command	Does
itero daemon	runs the workspace: messages, schedules, watched files, steps
itero emit	sends a message, and says what it starts; --wait for its answer
itero workflows	each workflow, its runs and the last; whether the daemon runs
itero runs	the runs, or one run step by step
itero errors	the runs that ended in error, and why
itero check	reads every file and says what is wrong
itero which	where a workflow, action or connector of a name is
itero info	the workspace and its daemon: IDs, names, limits
itero args	sets an action’s or a connector’s data
itero config	sets a workflow’s settings, or shows them
itero secret	keeps a secret in the OS secret store
itero service	runs the daemon from login on
itero watch	for connectors: a line per change to a file or folder
itero help	the commands, or one command’s options

A day with itero, in four of them:

itero daemon                                   # in one terminal, left running
itero emit order.placed '{"order": 43}'        # from an app, a script, you
itero workflows                                # what ran, and what waits
itero runs misty-lake                          # one run, step by step