Commands

Commands let you save prompts you use often. Instead of typing the same request again and again, you can save it once and run it whenever you need it.

For example, you might save commands for:

Rewriting selected text
Turning notes into an email
Summarizing the current page
Translating copy
Cleaning up voice notes

Use A Command

Type / in the command bar to see your saved commands.

Keep typing to filter the list
Use the arrow keys to choose one
Press Enter to run it

You can also give a command its own keyboard shortcut.

Create A Command

Open Settings → Commands.
Click +.
Give it a short name, such as “Fix Grammar” or “Summarize”.
Write the prompt you want Atua to use.
Choose an output mode (see below).
If you want, assign a keyboard shortcut.

Share Commands

You can export one command or several commands as a JSON bundle and share that file with someone else.

To export:

Open Settings → Commands.
Click the Export button in the sidebar.
Choose one or more commands.
Save the JSON file.

To import:

Open Settings → Commands.
Click the Import button in the sidebar.
Pick a previously exported JSON file.
Review the commands and any MCP servers they depend on.
Click Import.

If an imported command depends on MCP tools from a server you do not already have, Atua shows that server in the import review and asks whether you want to install it. If you install it, Atua also enables the specific MCP tools that the imported command needs.

Shared command bundles include:

Command name
Prompt
Output mode
Per-command model settings
Tool access settings
MCP server definitions needed for the selected MCP tools

Shared command bundles do not include:

API keys
OAuth tokens
Client secrets
Custom header secrets
Local environment secrets

That means the person importing the file may still need to finish authentication for a remote MCP server such as Notion.

Context tags

Context tags are placeholders that pull in what you are already working on. Add them to your prompt using double curly braces, like {{selectedText}}.

Quick reference

Tag	What it captures	Captured when
selectedText	The text you have highlighted	When the command bar or command hotkey is triggered
appContext	The app you came from, plus the window title or browser URL when available	When the command runs
clipboardContent	Whatever text is currently on your clipboard	When the command runs
currentDate	Today’s date and time	Command runs
screenshot	A screenshot of the active window	Included only when used
ocr	Text read from the screen	Command runs
windowContent	The full content of the current page or window	Command runs
transcript	Voice input recorded and transcribed on-device	Command runs (prompts you to speak)

selectedText

Use this when you want Atua to work on the exact text you selected.

Example prompts:

Translate {{selectedText}} to Spanish. Keep the original formatting.

Rewrite {{selectedText}} to be more concise and professional.

appContext

Use this when the current app or page matters.

{{appContext}} gives Atua extra clues about where you came from.

Depending on the app, it can include:

The app name
The window title
The current browser URL

This is useful when you want Atua to understand not just the text, but the place it came from. For example, a page in Safari, a draft in Mail, or a document in Notion can all call for different output.

Example prompts:

Rewrite {{selectedText}} to match the tone implied by {{appContext}}.

You are assisting the user in this context: {{appContext}}. Adapt your response accordingly.

Save this page as a bookmark. Use {{appContext}} to capture the source and {{windowContent}} to understand the page.

clipboardContent

Use this when you copied something and want to bring it into the prompt without selecting it again.

Example prompts:

Compare {{selectedText}} with {{clipboardContent}} and highlight the differences.

Use {{clipboardContent}} as reference material to answer this question: {{selectedText}}

currentDate

Use this for anything time-sensitive.

Example prompts:

Draft a follow-up email. Reference that today is {{currentDate}} and the deadline is in 3 days.

screenshot

Use this when the visual layout matters, such as a chart, a UI, or an error message on screen.

Example prompts:

Describe what you see in {{screenshot}} and suggest improvements to the UI.

Draft a reply to the email shown in {{screenshot}} using {{selectedText}} as key points.

What error is shown in {{screenshot}}? How do I fix it?

ocr

Use this when the text is visible on screen but you cannot select it, such as a PDF, image, scanned page, or screenshot.

Example prompts:

Extract the total amount, date, and vendor from {{ocr}} and format as JSON.

Summarize the article text from {{ocr}} into 3 bullet points.

Translate all text from {{ocr}} to English.

windowContent

Use this when you want Atua to read the whole page or window instead of just the selected text.

Example prompts:

Summarize the content of this page using {{windowContent}} into 3 bullet points.

