Aura Docs
User-ready guide

Set up Aura, connect context, and teach it useful Cookbooks.

Aura is a personal AI assistant you can text. These docs explain what works today, how to connect tools, how Cookbooks run, and where Aura asks before taking important actions.

What you can text Aura

Prep my day from my calendar.
What needs my attention in email?
Turn this messy note into tasks.
Find people I owe replies to.
Draft a reply, but ask before sending.

Set up Aura

Sign in, choose a plan, connect Google Workspace, and text Aura a first simple request.

Get started

Use a Cookbook

Browse workflows, open the setup page, connect required tools, then text Aura with the prefilled prompt.

Browse Cookbooks

Teach Aura how to cook

Use Kitchen to turn repeated work into a private Cookbook you can review, approve, and optionally publish.

Open Kitchen

Setup

The fastest path from account to first useful text.

1

Create or log into your account

Use Log in for an existing account or Get Started for a new setup. Aura routes existing users back to the dashboard.

Log in
2

Connect the tools Aura needs

Go to Integrations and connect Google Workspace when you want email and calendar help. Aura supports multiple connected Google accounts, with plan limits shown before you add another account.

Open Integrations
3

Text Aura

Use the dashboard iMessage/SMS card or a Cookbook detail page. Cookbook Get Started opens Messages with a prompt ready to send.

Open Dashboard

Texting Aura

Aura works best when your request names the outcome.

Use short, natural requests. Aura can summarize, draft, organize, prep, and run approved Cookbook guidance based on the context and integrations available to your account.

When a Cookbook opens Messages, review the prefilled prompt and press send. That text is the handoff that tells Aura which workflow to use.

Good pattern

“Draft a reply to the important emails from this morning. Ask before sending anything.”

Integrations

Connect only the tools Aura needs for the workflow.

  • Google Workspace powers Gmail and calendar-aware workflows when connected.
  • Some integrations are native Aura connections; others may be handled through the integration provider layer.
  • Cookbook detail pages show required integrations before Get Started is available.
  • You can disconnect integrations from the Integrations page and may also revoke access directly at the provider.

Cookbooks

Cookbooks are reusable workflows Aura can follow from text.

  • Browse public Cookbooks in the marketplace.
  • Open a Cookbook detail page and review what Aura will do.
  • Connect required integrations first if the setup panel says they are missing.
  • Click Get Started to install or reuse your copy and open Messages with the prefilled text.
  • Aura uses the Cookbook as guidance and asks before sensitive actions.

Before Get Started

If a Cookbook needs Google Workspace or another tool, the setup panel appears before the action button. Connect those tools first.

Kitchen

Kitchen is where you teach Aura how to cook.

  • Describe the repeated work in plain language.
  • Add a Cookbook name, required tools, and confirmation preference.
  • Review the draft Aura creates: title, purpose, triggers, steps, and safety rules.
  • Approve it for private use or publish it if you want others to install a copy.
  • Track installs and payout eligibility without exposing private data.

Private unless published

Drafts stay private. Publishing is optional, and published Cookbooks should contain workflow instructions only.

Security & privacy

Useful workflows should not leak private context.

Never included in public Cookbooks

  • Private memory and Soul.md content
  • Email contents and account-specific messages
  • OAuth tokens, API keys, and credentials
  • Private drafts that you have not published
  • Billing records and internal security details

Sensitive actions stay approval-first

Cookbooks can guide Aura, but they do not grant permission to send messages, schedule events, purchase, delete, share private content, or modify external records without an approval path.

Billing

Plans should map to real product capacity.

  • Aura Pro is the self-serve plan for memory, on-demand email/calendar help, SMS/iMessage chat, and private Cookbooks.
  • Aura Max adds proactive daily-delegation features such as scheduled briefings and follow-up detection controls.
  • Aura Enterprise is custom-scoped for teams, managed setup, custom workflows, and governance planning.
  • Checkout is plan-specific. Existing subscriptions should continue using their current billing state unless changed through the product.

Troubleshooting

Common things users run into.

A Cookbook says I need an integration.

Open the Cookbook detail page and use the Connect button in Required setup. After connecting, return to the same Cookbook page.

My profile does not show an email yet.

Make sure Google Workspace is connected on the Integrations page. The connected account is separate from a wallet or phone identity.

Aura opened Messages with a prompt.

That is expected. Review the text, press send, and Aura will use the Cookbook prompt as context.

Aura cannot do something automatically.

Sensitive actions are approval-first. Aura may draft, summarize, or prepare an action before asking you to confirm.

Current limitations

What Aura does not claim yet.

  • Self-serve Google Workspace currently centers on one connected account per user.
  • Public developer APIs are not broadly launched from these docs.
  • Creator payouts are payout-ready tracking and review language, not guaranteed instant payments.
  • Enterprise controls such as SSO, SCIM, formal compliance packages, and custom retention policies require a custom Enterprise conversation.
  • Aura may ask for clarification when context, permissions, or integrations are missing.

Need a custom workflow, team rollout, or security review? Book a short setup call and we can scope what Aura can support today.

Contact Aura