Skip to main content
Sign in to BrowserOS and your data follows you everywhere. Your conversations, AI model settings, and scheduled tasks sync automatically to the cloud so you never lose your setup.

​
Why Sign In?

Without an account, everything stays on one device. Sign in and your data is backed up and available wherever you use BrowserOS.

Access anywhere

Open BrowserOS on a new device and your conversations, model settings, and scheduled tasks are already there.

Never lose your history

Chat history is saved to the cloud automatically. Clear your browser data or switch machines and everything is still available.

Settings follow you

Set up your AI models once. Your provider configurations sync across devices so you never re-enter the same setup twice.

Automations stay in sync

Create a scheduled task on your laptop and it appears on your desktop. Edits sync both ways.

​
How to Sign In

1

Open a new tab

Open a new tab in BrowserOS to see the home page.
2

Click Sign In

Click Sign In in the sidebar to open the login page.
3

Choose your sign-in method

Enter your email for a magic link, or sign in with Google.
4

Verify and you're in

Click the link in your email (or complete Google sign-in). BrowserOS starts syncing your data immediately.
Magic link sign-in means you never need to create or remember a password. Just enter your email and click the link.

​
What Gets Synced

Your full chat history syncs to the cloud as you go. Every message is saved in real time so you can pick up any conversation on another device. Locally, BrowserOS keeps your 50 most recent conversations. In the cloud, there is no limit.
Your configured LLM providers (OpenAI, Anthropic, Google, Moonshot, Azure, Bedrock, and others) sync across devices. This includes the model name, provider type, base URL, temperature, and context window settings.Your API keys are never synced. Sensitive credentials like API keys, access keys, and session tokens stay on the device where you entered them. You will need to re-enter API keys on each new device.
Your scheduled task configurations sync in both directions. Create a task on one device, edit it on another, and changes are merged automatically using timestamps to resolve conflicts. Only the schedule setup syncs (name, prompt, schedule type, and timing). Task run results and output stay on the device where the task ran.
Your name, profile picture, and account preferences sync across devices. Information you provide during onboarding (role, company) is also saved to your profile.

​
What Stays Local

Some settings are device-specific and do not sync to the cloud:
  • API keys and secrets for LLM providers
  • Memory (core facts and daily notes)
  • SOUL.md (assistant personality)
  • Theme (light/dark mode)
  • Workspace folder selection
  • Connected MCP servers
  • Workflows
  • Scheduled task results (run output stays on the device where the task ran)
This is intentional. Sensitive credentials never leave your device, memory and personality files stay private, and display preferences can differ between machines.

​
How Sync Works

BrowserOS uses a local-first approach. Your data is always saved on your device first, then synced to the cloud in the background.
1

Local save

Every action (sending a message, adding a provider, creating a task) is saved locally first. BrowserOS works fully offline.
2

Background sync

When you are signed in, changes are automatically pushed to the cloud. New chat messages sync in real time. Provider and task changes sync whenever they are updated.
3

Restore on new devices

When you sign in on a new device, BrowserOS pulls your conversations, model settings, scheduled tasks, and profile from the cloud and merges them with any local data.
If the same scheduled task is edited on two devices before they sync, BrowserOS keeps the version with the most recent timestamp.

​
Security

API keys never leave your device

Sensitive credentials like API keys, access keys, and tokens are excluded from cloud sync entirely.

Session-based authentication

Sign-in uses magic links or Google OAuth. No passwords are stored.

Scoped to your account

All synced data is tied to your user account and is not accessible to anyone else.

Sync failures are silent

If cloud sync fails (e.g., no internet), your local data is unaffected. Sync resumes automatically when connectivity is restored.