Commands

Yuna has two command surfaces: the local CLI (yuna) for setup and device management, and Telegram slash-commands for runtime control. Most day-to-day operation happens via plain Telegram messages — you only touch the CLI once per device.

CLI

Command	Description
`yuna init`	Interactive wizard: deploy server to Vercel, configure Telegram + Anthropic + Upstash, save local config
`yuna init --manual`	Scaffold the server to `./yuna-server/` instead of auto-deploying
`yuna add-device --code X --url Y`	Register this machine as a device using a one-time setup code from Telegram
`yuna start`	Run the device agent in the foreground. Long-polls for commands and executes them.
`yuna status`	Server health check + online/offline device list
`yuna reset`	Pointer to `/reset` on Telegram
`yuna create-code`	Pointer to `/create-code` on Telegram
`yuna revoke-device <name>`	Pointer to `/revoke` on Telegram
`yuna logs`	Pointer to `/logs` on Telegram
`yuna --help`	All of the above

Send any of these as a message to your bot. Slash-commands are instant; plain-text messages go through Claude and may dispatch tool calls to your devices.

Slash-commands

Command	What it does
`/start`	Welcome message and command reference
`/status`	Device list with 🟢/🔴 online status and last heartbeat
`/reset`	Clear conversation history
`/create-code`	Generate a one-time device setup code (10-min TTL, single-use)
`/revoke <name>`	Revoke a device's token (instant — the Redis key is deleted)
`/logs`	Last 20 audit log entries (commands + errors)

Model overrides

Prefix any message to pick the model for that turn:

Prefix	Model	Rough cost
`@haiku` (default)	Claude Haiku 4.5	~$0.001/msg
`@sonnet`	Claude Sonnet 4.6	~$0.01/msg
`@opus`	Claude Opus 4.6	~$0.05/msg

@opus explain why my build is failing
@sonnet draft a changelog for v0.2
what's 2+2       # → direct answer, no tools, Haiku

Emoji reactions

React to any message Yuna sent to drive the next turn without typing. For risky-command confirmations, 👍 approves and ❌ cancels.

Emoji	Meaning
👍 / ❤️ / ✅ / 🚀	Yes, proceed / confirm / ship it
👎 / ❌	No, stop / cancel / revert
🔄	Retry the previous action

Natural-language examples

check my battery                 # routes to the right device
clean up /tmp on the laptop      # triggers the risk gate
copy build.tgz from mac to pi    # uses transfer_file if mesh-configured
what's the load avg everywhere   # parallel tool use across devices
@opus debug this stack trace ... # one-off model override