Commands & the Palette

Slash commands, @-mentions, the command palette, runbooks, and exporting chats — the power-ups that make the composer fast.

The composer and the command palette are where Dices gets fast. Slash commands expand saved prompt templates, @-mentions pull files into context, and the command palette (⌘K / Ctrl K) lets you jump anywhere, run runbooks, and start from an issue — all without leaving the keyboard.

Slash commands

Type / at the start of the composer to expand a saved prompt template. As you type, a suggestion list filters down; pick one and its full prompt drops into the composer, ready to send or edit.

Built-in commands

Examples

/review
/explain
/fix the login redirect loop
/tests for the new pricing module
/commit

A slash command is just a starting point — after it expands you can keep typing to add specifics, as in /fix the login redirect loop above.

Add your own

You can define your own slash commands in Settings. Give the command a name and the prompt template it should expand to, and it shows up in the / list alongside the built-ins.

Tip: Build slash commands for the prompts you retype constantly — your house code-style rules, your PR description format, your “summarize this thread” boilerplate. A good / library turns repetitive instructions into a single keystroke.

@-mentions

Type @ in the composer to fuzzy-pick from your project. There are two distinct behaviors depending on what you pick.

Mention a file — it gets attached

When you @-mention a file, Dices attaches it to the message. The agent reads the file’s contents directly, so you don’t have to paste code or describe where something lives.

Refactor the auth guard in @src/middleware/auth.ts to use the new session helper.

Mention a folder — it stays as text

When you @-mention a folder with a trailing slash (@folder/), it stays as plain text in your message. The agent treats it as a path it can list and explore on its own, rather than receiving the whole folder up front.

Take a look at @src/components/ and tell me which components are unused.

Note: Use @file when you already know the exact file the agent should read, and @folder/ when you want the agent to discover what’s inside for itself.

The command palette

Press ⌘K / Ctrl K anywhere to open the command palette — the universal jump-and-search surface in Dices.

What you can do from the palette

• Fuzzy-search chats — find any chat by name across all your Groups and Folders.
• Search message history — the palette searches inside your messages, not just chat titles, so you can find that one thing you said three days ago.
• Jump anywhere — select a result to jump straight to that chat or message.
• Run runbooks — type Run: … to launch a saved runbook.
• Start from an issue — kick off a new chat seeded from a Linear or GitHub issue (see Integrations).
• Open Settings — jump to configuration without hunting through menus.

Runbooks

Runbooks are saved, repeatable procedures you trigger from the palette with the Run: prefix:

Run: deploy staging
Run: nightly cleanup

Type Run: in the palette, pick the runbook, and Dices kicks it off — handy for the multi-step routines you’d otherwise have to remember and retype.

Keyboard navigation

Both the slash list, the @ picker, and the command palette share the same keyboard model, so the muscle memory carries over everywhere.

Tip: You almost never need the mouse here. Type / or @, use ↑/↓ to choose, and Tab or ⏎ to accept.

Export chat as Markdown

Any chat can be exported as Markdown from the chat-header menu. This gives you a clean, portable transcript of the whole conversation — useful for sharing a result, archiving a decision, or pasting context into a doc or ticket.

Next steps

• Voice input — dictate into the composer instead of typing.
• Integrations — start a chat straight from a Linear or GitHub issue.
• The Cockpit — how chats, folders, and groups fit together.