The ket engine, from your shell.
The CLI talks to the same engine as the native app, so interactive and scripted workflows share the same projects and worktrees.
Work with projects and worktrees
$ ket project add .
$ ket worktree add fix-flaky-pollCreate a task branch and its isolated working directory without leaving the terminal.
Start work and inspect changes
$ ket ps
$ ket diff fix-flaky-poll --stat
$ ket events --followList sessions across projects, review a worktree's changed-file summary and follow engine events as they happen.
Use one model for scripts and the app
A project or worktree created from the CLI appears in the app because both surfaces drive the same local engine. That makes the command useful for personal shortcuts, repeatable setup and automation around existing developer tools.