> ## Documentation Index
> Fetch the complete documentation index at: https://www.rumus.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign up & sign in

> Create a Rumus account, sign in with GitHub or email, and what happens after.

Rumus is usable without an account — local terminal, profiles, and bring-your-own-key AI all work signed out. Signing in unlocks the rest:

* **Built-in AI models** included with [Pro](/docs/models/built-in).
* **Cloud sync** for your settings — see [Config sync](/docs/account/sync).
* **Encrypted vault sync** so your hosts and credentials follow you across devices — see [Vault sync](/docs/account/vault-sync).
* **Invitation codes** and other account features.

## Sign in methods

Rumus supports two ways to sign in:

* **GitHub OAuth** — one click, browser handoff, done.
* **Email + verification code** — enter your email, get a code, paste it back.

Other OAuth providers (Google, Apple) aren't supported today.

## Sign in

<Steps>
  <Step title="Open the menu">
    Click the **menu button** at the far right of the title bar.
  </Step>

  <Step title="Click Sign In">
    The sign-in dialog opens.
  </Step>

  <Step title="Choose a method">
    * **Sign in with GitHub** — opens a browser window. Authorize the Rumus app, then return to Rumus; the dialog closes automatically.
    * **Sign in with email** — type your email, click Send code, and check your inbox. Paste the code back into Rumus.
  </Step>
</Steps>

## Sign up

The sign-up flow is the same as sign-in. The first time you sign in with a GitHub account or email that doesn't yet have a Rumus account, one is created automatically. There's no separate registration page.

## After signing in

The menu button shows your name / avatar instead of **Sign In**. Click it for:

* **Account** — go to the account page.
* **Sign out** — log this device out.

You can also visit your dashboard at [rumus.ai/dashboard](https://www.rumus.ai/dashboard) for usage, billing, and account settings beyond what's surfaced in the app.

## Sign out

Click the menu button → **Sign out**. The current device's session is terminated and your local user state is cleared.

What happens to your local data:

* **Vault** — stays on disk, encrypted, until you sign back in (or delete it manually).
* **Settings** — stay local; the next sign-in pulls down what's in the cloud and reconciles.
* **Conversation history** — local; not affected by sign-out.

The "log out everywhere" capability exists on the server but isn't exposed in the current client UI — sign-out today affects this device only.

## Multiple devices

Sign in on as many devices as you like. They all share the same account.

* Settings (appearance, AI, keyboard, rules / skills) sync via [config sync](/docs/account/sync).
* Hosts and credentials sync via [vault sync](/docs/account/vault-sync) — encrypted end to end.
* The current Rumus client doesn't show a list of active devices or let you revoke a specific one. That capability is on the server side and will surface in the client when device-management UI ships.

## Troubleshooting

<AccordionGroup>
  <Accordion title="GitHub OAuth opens but doesn't redirect back">
    Make sure your default browser is set correctly. Rumus listens for a deep-link callback — if your browser opens a different app, the callback won't reach Rumus. Check **Settings → Default Apps** on your OS.
  </Accordion>

  <Accordion title="The email verification code never arrived">
    Check your spam folder. If it's still missing, request a new code from the sign-in dialog. Codes are time-limited and one-time-use, so an old code won't work.
  </Accordion>
</AccordionGroup>

<Note>
  Have a sign-in problem we didn't cover? Ask in the [Rumus community](https://www.rumus.ai/community).
</Note>

## Privacy

* The sign-in token is stored locally and used to authenticate API requests on your behalf.
* GitHub OAuth grants Rumus the standard public profile + email scopes — nothing more.
* Email-code sign-in stores your email and a session token. The verification code itself is one-time-use.

## Next steps

<CardGroup cols={2}>
  <Card title="Config sync" icon="cloud-arrow-up" href="/docs/account/sync">
    What gets synced (settings, AI prefs, rules / skills) and what doesn't (profiles, models).
  </Card>

  <Card title="Vault & encryption" icon="lock" href="/docs/account/vault">
    Set up the encrypted vault so your hosts and credentials can sync safely.
  </Card>
</CardGroup>