> ## Documentation Index > Fetch the complete documentation index at: https://docs.clawker.dev/llms.txt > Use this file to discover all available pages before exploring further. # Command Aliases > Define shortcuts that expand to full clawker commands — shipped defaults, positional placeholders, and team sharing via project config Aliases are user-defined shortcuts expanded before execution: the alias value is appended to `clawker` in place of the alias name, and any further arguments are appended after it. They turn long, flag-heavy invocations into one-word commands. ```bash theme={"dark"} # Instead of typing this every time... clawker run --rm -it --agent dev @:claude --dangerously-skip-permissions # ...type this clawker claude dev ``` ## Shipped Defaults Clawker ships four aliases out of the box: | Alias | Expansion | What it does | | -------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `go` | `run --rm -it --agent $1 @` | Launch a disposable interactive agent on your default harness: `clawker go dev` | | `wt` | `run --rm -it --agent $1 --worktree $2 @` | Launch a default-harness agent on a fresh [worktree](/worktrees) ([caveats](/worktrees#worktree-caveats)) — `$2` is a `branch[:base]` spec: `clawker wt auth feature/auth:main` | | `claude` | `run --rm -it --agent $1 @:claude --dangerously-skip-permissions` | Launch a Claude Code agent with permission prompts skipped: `clawker claude dev` | | `codex` | `run --rm -it --agent $1 @:codex --yolo` | Launch a Codex agent with approvals and sandboxing bypassed: `clawker codex dev` | `go` and `wt` run whichever harness is your project default, so they pass no harness-specific flags — add your harness's own flags after the alias (`clawker go dev --dangerously-skip-permissions`). The per-harness aliases select their harness with `@:` and bake in its auto-approve flag, which is safe to skip inside the container's isolation. Defaults are always active — no setup required. They can be overridden (see [Deleting and Overriding](#deleting-and-overriding)) but never deleted. ## How Expansion Works The expansion may reference positional arguments as `$1`..`$N`; arguments beyond the highest placeholder are appended after the expansion. Without placeholders, all arguments are appended. ```yaml theme={"dark"} aliases: claude: run --rm -it --agent $1 @:claude --dangerously-skip-permissions lg: logs $1 --tail $2 ``` * `clawker claude dev --model opus` runs `clawker run --rm -it --agent dev @:claude --dangerously-skip-permissions --model opus` * `clawker lg web 50` runs `clawker logs web --tail 50` * Invoking an alias with fewer arguments than its highest placeholder is an error (`expansion references $2 but 1 given`) * Placeholders substitute before the expansion is tokenized (same model as the gh CLI), so an argument containing spaces splits into separate tokens through a bare `$1`. Quote the placeholder in the alias definition — `clawker alias set ex 'container exec "$1" sh'` — to keep the substituted value a single argument. ## Defining Aliases ```bash theme={"dark"} clawker alias set lg "logs \$1 --tail \$2" ``` `alias set` writes to the user-level `clawker.yaml` in your config directory, so the alias is available in every project. Overwriting an existing alias requires `--clobber`. Most shells expand `$1` before clawker sees it. Escape placeholders (`\$1`) or single-quote the expansion. You can also define aliases directly in any project config file under the `aliases` key — they apply automatically to anyone working inside that project: ```yaml theme={"dark"} # .clawker.yaml aliases: fable: container run --rm -it --agent fable @ --dangerously-skip-permissions --model "claude-fable-5" ``` ## Listing Aliases ```bash theme={"dark"} clawker alias list ``` The SOURCE column shows which file provides each alias (or `default` for shipped defaults). `--json`, `--format`, and `-q` are available for scripting. ## Sharing with Your Team ```bash theme={"dark"} clawker alias export ``` `alias export` publishes your active aliases into the project's own config file — the most local config file found in the walk-up (it never creates one). Committed aliases then apply automatically for everyone who works in the repository. Export skips shipped defaults, empty entries, and aliases the target file already provides. ## Deleting and Overriding ```bash theme={"dark"} clawker alias delete lg ``` `alias delete` removes the alias from **every** config file that defines it, so one delete clears the name. Every command that writes a file prints the absolute path it wrote. Shipped defaults are immutable — they can't be deleted, only overridden: ```bash theme={"dark"} clawker alias set go "run --rm -it --agent \$1 @" --clobber ``` Deleting an override restores the shipped default. ## Layering Aliases merge across every project config layer, like any other project config key — key by key, so different layers can each contribute aliases: 1. Project files discovered in the walk-up (closest to your working directory wins) 2. The user-level `clawker.yaml` in the config directory 3. Shipped defaults See [Configuration](/configuration#how-configuration-works) for the full layering model. ## Rules and Limitations * An alias can never shadow a built-in command — the real command always wins. * An alias may expand to another alias, but cyclic chains are skipped at startup. * Shell-style aliases (running arbitrary shell commands) are not supported — expansions always invoke clawker commands. * Because alias commands disable flag parsing, even `--help` is forwarded into the expansion. * Aliases in a repository's project config apply automatically when you work inside that project — review the `aliases` key of projects you clone. ## CLI Reference Create or update an alias List aliases with their source file Publish aliases into the project config Remove an alias from every file layer