When you’re signed in, Rumus quietly keeps your settings consistent across the devices where you use the app. The mental model: anything that isn’t a credential or a device-specific binary syncs. Credentials and the like sync separately, encrypted, via the vault.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.
What syncs
| Category | Included |
|---|---|
| Appearance | Theme, accent color, terminal palette, language, terminal font (family, size, line height) |
| Keyboard shortcuts | Every custom binding |
| Privacy preferences | Telemetry / crash report toggles, sync toggles |
| AI settings | Smart-autocomplete on/off, todo-list toggle, auto-collapse, max mode, command whitelist / blacklist |
| Rules & skills | Both lists, including enabled state, with tombstone deletes for proper propagation |
| Workspace settings | Workspace-level configuration (separate sync type) |
What doesn’t sync
| Category | Why |
|---|---|
| Custom AI models | Stored locally because they’re security-sensitive (API keys live in the vault, not in synced settings) |
| Local terminal profiles | Device-specific — paths to shells differ across machines, WSL distros differ, etc. |
| Conversation history | Local to each device today |
| Tabs and open workspaces | Live state, not configuration |
When sync runs
Sync runs:- At sign-in — pulls down whatever the cloud has and reconciles with local.
- Periodically in the background — currently every ~30 minutes for profile refresh.
- On demand — there’s a Sync Now button in Settings → Privacy → Sync (or the equivalent panel where the sync toggles live).
Conflict resolution
Most settings sync is per-field with a “newest wins” merge — if you change theme to Dark on your laptop and accent color to Green on your desktop, both changes take effect after sync. For rules and skills (which are lists), Rumus uses soft delete tombstones so deletions from one device propagate cleanly without resurrecting items from a stale snapshot on another. The harder cases — vault data conflicts where two devices made changes to the same encrypted item — are handled differently; see Vault sync & recovery.Turn sync off
If you’d rather not sync at all, Settings → Privacy → Sync has toggles for each sync category. Turning a category off:- Stops pushing changes from this device.
- Stops pulling cloud changes onto this device.
- Doesn’t delete anything that’s already in the cloud — it just isolates this device.
Telemetry and crash reports
Adjacent to sync — and equally optional — Rumus can send anonymous telemetry and crash reports to help fix bugs and prioritize features. Toggles live in Settings → Privacy. Both are independent of sign-in: you can be signed in with telemetry off, or signed out with telemetry on.Privacy
- Synced settings are sent to Rumus’s API over TLS and stored on Rumus servers.
- Settings are not encrypted with your secret key the way vault data is — they’re configuration, not credentials. Don’t put secrets into a rule or skill (use vault-stored credentials instead).
- Conversation history isn’t synced today — it lives only on the device where you had the conversation.
Next steps
Vault & encryption
The separate, end-to-end-encrypted store for your secrets.
Vault sync & recovery
How encrypted vault data flows between devices, and what to do on a fresh install.