List all links and their destinations from {{windowContent}}.

What are the main topics covered on this page? Use {{windowContent}} to answer.

Extract all product names and prices from {{windowContent}} and format as a table.

transcript

Use this when speaking is faster than typing.

Example prompts:

Turn {{transcript}} into a meeting summary with action items and owners.

Clean up {{transcript}} into a well-structured email.

Convert these voice notes into a bullet-point list: {{transcript}}

Choosing the right tag

Use {{selectedText}} when you already highlighted what matters.

Use {{windowContent}} when you want Atua to read the whole page or window.

Use {{ocr}} when text is visible but not selectable.

Use {{screenshot}} when the look of the screen matters.

Use {{transcript}} when you want to speak instead of type.

Use {{appContext}} when the current app or page matters.

Writing prompts

You can combine tags in one prompt. A simple pattern that works well is:

Tell Atua what to work on
Tell it what you want back
Add any useful tags

Examples:

Summarize {{windowContent}} in 5 bullet points.

Rewrite {{selectedText}} for a customer email in {{appContext}}.

Turn {{transcript}} into meeting notes with action items.

Real-World Command Examples

These examples are a good starting point. You can save them as commands and adjust the wording to fit how you work.

Fix Grammar

Good for: cleaning up selected writing before you paste it back

Prompt:

Fix grammar, spelling, and punctuation in {{selectedText}}. Keep the original meaning and tone. Return only the corrected version.

Best output mode: Replace Selected Text

Reply In My Tone

Good for: drafting a response to an email, message, or comment

Prompt:

Draft a reply to {{selectedText}}. Use {{appContext}} to match the setting and tone. Keep it clear, friendly, and ready to send.

Best output mode: Show in Chat

Summarize This Page

Good for: articles, docs, or long internal pages

Prompt:

Summarize {{windowContent}} into 5 short bullet points. End with one sentence that explains why this page matters.

Best output mode: Show in Chat

Turn Voice Notes Into Tasks

Good for: spoken planning, meeting notes, or quick brain dumps

Prompt:

Turn {{transcript}} into a short task list. Group related items together, keep the wording practical, and flag anything that sounds like a follow-up.

Best output mode: Show in Chat

Create Reminders From Voice Notes

If you have the Reminders tool enabled, you can go one step further.

Prompt:

Read {{transcript}}, extract clear action items, and create reminders for them with the Reminders tool. Use short reminder titles and include due dates only when they are clearly mentioned.

Best output mode: Run in Background

Triage A Bug Report

Good for: bug reports, support messages, or copied error notes

Prompt:

Analyze {{selectedText}} and turn it into a structured bug summary with: issue, likely cause, steps to reproduce, user impact, and next action.

Best output mode: Show in Chat

Example Command: Bookmark To Notion

If you have the Notion MCP server connected, you can make a command that saves the page you are viewing directly to a Notion database.

Name: Bookmark to Notion

Prompt:

Look at the page I’m on. Use {{appContext}} to capture the source and URL. Use {{windowContent}} to understand what the page is about. Write a short summary, pick a few relevant tags, and save it to my bookmarks database in Notion. The database ID is d3155ef96c584bf090e1d8b1a7ee8940.

This works well in browsers because {{appContext}} includes the page URL and {{windowContent}} gives Atua the full page content. The Notion MCP server handles authorization through OAuth, so there are no API keys to manage.

Output modes

Each command can send the result somewhere different:

Show in Chat keeps the result in the command bar so you can review it first.
Replace Selected Text pastes the result over the text you selected.
Run in Background runs the command quietly, shows a small status bubble, and lets you check the result later in chat history.

Add A Shortcut

You can give a command its own keyboard shortcut. Select text in any app, press the shortcut, and run the command right away.

Set this up in Settings → Commands.

Choose A Different Model For One Command

Each command can use its own provider and model. This is useful if you want a fast model for quick edits and a stronger model for bigger tasks.

You can also adjust things like creativity and response length for each command.

Notes About Imported Commands

When you import commands:

Atua keeps the prompt and command settings
Imported commands are added as new commands instead of replacing existing ones
If a name already exists, Atua gives the imported copy a unique name
If the bundle includes MCP server dependencies, Atua can add those servers for you during import