Command Aliases
Command aliases let you keep familiar spellings when coming from another harness. Each alias resolves to an existing namespace command; the target owns the behavior and receives the arguments unchanged.
Declared aliases
This is the complete alias list declared for the command surface in the agent and model registries consumed by Link Harness. Each mapping links to its declaration and the namespace command list provides the primary names. Availability follows the target, so an alias grants no additional capability and has no independent switch.
/btw→/chat:ask/clear→/chat:create/compact→/chat:compact/context→/model:context/cost→/model:usage/export→/chat:export/fork→/chat:fork/goal→/chat:goal/learn→/skill:write/loop→/task:schedule/model→/model:set/models→/model:list/new→/chat:create/ps→/task:list/queue→/chat:queue/rename→/chat:rename/resume→/chat:resume/side→/chat:ask/skills→/skill:list/status→/chat:status/steer→/chat:steer/stop→/chat:stop/tasks→/task:list/tools→/tool:list/usage→/model:usage/verbose→/chat:verbose/whoami→/agent:show
Choose a spelling
Use the namespace form in new documentation and automation so the
subject and action stay visible. Use an alias when it matches a command
you already know. For example, /clear and /new both resolve to
/chat:create; /model <name> resolves to /model:set <name>.
Shared execution
Alias lookup selects the same command object as the namespace name; it has no separate handler. The target's owner checks, argument rules, spec switch and grants apply to either spelling. An unavailable target has no usable alias. Commands explains when a slash message is treated as ordinary text and how each command behaves.
Other slash names
Root-level /help is its own discovery command. It is not an alias.
Skills supply reusable prompts, and their loading and invocation depend
on the harness; see Skills.
A native command offered by another harness is not automatically a Link
alias. Only the mappings declared above belong to this inventory.