Appendix B: CLI Command Reference
This document provides a reference for all the commands available in the worka command-line interface.
worka init
Scaffolds a new Worka pack in the specified directory, creating a starter template with all the necessary files.
Usage:
worka init [path] [options]
| Argument / Option | Description |
|---|---|
path | The directory to initialize the pack in. Defaults to the current directory (.). |
--tenant | The tenant name for the pack (e.g., your GitHub username). If omitted, the CLI will prompt for it. |
--name | The machine-readable name for the pack (e.g., my-cool-pack). If omitted, the CLI will prompt for it. |
--display-name | The human-readable name for the pack. If omitted, the CLI will prompt for it. |
worka dev
Starts a development server for a specific pack. This server provides hot-reloading, automatically recompiling your pack and notifying the Worka Host application whenever you save a file.
Usage:
worka dev [options]
| Option | Description |
|---|---|
--path <PATH> | The path to the pack you want to run in development mode. Defaults to the current directory (.). |
--port <PORT> | The port to run the development server on. Defaults to 5174. |
--with-zigbuild | Use cargo-zigbuild for cross-compiling a Rust MCP server. This is necessary if you are on Apple Silicon. |
worka bundle
Builds and packages your pack into a final, distributable .aip archive. This command performs production optimizations, cross-compiles backend code, and creates the final package.
Usage:
worka bundle [options]
| Option | Description |
|---|---|
--path <PATH> | The path to the pack you want to bundle. Defaults to the current directory (.). |
--output <PATH> | The directory where the final .aip file(s) will be saved. Defaults to the pack's directory. |
--target <TRIPLE> | Build for a specific target architecture only (e.g., x86_64-unknown-linux-musl). |
--with-zigbuild | Use cargo-zigbuild for cross-compiling a Rust MCP server. This is necessary if you are on Apple Silicon. |