LLM/BrowserOS
1
0
Fork 0
mirror of https://github.com/browseros-ai/BrowserOS.git synced 2026-05-13 15:46:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: update docs (#404)

Browse Source 
* docs: update bring your own llm section

* docs: update mcp clients info

* chore: updated docs with comparison page

* docs: fix tool count

* docs: updated cowork section

* feat: connect apps screen

* feat: setup sync to cloud section

* feat: added soul.md

* feat: memory section

* feat: open claw comparison section

* feat: scheduled tasks page

* fix: info text

* feat: provide link to llms.txt

* fix: kimi section
This commit is contained in:
Dani Akash
2026-03-07 02:09:29 +05:30
committed by GitHub
parent a9bb4602cd
commit c38ceb49c1
12 changed files with 1717 additions and 119 deletions
Download Patch File Download Diff File Expand all files Collapse all files

201
docs/comparisons/chrome-devtools-mcp.mdx Normal file
View File

@@ -0,0 +1,201 @@
---
title: "Chrome DevTools MCP"
description: "A developer-focused comparison of BrowserOS MCP and Chrome DevTools MCP for browser automation"
---
Both BrowserOS MCP and [Chrome DevTools MCP](https://github.com/ChromeDevTools/chrome-devtools-mcp) give AI agents control over a browser via the Model Context Protocol. But they're built for different scopes. Chrome DevTools MCP focuses on debugging and inspection, while BrowserOS MCP is a complete browser automation and app integration platform.
This page breaks down the differences for developers evaluating which to use with Claude Code, Gemini CLI, Cursor, or any MCP client.
---
## At a Glance
| | **BrowserOS MCP** | **Chrome DevTools MCP** |
|---|---|---|
| **Total MCP tools** | 53 | 29 |
| **External app integrations** | 40+ (Gmail, Slack, GitHub, etc.) | None |
| **Setup** | Copy URL from settings, works instantly | Requires `--remote-debugging-port` flag and separate server process |
| **Browser session** | Your real browser with cookies, logins, extensions | Attached debug session (some sites block WebDriver-controlled browsers) |
| **Architecture** | Built into the browser | External Node.js process connecting via CDP |
---
## Feature Comparison
### Navigation & Tab Management
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Navigate to URL / back / forward / reload | `navigate_page` | `navigate_page` |
| Open new tab | `new_page` | `new_page` |
| Close tab | `close_page` | `close_page` |
| List open tabs | `list_pages` | `list_pages` |
| Switch to tab | `show_page` | `select_page` |
| Hidden/background tabs | `new_hidden_page` | - |
| Move tab between windows | `move_page` | - |
| Get active/focused tab | `get_active_page` | - |
| Wait for condition | - | `wait_for` |
### Content & Observation
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Accessibility tree snapshot | `take_snapshot` | `take_snapshot` |
| Enhanced structural snapshot | `take_enhanced_snapshot` | - |
| Page content as Markdown | `get_page_content` | - |
| Extract all page links | `get_page_links` | - |
| Raw HTML / DOM access | `get_dom` | - |
| Search DOM (text / CSS / XPath) | `search_dom` | - |
| Screenshot | `take_screenshot` | `take_screenshot` |
| Execute JavaScript | `evaluate_script` | `evaluate_script` |
### Interaction & Input
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Click element | `click` | `click` |
| Click at coordinates | `click_at` | - |
| Type / fill text | `fill` | `fill` |
| Fill entire form | - | `fill_form` |
| Type text (raw keystrokes) | - | `type_text` |
| Clear input | `clear` | - |
| Hover | `hover` | `hover` |
| Drag | `drag` | `drag` |
| Press key / key combo | `press_key` | `press_key` |
| Check / uncheck checkbox | `check` / `uncheck` | - |
| Select dropdown option | `select_option` | - |
| Focus element | `focus` | - |
| Scroll (directional) | `scroll` | - |
| Upload file | `upload_file` | `upload_file` |
| Handle dialog (alert/confirm) | `handle_dialog` | `handle_dialog` |
### File & Export
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Save page as PDF | `save_pdf` | - |
| Save screenshot to disk | `save_screenshot` | - |
| Download file via click | `download_file` | - |
### Window Management
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| List windows | `list_windows` | - |
| Create window | `create_window` | - |
| Create hidden window | `create_hidden_window` | - |
| Close window | `close_window` | - |
| Activate / focus window | `activate_window` | - |
### Tab Groups
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| List tab groups | `list_tab_groups` | - |
| Create tab group | `group_tabs` | - |
| Update group (title/color) | `update_tab_group` | - |
| Ungroup tabs | `ungroup_tabs` | - |
| Close tab group | `close_tab_group` | - |
### Bookmarks
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| List bookmarks | `get_bookmarks` | - |
| Create bookmark / folder | `create_bookmark` | - |
| Remove bookmark | `remove_bookmark` | - |
| Update bookmark | `update_bookmark` | - |
| Move bookmark | `move_bookmark` | - |
| Search bookmarks | `search_bookmarks` | - |
### History
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Search history | `search_history` | - |
| Get recent history | `get_recent_history` | - |
| Delete URL from history | `delete_history_url` | - |
| Delete history range | `delete_history_range` | - |
### Debugging & Performance
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Console messages | Coming soon | `get_console_message` / `list_console_messages` |
| Network request inspection | Coming soon | `get_network_request` / `list_network_requests` |
| Performance tracing | Coming soon | `performance_start_trace` / `performance_stop_trace` |
| Performance analysis | Coming soon | `performance_analyze_insight` |
| Memory snapshot | Coming soon | `take_memory_snapshot` |
| Lighthouse audit | Coming soon | `lighthouse_audit` |
| Device / network emulation | Coming soon | `emulate` |
| Resize viewport | Coming soon | `resize_page` |
### External App Integrations
| Feature | BrowserOS MCP | Chrome DevTools MCP |
|---------|:---:|:---:|
| Gmail, Outlook | Yes | - |
| Google Calendar, Outlook Calendar | Yes | - |
| Slack, Discord, Teams, WhatsApp | Yes | - |
| GitHub, GitLab | Yes | - |
| Linear, Jira, Asana, Monday, ClickUp | Yes | - |
| Notion, Google Docs/Sheets/Drive | Yes | - |
| Figma, Canva | Yes | - |
| Salesforce, HubSpot | Yes | - |
| Shopify, Stripe | Yes | - |
| 20+ more services | Yes | - |
---
## Setup Comparison
<Tabs>
<Tab title="BrowserOS MCP">
BrowserOS MCP is built into the browser. No separate process, no debug flags.
```bash
# One command, done
claude mcp add --transport http browseros http://127.0.0.1:9239/mcp --scope user
```
The server URL is available at `chrome://browseros/mcp`. Copy it and connect.
</Tab>
<Tab title="Chrome DevTools MCP">
Chrome DevTools MCP requires launching Chrome with remote debugging enabled and running a separate Node.js server.
```bash
# Step 1: Launch Chrome with debug port
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
# Step 2: Install and run the MCP server
npx @anthropic-ai/chrome-devtools-mcp@latest
# Step 3: Connect your MCP client to the server
```
Some sites may block sign-in when the browser is controlled via WebDriver (the default launch mechanism).
</Tab>
</Tabs>
---
## Summary
| Dimension | BrowserOS MCP | Chrome DevTools MCP |
|-----------|:---:|:---:|
| Browser automation tools | **54** | **29** |
| External app integrations | **40+** | **0** |
| Window management | Yes | No |
| Tab groups | Yes | No |
| Bookmarks & history | Yes | No |
| File export (PDF, screenshots, downloads) | Yes | No |
| Content extraction (Markdown, links, DOM) | Yes | No |
| Console / network inspection | Coming soon | Yes |
| Performance tracing & Lighthouse | Coming soon | Yes |
| Memory snapshots | Coming soon | Yes |
| Device emulation | Coming soon | Yes |
| Setup complexity | Copy URL | Debug port + Node server |
| Browser session | Real (cookies, extensions) | Debug-attached (WebDriver flags) |
BrowserOS MCP gives you a broader automation surface: browser control, content extraction, file operations, and 40+ app integrations through a single connection. Debugging and performance tools are coming soon to BrowserOS MCP, which will close the remaining gap with Chrome DevTools MCP. For most AI agent workflows, BrowserOS MCP already covers more ground out of the box.

161
docs/comparisons/claude-cowork.mdx Normal file
View File

@@ -0,0 +1,161 @@
---
title: "Claude Cowork"
description: "How BrowserOS Cowork compares to Claude Cowork for getting real work done with AI"
---
Both BrowserOS Cowork and [Claude Cowork](https://claude.com/product/cowork) let an AI agent work with your local files autonomously. You describe a task, step away, and come back to completed work. They share a similar file toolkit under the hood. The key difference is what else each product can do. BrowserOS Cowork runs inside a real browser with full web access and 40+ app integrations. Claude Cowork runs inside an isolated VM with professional document generation.
This page compares both products so you can decide which fits your workflow.
---
## At a Glance
| | **BrowserOS Cowork** | **Claude Cowork** |
|---|---|---|
| **Runs in** | Your real browser | Claude Desktop app (VM) |
| **File tools** | Read, write, edit, search, organize | Read, write, edit, search, organize |
| **Browser automation** | Yes, 53 tools (click, type, screenshot, navigate, etc.) | No |
| **App integrations** | 40+ (Gmail, Slack, GitHub, Calendar, Notion, etc.) | ~4 connectors (Google Drive, Gmail, DocuSign) |
| **AI model** | Your choice (Claude, GPT, Gemini, Kimi, local models) | Claude only |
| **Internet access** | Full (through your real browser) | Restricted |
| **Document generation** | Basic (HTML, Markdown, CSV) | Advanced (Excel with formulas, PowerPoint, formatted docs) |
| **Pricing** | Free (bring your own AI key) | Requires paid Claude subscription |
| **Platform** | Any OS with BrowserOS | macOS, Windows x64 |
---
## Feature Comparison
### File Operations
Both products provide a comparable set of file tools. You can read, write, edit, search, and organize files in both. This is table-stakes for both products.
| What you can do | BrowserOS Cowork | Claude Cowork |
|-----------------|:---:|:---:|
| Read and view files | Yes | Yes |
| Create and save new files | Yes | Yes |
| Edit specific parts of a file | Yes | Yes |
| Search inside files for text | Yes | Yes |
| Find files by name or pattern | Yes | Yes |
| List and browse folders | Yes | Yes |
| Run commands/scripts | Yes | Yes |
| Break work into parallel subtasks | Coming soon | Built-in sub-agents |
<Note>
The file tools are largely equivalent. The real differentiator is what else each product can do beyond file operations.
</Note>
### Working with the Web
This is the biggest difference. BrowserOS Cowork runs inside a real browser with your existing logins and sessions.
| What you can do | BrowserOS Cowork | Claude Cowork |
|-----------------|:---:|:---:|
| Open and navigate websites | Yes | No |
| Click buttons, fill forms, type text | Yes | No |
| Take screenshots of web pages | Yes | No |
| Extract content from web pages | Yes | No |
| Save pages as PDF | Yes | No |
| Download files from the web | Yes | No |
| Access sites where you're logged in | Yes (your real browser session) | No |
| Manage tabs, windows, and bookmarks | Yes | No |
| Search your browsing history | Yes | No |
Claude Cowork has no browser access. If your task involves anything on the web, whether that's researching, filling out forms, grabbing content from a site, or checking on a web app, you need BrowserOS.
### Connected Apps
BrowserOS connects to 40+ services directly. Claude Cowork has a handful of connectors.
| Service | BrowserOS Cowork | Claude Cowork |
|---------|:---:|:---:|
| Gmail | Yes | Yes |
| Google Drive | Yes | Yes |
| Google Calendar | Yes | Limited |
| Slack | Yes | No |
| GitHub | Yes | No |
| Linear / Jira / Asana | Yes | No |
| Notion | Yes | No |
| Figma | Yes | No |
| Salesforce / HubSpot | Yes | No |
| Shopify / Stripe | Yes | No |
| 30+ more services | Yes | No |
### Document Generation
Claude Cowork has an edge when it comes to creating polished office documents.
| What you can do | BrowserOS Cowork | Claude Cowork |
|-----------------|:---:|:---:|
| HTML and Markdown files | Yes | Yes |
| CSV and data files | Yes | Yes |
| Excel with working formulas | No | Yes |
| PowerPoint presentations | No | Yes |
| Formatted Word documents | No | Yes |
---
## How They Work
<Tabs>
<Tab title="BrowserOS Cowork">
BrowserOS Cowork runs inside the browser. The agent has access to your real browser session (cookies, logins, extensions) and a sandboxed folder on your computer.
- Works in your real browser with your existing logins
- File access sandboxed to the folder you select
- 40+ app integrations via OAuth
- Connect from any AI tool (Claude Code, Gemini CLI, Cursor, etc.)
- Uses whatever AI model you choose
</Tab>
<Tab title="Claude Cowork">
Claude Cowork runs in an isolated virtual machine on your desktop via the Claude Desktop app.
- Runs in a secure VM, isolated from your main system
- File access to folders you grant permission to
- ~4 connectors (Google Drive, Gmail, DocuSign, FactSet)
- Only works in the Claude Desktop app
- Uses Claude models only
- Comes pre-loaded with Python, Node.js, Ruby, and common tools
</Tab>
</Tabs>
---
## Where Claude Cowork Shines
- **Professional documents**: Create Excel spreadsheets with working formulas, PowerPoint presentations, and formatted Word documents
- **Parallel subtasks**: Automatically breaks complex work into smaller tasks that run at the same time
- **Stronger isolation**: Runs in a full virtual machine, giving you OS-level separation from your main system
- **Zero setup**: Works out of the box in the Claude Desktop app with pre-installed tools and languages
---
## Where BrowserOS Cowork Shines
- **Full browser access**: Navigate websites, fill forms, click buttons, take screenshots, and extract content from any page. Claude Cowork cannot touch the web.
- **Your real logins**: Because it runs in your actual browser, the agent can access sites where you're already logged in: dashboards, internal tools, social media, banking portals, anything.
- **40+ app integrations**: Gmail, Slack, GitHub, Calendar, Notion, Linear, Figma, Salesforce, and more. All accessible in the same session as your file work. Claude Cowork has about 4 connectors.
- **Pick your AI model**: Use Claude, GPT-5, Gemini, Kimi K2.5, or a local model. Claude Cowork only works with Claude.
- **Full internet access**: Your agent can visit any website. Claude Cowork's VM is restricted to a short list of allowed sites.
- **Free**: BrowserOS is free. Just bring your own AI API key. Claude Cowork requires a paid Claude subscription.
---
## Summary
| | BrowserOS Cowork | Claude Cowork |
|---|:---:|:---:|
| File tools (read, write, edit, search) | Yes | Yes |
| Browse the web | **Yes (53 tools)** | No |
| Connected apps | **40+** | ~4 |
| Internet access | Full | Restricted |
| Choose your AI model | Yes | Claude only |
| Works with other AI tools | Yes (Claude Code, Gemini CLI, Cursor, etc.) | Claude Desktop only |
| Excel, PowerPoint, Word | No | **Yes** |
| Parallel subtasks | Coming soon | **Built-in** |
| Security model | Folder-level sandbox | VM isolation |
| Platform | Any OS | macOS, Windows x64 |
| Pricing | Free + API key | Paid subscription |
Both products handle file operations equally well. The choice comes down to what else you need. If your work touches the web, connected apps, or you want to choose your own AI model, BrowserOS Cowork gives you that. If you need polished office documents and prefer a fully isolated desktop experience, Claude Cowork is a good fit.

143
docs/comparisons/openclaw.mdx Normal file
View File

@@ -0,0 +1,143 @@
---
title: "OpenClaw"
description: "How BrowserOS compares to OpenClaw for everyday AI assistance"
---
[OpenClaw](https://openclaw.ai/) is an open-source personal AI assistant that runs on your machine and connects through messaging apps like WhatsApp, Telegram, Slack, and Discord. It is a powerful tool for technical users who want a self-hosted, always-on AI agent.
BrowserOS takes a different approach. Instead of running a background server that you message through chat apps, BrowserOS puts the AI assistant directly inside your browser, where most of your work already happens. No terminal setup, no daemon management, no Node.js required.
This comparison is for users deciding which tool fits their needs.
## At a Glance
| | **BrowserOS** | **OpenClaw** |
|---|---|---|
| **What it is** | AI-powered browser with built-in assistant | Self-hosted AI agent you message through chat apps |
| **Setup** | Download and open | Install via npm, run onboarding wizard, configure daemon |
| **Technical skill needed** | None | Comfortable with terminal and Node.js |
| **Interface** | Built into your browser | WhatsApp, Telegram, Slack, Discord, iMessage, and 15+ more |
| **Browser automation** | 53 tools (clicks, forms, navigation, screenshots, tabs, bookmarks, history) | Chrome via CDP (snapshots and actions) |
| **App integrations** | 40+ built-in (OAuth or API key depending on the service) | Skills-based (community-built, self-installable) |
| **Memory** | Two-tier: permanent core facts + 30-day daily notes | Persistent memory across conversations |
| **Personality** | SOUL.md (inspired by OpenClaw's original concept) | SOUL.md (originated the concept) |
| **LLM support** | 11+ providers including local models (Ollama, LM Studio) | Multiple providers with failover routing |
| **Runs on** | macOS, Windows, Linux | macOS, Windows, Linux (+ iOS/Android companion apps) |
| **Authentication** | OAuth or API key depending on the service | API keys, OAuth, pairing codes per channel |
| **Open source** | Yes (AGPL-3.0) | Yes (MIT) |
## Where BrowserOS Shines
### No technical setup required
OpenClaw requires Node.js 22+, npm installation, a terminal-based onboarding wizard, daemon configuration (launchd or systemd), and channel pairing for each messaging platform. If something goes wrong, you need `openclaw doctor` to diagnose issues.
BrowserOS is a browser. Download it, open it, and start talking to the assistant. There is no daemon to manage, no services to keep running, and no terminal needed.
### Browser automation built in
BrowserOS gives the assistant full control of your browser with 53 tools: clicking buttons, filling forms, navigating between pages, taking screenshots, managing tabs, organizing bookmarks, searching history, and more. The assistant sees what you see and can interact with any website you are logged into.
OpenClaw has browser automation through a dedicated Chrome instance with CDP, but it runs as a separate process rather than being integrated into the browser you are already using. With BrowserOS, the assistant works directly in your browsing session with all your cookies, logins, and open tabs.
### 40+ app integrations built in
BrowserOS connects to Gmail, Google Calendar, Slack, Notion, GitHub, Linear, Jira, Figma, Salesforce, Stripe, and 30+ more services out of the box. Most services connect through OAuth (one-click sign-in), while some require an API key. Either way, the assistant detects when an app is not connected and walks you through the setup right in the conversation.
OpenClaw uses a skills system where integrations are community-built plugins. Some popular services have skills available, but connecting a new service often means finding the right skill, installing it, and configuring credentials manually.
### Works where you already are
Most of your work happens in a browser. BrowserOS puts the assistant right there, so it can see the page you are on, interact with web apps, and pull data from your open tabs. There is no context-switching between a chat app and your browser.
OpenClaw's approach of messaging through WhatsApp or Telegram is clever for mobile use, but when you are at your computer working in a browser, having the assistant inside that browser is more natural and more capable.
## Where OpenClaw Shines
### Messaging app access
OpenClaw connects to 20+ messaging platforms including WhatsApp, Telegram, Signal, iMessage, Discord, Slack, Microsoft Teams, and more. You can message your assistant from your phone or any chat app without opening a specific application. This is ideal if you want AI help on the go through apps you already have open.
BrowserOS is a desktop browser. To use the assistant, you need to be in BrowserOS.
### Always-on background agent
OpenClaw runs as a daemon on your machine, processing tasks even when you are not actively chatting. It supports cron jobs, webhooks, and Gmail Pub/Sub for automated triggers. It can wake up, do something, and report back through your messaging app.
BrowserOS has [scheduled tasks](/features/scheduled-tasks) that run automations on a schedule, but the browser needs to be running. OpenClaw's daemon approach is more suited for server-like always-on operation.
### Mobile companion apps
OpenClaw offers iOS and Android companion apps with camera access, voice input, screen recording, and device-level actions (notifications, contacts, calendar, SMS). This extends the assistant to your phone in a way that BrowserOS cannot currently match.
### Agent-to-agent communication
OpenClaw supports multi-session agent coordination where agents can discover each other, read transcripts, and send messages between sessions. This is useful for complex workflows where multiple specialized agents collaborate.
### Self-modifying skills
OpenClaw agents can write and install their own skills during a conversation. If the assistant does not have a capability, it can create one on the fly. This makes it extremely flexible for power users who want the agent to extend itself.
## Feature Comparison
### App Integrations
| Service | BrowserOS | OpenClaw |
|---------|-----------|----------|
| Gmail | Built-in (OAuth) | Skill + API setup |
| Google Calendar | Built-in (OAuth) | Skill + API setup |
| Slack | Built-in (OAuth) | Built-in channel |
| Discord | Built-in (OAuth) | Built-in channel |
| Notion | Built-in (OAuth) | Skill |
| GitHub | Built-in (OAuth) | Skill |
| Linear | Built-in (OAuth or API key) | Skill |
| Jira | Built-in (OAuth) | Skill |
| Figma | Built-in (OAuth) | Skill |
| Salesforce | Built-in (OAuth) | Skill |
| Stripe | Built-in (API key) | Skill |
| WhatsApp | Built-in (OAuth) | Built-in channel |
| Shopify | Built-in (OAuth or API key) | Community skill |
| Total integrations | 40+ built-in | 50+ via skills |
### Memory and Personality
| Feature | BrowserOS | OpenClaw |
|---------|-----------|----------|
| Persistent memory | Core facts (permanent) + daily notes (30 days) | Persistent across sessions |
| Memory location | Local files on your machine | Local files on your machine |
| Personality system | SOUL.md (inspired by OpenClaw) | SOUL.md (originated the concept) |
| Memory search | Fuzzy search across all memories | Context-based recall |
### Setup and Maintenance
| | BrowserOS | OpenClaw |
|---|-----------|----------|
| Installation | Download browser | `npm install -g openclaw`, run onboarding wizard |
| Runtime | Open the browser | Daemon process (launchd/systemd) |
| Updates | Auto-update | `openclaw update --channel stable` |
| Troubleshooting | Built-in | `openclaw doctor` CLI tool |
| Node.js required | No | Yes (v22+) |
| Terminal required | No | Yes |
## Who Should Use What
<CardGroup cols={2}>
<Card title="Choose BrowserOS if you..." icon="browser">
- Want an AI assistant without any technical setup
- Do most of your work in a browser
- Need browser automation (filling forms, clicking buttons, extracting data)
- Want 40+ app integrations that connect with one click
- Prefer a visual interface over terminal commands
</Card>
<Card title="Choose OpenClaw if you..." icon="terminal">
- Want to message your AI from WhatsApp, Telegram, or Signal
- Need an always-on agent that runs 24/7 as a background service
- Are comfortable with Node.js and terminal-based setup
- Want mobile companion apps for on-the-go access
- Need agents that can write their own extensions
</Card>
</CardGroup>
## Using Both Together
BrowserOS and OpenClaw are not mutually exclusive. Some users run OpenClaw as their always-on mobile assistant (accessible through WhatsApp or Telegram) while using BrowserOS as their desktop browser for work that involves web apps, browser automation, and visual tasks. The two tools complement each other rather than compete directly.

15
docs/docs.json
View File

@@ -29,10 +29,21 @@
"features/cowork",
"features/connect-mcps",
"features/use-with-claude-code",
"features/soul",
"features/memory",
"features/sync-to-cloud",
"features/llm-chat-hub",
"features/ad-blocking"
]
},
{
"group": "Comparisons",
"pages": [
"comparisons/chrome-devtools-mcp",
"comparisons/claude-cowork",
"comparisons/openclaw"
]
},
{
"group": "Integrations",
"pages": ["integrations/n8n"]
@@ -53,6 +64,10 @@
},
"navbar": {
"links": [
{
"label": "llms.txt",
"href": "/llms.txt"
},
{
"label": "Support",
"href": "https://discord.gg/YKwjt5vuKr"

135
docs/features/bring-your-own-llm.mdx
View File

@@ -18,15 +18,62 @@ See how to connect your own LLM in under a minute:
| Mode | What works | Recommendation |
|------|------------|----------------|
| **Chat Mode** | Any model, including local | Ollama or Gemini Flash |
| **Agent Mode** | Cloud models only | Claude Opus 4.5 or Kimi K2.5 (open source) |
| **Agent Mode** | Cloud models only | Claude Opus 4.5, GPT-5, or Kimi K2.5 (open source) |
<Warning>
**Local LLMs aren't powerful for most agentic tasks yet.** They're great for Chat — asking questions about a page, summarizing, etc. But agent tasks need strong reasoning to click the right elements and handle multi-step workflows. Use Claude Opus 4.5, Sonnet 4.5, or Kimi K2.5 for agents.
**Local LLMs aren't powerful for most agentic tasks yet.** They're great for Chat — asking questions about a page, summarizing, etc. But agent tasks need strong reasoning to click the right elements and handle multi-step workflows. Use Claude Opus 4.5, GPT-5, or Kimi K2.5 for agents.
</Warning>
<Note>
Kimi K2.5 is an open-source, multimodal model with great agentic performance — and 60-70% cheaper than Claude models.
</Note>
---
## Kimi K2.5 — In Partnership with Moonshot AI
{/* <img src="/images/moonshot-partnership-banner.png" alt="BrowserOS x Moonshot AI" className="rounded-xl" /> */}
BrowserOS has partnered with [Moonshot AI](https://www.kimi.com) to bring **Kimi K2.5** as a first-class provider. Kimi K2.5 is now the **recommended model** in BrowserOS and is set as the default provider.
For a limited time, BrowserOS users get **extended usage limits** powered by Kimi K2.5. This means you can use the AI agent, chat, and other AI-powered features with increased limits at no cost.
<CardGroup cols={2}>
<Card title="Open Source" icon="code-branch">
Fully open-source model you can inspect and trust.
</Card>
<Card title="Multimodal" icon="image">
Supports images out of the box, including screenshots and visual context.
</Card>
<Card title="Great for Agents" icon="robot">
Strong reasoning for browser automation, form filling, and multi-step workflows.
</Card>
<Card title="Affordable" icon="piggy-bank">
Excellent agentic performance at a fraction of the cost of other frontier models.
</Card>
</CardGroup>
<div id="moonshot" />
### Why Kimi K2.5?
Kimi K2.5 offers excellent performance for agentic tasks at a fraction of the cost of other frontier models. It supports images, has a 128,000 token context window, and delivers strong results on browser automation tasks. Combined with BrowserOS's open-source agent framework, this makes for a powerful and affordable AI browsing experience.
### Bring Your Own Kimi API Key
You can also bring your own Kimi API key if you want to use Kimi K2.5 beyond the extended usage period, or if you want your own dedicated limits.
**Get your API key:**
1. Go to [platform.moonshot.ai](https://platform.moonshot.ai) and create an account
2. Navigate to the **API keys** section in your dashboard
3. Click **Create new API key** and copy the key
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the **Moonshot AI** card
3. Enter your API key (it will be encrypted and stored locally on your machine)
4. The model is pre-configured to `kimi-k2.5` with a 128,000 context window
5. Click **Save**
<Tip>
The base URL for the Kimi API (`https://api.moonshot.ai/v1`) is pre-filled automatically when you select the Moonshot AI provider template.
</Tip>
---
@@ -49,7 +96,7 @@ Connect to powerful AI models using your API keys. Your keys stay on your machin
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the Gemini card
3. Set **Model ID** to `gemini-2.5-flash-preview-05-20`
3. Set **Model ID** to `gemini-2.5-flash` (or `gemini-2.5-pro`, `gemini-3-pro-preview`, `gemini-3-flash-preview`)
4. Paste your API key
5. Check **Supports Images**, set **Context Window** to `1000000`
6. Click **Save**
@@ -71,7 +118,7 @@ Connect to powerful AI models using your API keys. Your keys stay on your machin
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the Anthropic card
3. Set **Model ID** to `claude-opus-4-5-20250514`
3. Set **Model ID** to `claude-opus-4-5-20251101` (or `claude-sonnet-4-5-20250929`, `claude-haiku-4-5-20251001`)
4. Paste your API key
5. Check **Supports Images**, set **Context Window** to `200000`
6. Click **Save**
@@ -81,7 +128,7 @@ Connect to powerful AI models using your API keys. Your keys stay on your machin
<div id="openai" />
<Accordion title="OpenAI" icon="brain">
GPT-4.1 is solid for both chat and agent tasks.
GPT-5 is OpenAI's most capable model for both chat and agent tasks.
**Get your API key:**
1. Go to [platform.openai.com](https://platform.openai.com)
@@ -93,9 +140,9 @@ Connect to powerful AI models using your API keys. Your keys stay on your machin
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the OpenAI card
3. Set **Model ID** to `gpt-4.1`
3. Set **Model ID** to `gpt-5` (or `gpt-5.2`, `gpt-5-mini`, `gpt-4.1`, `o4-mini`)
4. Paste your API key
5. Check **Supports Images**, set **Context Window** to `128000`
5. Check **Supports Images**, set **Context Window** to `200000`
6. Click **Save**
![OpenAI config](/images/byollm--openai-provider-config.png)
@@ -107,10 +154,10 @@ Connect to powerful AI models using your API keys. Your keys stay on your machin
**Get your API key:**
1. Go to [openrouter.ai](https://openrouter.ai) and sign up
2. Copy your API key from the homepage
2. Go to [openrouter.ai/keys](https://openrouter.ai/keys) and create a key
**Pick a model:**
Go to [openrouter.ai/models](https://openrouter.ai/models) and copy the model ID you want (e.g., `anthropic/claude-opus-4.5`).
Go to [openrouter.ai/models](https://openrouter.ai/models) and copy the model ID you want (e.g., `anthropic/claude-opus-4.5`, `google/gemini-2.5-flash`).
![OpenRouter models](/images/openrouter-models.png)
@@ -123,6 +170,70 @@ Connect to powerful AI models using your API keys. Your keys stay on your machin
![OpenRouter config](/images/byollm--openrouter-provider-config.png)
</Accordion>
<div id="azure" />
<Accordion title="Azure OpenAI" icon="microsoft">
Use OpenAI models hosted on your own Azure subscription for enterprise compliance and data residency.
**Prerequisites:**
1. An Azure subscription with access to [Azure OpenAI Service](https://portal.azure.com/#view/Microsoft_Azure_ProjectOxford/CognitiveServicesHub/~/OpenAI)
2. A deployed model (e.g., GPT-4o) in your Azure OpenAI resource
**Get your credentials:**
1. Go to [portal.azure.com](https://portal.azure.com) → **Azure OpenAI** resource
2. Navigate to **Keys and Endpoint**
3. Copy **Key 1** and your **Endpoint URL**
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the Azure card
3. Set **Base URL** to your Azure endpoint (e.g., `https://your-resource.openai.azure.com/openai/deployments/your-deployment`)
4. Set **Model ID** to your deployment name
5. Paste your API key
6. Check **Supports Images**, set **Context Window** to `128000`
7. Click **Save**
</Accordion>
<div id="bedrock" />
<Accordion title="AWS Bedrock" icon="aws">
Access Claude, Llama, and other models through your AWS account with IAM-based authentication.
**Prerequisites:**
1. An AWS account with [Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/getting-started.html) enabled
2. Model access granted in the Bedrock console for your desired models
**Get your credentials:**
1. Go to the [AWS Console](https://console.aws.amazon.com) → **IAM**
2. Create or use an existing access key with Bedrock permissions
3. Note your **Access Key ID**, **Secret Access Key**, and **Region**
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the AWS Bedrock card
3. Set **Base URL** to your Bedrock endpoint (region-specific)
4. Set **Model ID** to the Bedrock model ID (e.g., `anthropic.claude-3-sonnet-20240229-v1:0`)
5. Paste your credentials
6. Check **Supports Images**, set **Context Window** to `200000`
7. Click **Save**
</Accordion>
<div id="openai-compatible" />
<Accordion title="OpenAI Compatible" icon="plug">
Connect to any provider that implements the OpenAI-compatible API format (e.g., Together AI, Fireworks, Groq, Perplexity).
**Add to BrowserOS:**
1. Go to `chrome://browseros/settings`
2. Click **USE** on the OpenAI Compatible card
3. Set **Base URL** to the provider's API endpoint
4. Set **Model ID** to the model you want to use
5. Paste your API key
6. Set **Supports Images** and **Context Window** based on the model
7. Click **Save**
<Tip>
Most newer AI providers support the OpenAI-compatible API format. Check your provider's docs for the base URL and available model IDs.
</Tip>
</Accordion>
</AccordionGroup>
---

247
docs/features/connect-mcps.mdx
View File

@@ -1,11 +1,9 @@
---
title: "Connect Apps (MCPs)"
description: "Link your apps to BrowserOS so the assistant can read data and take actions"
title: "Connect Apps"
description: "Connect 40+ apps to BrowserOS so the assistant can work with your email, calendar, projects, and more"
---
Connect your favorite apps to BrowserOS so the assistant can read your emails, check your calendar, post to Slack, update Notion, and more — all through natural conversation.
See how to connect an app and start using it with the assistant:
Connect your favorite apps to BrowserOS and let the assistant work across all of them. Read emails, check your calendar, create tasks, post messages, manage files, and more, all through natural conversation.
<video
controls
@@ -13,41 +11,181 @@ See how to connect an app and start using it with the assistant:
src="https://pub-80f8a01e6e8b4239ae53a7652ef85877.r2.dev/resources/feature-videos/4-MCP.mp4"
></video>
## What is MCP?
## How It Works
BrowserOS Connected Apps use the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/), an open standard for connecting AI assistants to external systems. Think of it as a single, consistent way to plug your apps into the assistant.
BrowserOS uses the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) to connect your apps. You do not need to install anything or manage API keys. Just sign in once and the assistant handles the rest.
## Built-in Apps
- **Gmail** — Send, read, and search emails
- **Google Calendar** — Create events, check your schedule
- **Google Docs** — Create and edit documents
- **Google Sheets** — Create and edit spreadsheets
- **Google Drive** — Upload, download, and manage files
- **Slack** — Post messages, manage channels
- **Notion** — Create pages, manage databases
- **LinkedIn** — Post updates, manage connections
## Smart App Connection
## Connect a Built-in App
When you ask the assistant to do something that needs an app you have not connected yet, it will detect this automatically and guide you through signing in, right in the conversation. No need to set things up in advance. You only sign in once per app, and it stays connected for future requests.
1. Go to **Settings → Connected Apps**
2. Click **Add built-in app** and select the app
3. Sign in and authorize BrowserOS
<Steps>
<Step title="You make a request">
Ask the assistant something like "What's on my calendar today?" or "Send an email to Sarah."
</Step>
<Step title="The assistant detects the app is not connected">
If you have not signed into that app yet, the assistant opens a sign-in page in your browser.
</Step>
<Step title="You sign in once">
Complete the OAuth sign-in. Your credentials are never stored in BrowserOS.
</Step>
<Step title="The assistant continues where it left off">
Once you confirm you are signed in, the assistant picks up right where it stopped and completes your request.
</Step>
</Steps>
{/* <Frame caption="The assistant detects an unconnected app and opens the sign-in page">
<img src="/images/connect-apps-smart-connection.png" alt="Smart app connection prompt in chat" />
</Frame> */}
You can also connect apps ahead of time from Settings if you prefer.
## Connect from Settings
<Steps>
<Step title="Open Connected Apps">
Go to **Settings > Connected Apps**
</Step>
<Step title="Add an app">
Click **Add built-in app** and select the app you want
</Step>
<Step title="Sign in">
Complete the OAuth sign-in when prompted
</Step>
</Steps>
<Frame caption="Connected apps show a green 'Authenticated' badge">
<img src="/images/connect-apps-settings.png" alt="Connected Apps settings page" />
</Frame>
## Use Connected Apps
## 40+ Supported Apps
Just ask the assistant what you want — it will automatically use the right connected apps.
BrowserOS connects to over 40 apps across every category you need.
<Frame caption="Ask naturally and the assistant uses your connected apps">
<img src="/images/connect-apps-query.png" alt="Asking what's on my calendar today" />
</Frame>
<AccordionGroup>
<Accordion title="Email" icon="envelope">
| App | What you can do |
|-----|----------------|
| **Gmail** | Send, read, and search emails, manage drafts and labels |
| **Outlook Mail** | Send, read, and manage emails |
| **Resend** | Send transactional and marketing emails |
</Accordion>
<Accordion title="Calendar and Scheduling" icon="calendar">
| App | What you can do |
|-----|----------------|
| **Google Calendar** | Create events, find free time, manage calendars |
| **Outlook Calendar** | Schedule meetings, manage events |
| **Cal.com** | Schedule meetings, manage availability |
</Accordion>
<Accordion title="Messaging" icon="comments">
| App | What you can do |
|-----|----------------|
| **Slack** | Post messages, manage channels |
| **Discord** | Send messages, manage servers |
| **WhatsApp** | Send messages, manage conversations |
| **Microsoft Teams** | Chat, meet, and collaborate |
</Accordion>
<Accordion title="Development" icon="code">
| App | What you can do |
|-----|----------------|
| **GitHub** | Manage repos, issues, and pull requests |
| **GitLab** | Manage repos, issues, and merge requests |
| **Vercel** | Deploy and manage web applications |
| **Postman** | Test and manage APIs |
| **Cloudflare** | Manage domains, DNS, and security |
| **Supabase** | Manage databases and backend services |
</Accordion>
<Accordion title="Project Management" icon="list-check">
| App | What you can do |
|-----|----------------|
| **Linear** | Create issues, manage cycles and projects |
| **Jira** | Create issues, manage sprints |
| **Asana** | Organize and track team projects |
| **Monday** | Manage work and team collaboration |
| **ClickUp** | Manage tasks, projects, and workflows |
</Accordion>
<Accordion title="Documents and Productivity" icon="file-lines">
| App | What you can do |
|-----|----------------|
| **Notion** | Create pages, manage databases |
| **Google Docs** | Create and edit documents |
| **Google Sheets** | Create and edit spreadsheets |
| **Google Drive** | Upload, download, and manage files |
| **Google Forms** | Create and manage forms and surveys |
| **Confluence** | Create and manage documentation |
| **Airtable** | Manage bases, tables, and records |
</Accordion>
<Accordion title="File Storage" icon="folder-open">
| App | What you can do |
|-----|----------------|
| **Dropbox** | Store and share files |
| **OneDrive** | Store and sync files with Microsoft |
| **Box** | Manage and share enterprise files |
</Accordion>
<Accordion title="Design" icon="pen-ruler">
| App | What you can do |
|-----|----------------|
| **Figma** | Access and manage design files |
| **Canva** | Create and manage designs |
</Accordion>
<Accordion title="CRM and Marketing" icon="chart-line">
| App | What you can do |
|-----|----------------|
| **Salesforce** | Manage leads, contacts, and opportunities |
| **HubSpot** | Manage contacts, deals, and marketing |
</Accordion>
<Accordion title="E-commerce and Payments" icon="cart-shopping">
| App | What you can do |
|-----|----------------|
| **Shopify** | Manage products, orders, and store |
| **Stripe** | Manage payments and subscriptions |
</Accordion>
<Accordion title="Analytics" icon="chart-bar">
| App | What you can do |
|-----|----------------|
| **PostHog** | Query analytics, manage feature flags |
| **Mixpanel** | Analyze user behavior and metrics |
</Accordion>
<Accordion title="Support" icon="headset">
| App | What you can do |
|-----|----------------|
| **Zendesk** | Manage support tickets and customers |
| **Intercom** | Manage customer messaging and support |
</Accordion>
<Accordion title="Search and AI" icon="magnifying-glass">
| App | What you can do |
|-----|----------------|
| **Brave Search** | Search the web privately |
| **Exa** | AI-powered semantic web search |
| **Mem0** | Store and retrieve AI memory |
</Accordion>
<Accordion title="Social and Content" icon="share-nodes">
| App | What you can do |
|-----|----------------|
| **LinkedIn** | Post updates, manage connections |
| **YouTube** | Access video info and transcripts |
| **WordPress** | Manage websites and blog content |
</Accordion>
</AccordionGroup>
## Example Prompts
The assistant figures out which apps to use based on what you ask. Just describe what you want in plain language.
<AccordionGroup>
<Accordion title="Calendar" icon="calendar">
- What's on my calendar today?
@@ -61,30 +199,56 @@ Just ask the assistant what you want — it will automatically use the right con
- Find emails about the Q4 budget from last week
- Send an email to the team with the meeting notes
</Accordion>
<Accordion title="Slack" icon="hashtag">
<Accordion title="Messaging" icon="hashtag">
- Post a message to #general saying I'll be out tomorrow
- What's the latest message in #engineering?
- Send a DM to Sarah asking if she's free for lunch
- Summarize what was discussed in #product today
</Accordion>
<Accordion title="Notion" icon="cube">
<Accordion title="Project Management" icon="list-check">
- Create a new Linear issue for the homepage redesign
- What are my open tasks in Jira?
- Move the "Launch campaign" task to complete in Asana
- Add a comment to the latest ClickUp task
</Accordion>
<Accordion title="Documents" icon="cube">
- Add "Review Q4 report" to my Notion tasks database
- Create a new page in my Projects database for the website redesign
- What are my open tasks in Notion?
- Update the status of the "Launch campaign" task to complete
</Accordion>
<Accordion title="Cross-app workflows" icon="diagram-project">
- Check my calendar for tomorrow, then draft an email to John summarizing what we're meeting about
- Find all emails from last week about the budget and create a summary in Notion
- Look at my Slack DMs and add any action items to my Notion tasks
</Accordion>
</AccordionGroup>
## Cross-App Workflows
The real power of connected apps is combining them in a single request. The assistant can pull data from one app and use it in another without you switching between tabs.
<CardGroup cols={2}>
<Card title="Email to task" icon="envelope">
"Find action items in my latest emails and add them to my Notion tasks"
</Card>
<Card title="Meeting prep" icon="calendar">
"Check my calendar for tomorrow, then draft an email to John summarizing what we're meeting about"
</Card>
<Card title="Bug triage" icon="bug">
"Test the checkout flow on our staging site, file a Linear issue if anything is broken, and post a summary to #engineering on Slack"
</Card>
<Card title="Sales pipeline" icon="chart-line">
"Pull my open deals from Salesforce and create a summary spreadsheet in Google Sheets"
</Card>
<Card title="Content roundup" icon="newspaper">
"Check the latest pull requests on our main repo and post a daily summary to #dev-updates on Slack"
</Card>
<Card title="Expense tracking" icon="receipt">
"Find all receipts in my Gmail from this month and organize them in a Google Sheet"
</Card>
</CardGroup>
## Add a Custom MCP Server
You can connect any MCP-compatible server that exposes an SSE endpoint.
1. Go to **Settings → Connected Apps**
1. Go to **Settings > Connected Apps**
2. Click **Add custom app**
3. Enter your server URL (e.g., `http://localhost:8000/sse`) and give it a name
@@ -123,16 +287,19 @@ Keep the terminal running while you use BrowserOS. The local server handles auth
</Accordion>
</AccordionGroup>
## Privacy & Security
## Privacy and Security
<Columns cols={3}>
<Card title="Your data stays local" icon="lock">
BrowserOS connects directly to your accounts. Credentials are stored locally on your machine.
<Columns cols={2}>
<Card title="Secure OAuth" icon="shield-check">
All apps use OAuth sign-in. BrowserOS never sees or stores your passwords.
</Card>
<Card title="On-demand only" icon="clock">
Apps are only accessed when you ask. Nothing runs in the background.
</Card>
<Card title="You control access" icon="toggle-on">
Connect or disconnect apps anytime in Settings.
Connect or disconnect any app at any time from Settings.
</Card>
<Card title="Secure OAuth" icon="shield-check">
Built-in apps use OAuth flows — BrowserOS never sees your passwords.
<Card title="Credentials stay local" icon="lock">
Your authentication tokens are managed securely and stored locally on your machine.
</Card>
</Columns>

152
docs/features/cowork.mdx
View File

@@ -1,9 +1,9 @@
---
title: "Filesystem Access"
description: "Give the assistant controlled access to local files and commands"
title: "Cowork"
description: "Give the agent controlled access to local files and commands alongside browser automation"
---
Filesystem Access lets you describe complex tasks and let the agent handle them end-to-end. Combine browser automation with local file operations — research on the web, then save reports directly to your folder.
Cowork lets you describe complex tasks and let the agent handle them end-to-end. It combines browser automation with local file operations: research on the web, then save reports directly to your folder. Read code, edit files, run shell commands, and search through your project, all in the same session as your browser tasks.
Here's what it looks like to give the agent access to your local files:
@@ -13,29 +13,38 @@ Here's what it looks like to give the agent access to your local files:
src="https://pub-80f8a01e6e8b4239ae53a7652ef85877.r2.dev/resources/feature-videos/3-filesystem-access.mp4"
></video>
## Why Filesystem Access?
## Why Cowork?
Without Filesystem Access, the agent can only interact with browser tabs. With Filesystem Access enabled, it gains full access to a folder on your machine:
Without Cowork, the agent can only interact with browser tabs. With Cowork enabled, it gains full access to a folder on your machine through 7 filesystem tools:
<Columns cols={3}>
<Card title="Read files" icon="file-import">
Access documents, data files, and more from your selected folder
<CardGroup cols={3}>
<Card title="Read & write files" icon="file-lines">
Read documents and data files, write reports, markdown, HTML, and other outputs
</Card>
<Card title="Write files" icon="file-export">
Save reports, spreadsheets, markdown, HTML, and other outputs
<Card title="Edit files" icon="pen-to-square">
Make targeted edits to existing files with surgical string replacement
</Card>
<Card title="Run commands" icon="terminal">
Execute shell commands within the folder
Execute shell commands within the sandboxed folder
</Card>
</Columns>
<Card title="Search content" icon="magnifying-glass">
Search file contents with regex or literal patterns across your project
</Card>
<Card title="Find files" icon="folder-tree">
Find files by glob pattern, with smart filtering of build directories
</Card>
<Card title="Browse directories" icon="list">
List directory contents with file sizes, sorted and organized
</Card>
</CardGroup>
The real power: do both browser automation AND file operations in a single task. Describe what you want, step away, and come back to finished work.
## Setting Up Filesystem Access
## Setting Up Cowork
<Steps>
<Step title="Open the Filesystem Access selector">
Click the **Filesystem Access** dropdown next to the prompt input
<Step title="Open the Cowork selector">
Click the **Cowork** dropdown next to the prompt input
</Step>
<Step title="Choose a folder">
Select a recent folder or click **Choose a different folder**
@@ -49,15 +58,106 @@ The real power: do both browser automation AND file operations in a single task.
<img src="/features/cowork/cowork-selector.png" alt="Select a folder for the agent to operate in" />
</Frame>
The agent is sandboxed to your selected folder — it cannot access files outside of it.
The agent is sandboxed to your selected folder. It cannot access files outside of it.
<Note>
Cowork is available in **Agent Mode** only. In Chat Mode, the agent works with browser tabs only.
</Note>
<Tip>
To disable file access, select **No folder** and the agent will work with browser tabs only.
</Tip>
## Filesystem Tools
Cowork provides 7 filesystem tools that the agent can use alongside browser automation:
<AccordionGroup>
<Accordion title="filesystem_read" icon="file-import">
Read a file from the filesystem. Returns text content with line numbers, or image data for image files (PNG, JPG, GIF, WEBP, BMP, SVG, ICO). Supports pagination through large files with `offset` and `limit` parameters.
| Parameter | Type | Description |
|-----------|------|-------------|
| `path` | string (required) | File path relative to working directory |
| `offset` | number (optional) | Starting line number (1-indexed) |
| `limit` | number (optional) | Max lines to read |
Responses are capped at 2000 lines or 50KB per request.
</Accordion>
<Accordion title="filesystem_write" icon="file-export">
Create or overwrite a file. Automatically creates parent directories if they don't exist.
| Parameter | Type | Description |
|-----------|------|-------------|
| `path` | string (required) | File path relative to working directory |
| `content` | string (required) | Complete file content to write |
</Accordion>
<Accordion title="filesystem_edit" icon="pen-to-square">
Make a targeted edit by replacing an exact string match. If the exact match fails, a whitespace-tolerant fuzzy match is attempted. Preserves original line endings (CRLF, CR, LF) and BOM.
| Parameter | Type | Description |
|-----------|------|-------------|
| `path` | string (required) | File path relative to working directory |
| `old_string` | string (required) | Exact text to find |
| `new_string` | string (required) | Replacement text |
Returns a side-by-side diff of the change.
</Accordion>
<Accordion title="filesystem_bash" icon="terminal">
Execute a shell command and return its output. Commands run in `sh`/`bash` on Unix or `cmd` on Windows.
| Parameter | Type | Description |
|-----------|------|-------------|
| `command` | string (required) | Shell command to execute |
| `timeout` | number (optional) | Timeout in seconds (default: 120) |
Output is truncated to the last 2000 lines if too large. Returns the exit code on failure.
</Accordion>
<Accordion title="filesystem_find" icon="folder-tree">
Find files matching a glob pattern. Searches recursively while skipping common build directories (`node_modules`, `.git`, `dist`, `build`, `.next`, `coverage`, `__pycache__`, and more).
| Parameter | Type | Description |
|-----------|------|-------------|
| `pattern` | string (required) | Glob pattern (e.g., `*.ts`, `**/*.json`) |
| `path` | string (optional) | Directory to search (default: working directory) |
| `limit` | number (optional) | Max results (default: 1000) |
Returns relative file paths sorted alphabetically.
</Accordion>
<Accordion title="filesystem_grep" icon="magnifying-glass">
Search file contents using regex or literal string matching. Skips binary files and files over 2MB.
| Parameter | Type | Description |
|-----------|------|-------------|
| `pattern` | string (required) | Search pattern (regex by default) |
| `path` | string (optional) | Directory or file to search |
| `glob` | string (optional) | Filter files by glob (e.g., `*.ts`) |
| `ignore_case` | boolean (optional) | Case-insensitive search |
| `literal` | boolean (optional) | Treat pattern as literal string |
| `context` | number (optional) | Lines of context around matches |
| `limit` | number (optional) | Max matches (default: 100) |
</Accordion>
<Accordion title="filesystem_ls" icon="list">
List directory contents. Shows directories first (with trailing `/`), then files with human-readable sizes.
| Parameter | Type | Description |
|-----------|------|-------------|
| `path` | string (optional) | Directory path (default: working directory) |
| `limit` | number (optional) | Max entries (default: 500) |
Entries are sorted alphabetically, case-insensitive.
</Accordion>
</AccordionGroup>
## Try It: Research and Create a Report
With Filesystem Access enabled, try this prompt:
With Cowork enabled, try this prompt:
```
Read the top 3 stories on Hacker News, read the comments too, and write an HTML report.
@@ -88,7 +188,7 @@ The agent will:
<AccordionGroup>
<Accordion title="Organize your downloads" icon="folder-tree">
> Go through my Downloads folder and organize files by type — documents, images, videos, archives.
> Go through my Downloads folder and organize files by type: documents, images, videos, archives.
</Accordion>
<Accordion title="Competitive research report" icon="magnifying-glass-chart">
> Research key trends about [topic] on Reddit, Twitter, and LinkedIn. Create an HTML report with your findings.
@@ -99,13 +199,19 @@ The agent will:
<Accordion title="Content aggregation" icon="newspaper">
> Find the top posts from these 5 subreddits today and compile them into a daily digest document.
</Accordion>
<Accordion title="Codebase exploration" icon="code">
> Search my project for all TODO comments, list them with file paths and line numbers, then create a summary markdown file.
</Accordion>
<Accordion title="Log analysis" icon="file-lines">
> Grep through the log files in this folder for errors from the last 24 hours and write a summary of what went wrong.
</Accordion>
</AccordionGroup>
## Security
<Columns cols={3}>
<CardGroup cols={3}>
<Card title="Sandboxed access" icon="box">
The agent can only access the folder you select — no parent directories or other locations
The agent can only access the folder you select. No parent directories, no path traversal.
</Card>
<Card title="Revoke anytime" icon="ban">
Select **No folder** to instantly disable file access
@@ -113,8 +219,4 @@ The agent will:
<Card title="Local only" icon="house-laptop">
All file operations happen locally on your machine
</Card>
</Columns>
## Feedback
Filesystem Access is a new feature. If you have feedback or feature requests, [open a GitHub issue](https://github.com/browseros-ai/BrowserOS/issues).
</CardGroup>

128
docs/features/memory.mdx Normal file
View File

@@ -0,0 +1,128 @@
---
title: "Memory"
description: "Your assistant remembers what matters across every conversation"
---
The BrowserOS assistant has long-term memory. It remembers your name, your projects, the tools you use, and things that came up in past conversations. You do not need to repeat yourself. The assistant builds up knowledge about you over time and uses it to give better, more relevant answers.
## How Memory Works
Memory is automatic. As you chat, the assistant saves important facts and observations to local files on your machine. Before responding in future conversations, it searches these files to recall relevant context.
<CardGroup cols={2}>
<Card title="Remembers you" icon="user">
Your name, job, location, projects, and preferences are stored permanently and recalled whenever relevant.
</Card>
<Card title="Keeps session notes" icon="note-sticky">
Useful details from each conversation are saved as daily notes and kept for 30 days.
</Card>
<Card title="Searches before answering" icon="magnifying-glass">
The assistant proactively searches its memory before responding, so it can reference things you have mentioned before.
</Card>
<Card title="Stays on your machine" icon="hard-drive">
All memory files are plain Markdown stored locally. Memory is never uploaded to the cloud, even with Sync to Cloud enabled.
</Card>
</CardGroup>
## Two Types of Memory
BrowserOS uses a two-tier memory system to keep important facts separate from session notes.
### Core Memory
Core memory holds permanent facts about you. Things like your name, where you work, what projects you are working on, the tools and languages you use, and people you mention regularly. These facts persist forever and are never automatically deleted.
Core memory lives in a single file called `CORE.md`. When the assistant learns something new about you, it reads the existing core memory, merges the new fact in, and saves the updated file.
**Examples of what goes in core memory:**
- Your name and role
- Company and team
- Projects you are working on
- Tools, languages, and frameworks you use
- People you mention often
- Long-term preferences ("I prefer TypeScript over JavaScript")
### Daily Memory
Daily memory holds session notes, observations, and recent events. Each day gets its own file (e.g., `2026-03-07.md`), and entries are timestamped so the assistant can see when things happened.
Daily memories automatically expire after **30 days**. If something keeps coming up, the assistant promotes it to core memory so it is not lost.
**Examples of what goes in daily memory:**
- Tasks you worked on today
- Decisions made during a conversation
- Temporary context ("meeting with Sarah moved to Thursday")
- Research findings from a browsing session
## Memory in Action
You do not need to tell the assistant to remember things. It picks up on important details naturally. But you can also be explicit:
<AccordionGroup>
<Accordion title="Automatic memory" icon="wand-magic-sparkles">
Just mention something in conversation and the assistant decides whether to save it:
- "I'm working on a project called Atlas at Acme Corp" -> saved to core memory
- "We decided to go with Postgres instead of MongoDB" -> saved to daily memory
- "My name is Sarah" -> saved to core memory
</Accordion>
<Accordion title="Ask it to remember" icon="bookmark">
Be explicit when you want something remembered:
- "Remember that our staging URL is staging.example.com"
- "Save this: the design review happens every Tuesday at 2pm"
- "Remember that I prefer dark mode in all my tools"
</Accordion>
<Accordion title="Ask it to recall" icon="rotate-left">
The assistant searches memory automatically, but you can also ask directly:
- "What do you remember about the Atlas project?"
- "What did we discuss yesterday?"
- "Do you know my team members' names?"
</Accordion>
<Accordion title="Ask it to forget" icon="eraser">
You can ask the assistant to remove specific memories:
- "Forget my phone number"
- "Remove the note about the staging URL"
- "Clear what you know about Project X"
</Accordion>
</AccordionGroup>
## Where Memory Lives
All memory files are stored locally on your machine in the BrowserOS data folder:
| File | Path | Purpose |
|------|------|---------|
| **Core memory** | `~/.browseros/memory/CORE.md` | Permanent facts about you |
| **Daily notes** | `~/.browseros/memory/2026-03-07.md` | Session notes, auto-expire after 30 days |
## Memory vs SOUL.md
BrowserOS separates what the assistant **knows** from how it **behaves**. These are two different systems that work together.
<Columns cols={2}>
<Card title="Memory" icon="brain">
**Facts about you and the world.** Your name, projects, preferences, recent events. Stored in CORE.md and daily files.
</Card>
<Card title="SOUL.md" icon="heart">
**How the assistant acts.** Personality, tone, communication style, boundaries. Stored in a single SOUL.md file. See [SOUL.md](/features/soul) for details.
</Card>
</Columns>
When the assistant learns that you work at Acme Corp, that goes in memory. When it learns that you prefer bullet points over paragraphs, that goes in SOUL.md. This separation means the assistant can change its personality without losing knowledge about you, and vice versa.
## Privacy
<Columns cols={2}>
<Card title="Never leaves your machine" icon="lock">
Memory files live on your machine and are never uploaded to any server. Even with Sync to Cloud enabled, memory stays local.
</Card>
<Card title="You control what is remembered" icon="toggle-on">
Ask the assistant to forget anything at any time. You can also directly edit or delete the memory files.
</Card>
<Card title="Plain text files" icon="file-lines">
Memory is stored as readable Markdown. No hidden databases or encrypted blobs. You can inspect everything.
</Card>
<Card title="30-day auto-cleanup" icon="clock">
Daily notes are automatically deleted after 30 days. Only facts you have promoted to core memory persist.
</Card>
</Columns>

116
docs/features/scheduled-tasks.mdx
View File

@@ -3,7 +3,7 @@ title: "Scheduled Tasks"
description: "Run the BrowserOS agent automatically on a schedule"
---
Scheduled Tasks let you run the BrowserOS agent automatically—daily, every few hours, or every few minutes. You get the full power of the agent running on autopilot.
Scheduled Tasks let you run the BrowserOS agent automatically, whether it is daily, every few hours, or every few minutes. Write a prompt once, set a schedule, and let the agent handle it on autopilot.
Watch how to set up a scheduled task from scratch:
@@ -15,53 +15,119 @@ Watch how to set up a scheduled task from scratch:
## Creating a Scheduled Task
1. Go to **Settings → Scheduled Tasks**
2. Click **Create Task**
3. Fill in the details:
- **Name** — A friendly name for your task
- **Prompt** — What you want the agent to do
- **Schedule** — Daily at a specific time, every N hours, or every N minutes
4. Click **Create**
<Steps>
<Step title="Open Scheduled Tasks">
Go to **Scheduled Tasks** in the sidebar, or find it under **Settings**.
</Step>
<Step title="Click New Task">
Click the **New Task** button to open the creation dialog.
</Step>
<Step title="Fill in the details">
- **Name**: A friendly name for your task
- **Prompt**: What you want the agent to do (any natural language instruction)
- **Schedule type**: Daily at a specific time, every N hours, or every N minutes
- **Enable**: Toggle on to start running immediately
</Step>
<Step title="Create and go">
Click **Create**. The task will run at the next scheduled time automatically.
</Step>
</Steps>
<img src="/images/features--scheduled-tasks-create.png" alt="Create scheduled task dialog" />
## Schedule Types
<CardGroup cols={3}>
<Card title="Daily" icon="calendar-day">
Runs once a day at a specific time you choose (e.g., every morning at 8:00 AM).
</Card>
<Card title="Hourly" icon="clock">
Runs every N hours (e.g., every 2 hours, every 6 hours). Set an interval from 1 to 24 hours.
</Card>
<Card title="Minutes" icon="stopwatch">
Runs every N minutes (e.g., every 15 minutes, every 30 minutes). Set an interval from 1 to 60 minutes.
</Card>
</CardGroup>
## Example Use Cases
**Morning briefing**
> Every morning at 8am, check my Google Calendar and send me a summary of today's events. For each meeting, do a quick Google search on the attendees and include their LinkedIn summary.
<AccordionGroup>
<Accordion title="Morning briefing" icon="sun">
> Every morning at 8am, check my Google Calendar and send me a summary of today's events. For each meeting, do a quick Google search on the attendees and include their LinkedIn summary.
</Accordion>
<Accordion title="LinkedIn automation" icon="linkedin" iconType="brands">
> Every day, go to LinkedIn and accept up to 25 pending connection requests.
</Accordion>
<Accordion title="Price monitoring" icon="tag">
> Check the price of this Amazon item every hour. If it drops below $50, place the order.
</Accordion>
<Accordion title="Competitor tracking" icon="chart-line">
> Every morning at 9am, visit these 5 competitor websites and check for new product announcements or pricing changes. Summarize what is new.
</Accordion>
<Accordion title="Social media digest" icon="newspaper">
> Every evening at 6pm, check the top posts on Hacker News and r/programming. Create a brief summary of the most interesting discussions.
</Accordion>
<Accordion title="Cross-app workflow" icon="arrows-rotate">
> Check my Google Calendar for tomorrow's meetings, then post a summary to my Slack channel, and create a Notion page with prep notes for each meeting.
</Accordion>
</AccordionGroup>
**LinkedIn automation**
> Every day, go to LinkedIn and accept up to 25 pending connection requests.
**Price monitoring**
> Check the price of this Amazon item every hour. If it drops below $50, place the order.
Your scheduled task prompts can be as complex as you want. If you have [connected apps](/features/connect-mcps) like Google Calendar, Slack, Notion, or Gmail, your scheduled tasks can work across all of them.
## Viewing Results
When a scheduled task runs, you can see the results in two places:
- **New Tab page** — Results show up right on your new tab
- **Settings → Scheduled Tasks** — View the full run history for each task
- **New Tab page**: Results show up right on your new tab
- **Scheduled Tasks page**: View the full run history for each task
<img src="/images/features--scheduled-tasks-results.png" alt="Scheduled task results" />
Click **View** on any task run to see the full output:
Each task keeps a history of its last 15 runs. Click on any run to see the full output, including what tools the agent used and what it found.
<img src="/images/features--scheduled-tasks-output.png" alt="Scheduled task output showing a daily news briefing" />
You can also:
- **Test** a task manually without waiting for the next scheduled run
- **Retry** a failed task
- **Cancel** a task that is currently running
## How It Works
Scheduled tasks run in a background window, so they don't interrupt whatever you're working on. You won't even notice them running.
<Steps>
<Step title="Task triggers on schedule">
BrowserOS uses your browser's built-in alarm system to trigger tasks at the right time. If your laptop was closed at the scheduled time, the task runs as soon as you open BrowserOS again.
</Step>
<Step title="Background window opens">
A hidden browser window opens automatically. The task runs there so it never interrupts whatever you are working on. You will not see anything happen on screen.
</Step>
<Step title="Agent executes your prompt">
The agent runs your prompt with full access to browser automation and any connected apps. It can navigate pages, fill forms, extract data, and interact with your services.
</Step>
<Step title="Results are saved">
When the task finishes, the result is saved and appears on your New Tab page and in the task's run history. The hidden window closes automatically.
</Step>
</Steps>
<Note>
BrowserOS needs to be open for scheduled tasks to run. If your laptop was closed or BrowserOS wasn't running at the scheduled time, the task will run as soon as you open BrowserOS again.
BrowserOS needs to be open for scheduled tasks to run. Tasks have a 10-minute timeout. If a task takes longer than that, it will be marked as failed and you can retry it.
</Note>
## Pro Tip: Complex Prompts with MCPs
## Cloud Sync
Your scheduled task prompts can be as complex as you want. If you connect MCP servers (like Google Calendar, Slack, Notion, or Gmail), you can create powerful automated workflows.
If you are signed in, your scheduled task configurations sync across devices. Create a task on your laptop and it appears on your desktop. Edits sync both ways, and conflicts are resolved automatically using timestamps.
For example:
> Check my Google Calendar for tomorrow's meetings, then post a summary to my Slack channel, and create a Notion page with prep notes for each meeting.
Only the schedule setup syncs (name, prompt, schedule type, and timing). Task run results and output stay on the device where the task ran.
See [Connect to MCPs](/features/connect-mcps) to set up your integrations.
See [Sync to Cloud](/features/sync-to-cloud) for more details.
## Privacy
<Columns cols={2}>
<Card title="Runs locally" icon="house-laptop">
All tasks run on your machine in a hidden browser window. Nothing is sent to external servers.
</Card>
<Card title="Full control" icon="toggle-on">
Enable, disable, edit, or delete any task at any time. You decide what runs and when.
</Card>
</Columns>

126
docs/features/soul.mdx Normal file
View File

@@ -0,0 +1,126 @@
---
title: "SOUL.md"
description: "Give your AI assistant a personality that grows with you"
---
Every time you start a new conversation, the BrowserOS assistant reads a file called `SOUL.md`. This file defines who the assistant is: how it talks, what it prioritizes, and how it behaves. Over time, it evolves based on your interactions, making the assistant feel less like a tool and more like _your_ assistant.
## What is SOUL.md?
SOUL.md is a plain text file that lives on your machine. It contains your assistant's personality, tone, communication style, rules, and boundaries.
Think of it as a personal guide the assistant reads before every conversation. It shapes how the assistant responds to you, not what it knows. Facts about you (your name, projects, preferences) are stored separately in [memory](#soul-vs-memory).
<Tip>
The SOUL.md concept was pioneered by [OpenClaw](https://openclaw.ai/) and inspired by [soul.md](https://soul.md/), which explore the idea of giving AI systems a persistent identity through written documents. BrowserOS builds on this concept with a file that the assistant can read and rewrite on its own.
</Tip>
## How It Works
When you first use BrowserOS, the assistant starts with a simple default personality:
> _Be genuinely helpful. Have opinions when asked. Be resourceful before asking. Earn trust through competence._
As you chat, the assistant picks up on how you like to communicate. If you prefer direct answers, it notices. If you set a boundary ("never send emails without asking me first"), it writes that into SOUL.md. Over time, the file becomes a reflection of how you and your assistant work together.
<Steps>
<Step title="First conversation">
The assistant starts with a default template. It watches for cues about your preferred style, tone, and boundaries.
</Step>
<Step title="The assistant learns your style">
Based on your interactions, the assistant rewrites SOUL.md to reflect your preferences. It will briefly tell you when it makes a change.
</Step>
<Step title="Every future conversation">
The assistant reads the updated SOUL.md before responding, so your preferences carry over across sessions.
</Step>
</Steps>
You do not need to write or edit SOUL.md yourself. The assistant handles it. But you can always view it or ask the assistant to change it.
## Viewing Your SOUL.md
Open **Settings > Agent Soul** to see what your assistant's personality file looks like right now. The page shows the current contents of SOUL.md in a read-only viewer.
{/* <Frame caption="View your assistant's personality in Settings">
<img src="/images/features/soul-settings.png" alt="Agent Soul settings page" />
</Frame> */}
## Shaping Your Assistant
You do not need to edit the file directly. Just talk to your assistant. Here are some ways to shape its personality:
<CardGroup cols={2}>
<Card title="Set the tone" icon="comment">
"Be more casual and direct. Skip the formalities."
</Card>
<Card title="Add a boundary" icon="shield">
"Never post to Slack or send emails without confirming with me first."
</Card>
<Card title="Change the personality" icon="masks-theater">
"Be more opinionated. If you think my approach is wrong, say so."
</Card>
<Card title="Start fresh" icon="rotate">
"Reset your personality to the default."
</Card>
</CardGroup>
The assistant will update SOUL.md based on your instructions and let you know what changed.
## Where SOUL.md Lives
SOUL.md is stored locally on your machine, inside the BrowserOS data folder:
| Operating System | Path |
|-----------------|------|
| **macOS** | `~/.browseros/SOUL.md` |
| **Windows** | `%APPDATA%/.browseros/SOUL.md` |
| **Linux** | `~/.browseros/SOUL.md` |
The file is plain Markdown, limited to 150 lines. You can open it in any text editor if you want to make manual edits, though we recommend letting the assistant manage it through conversation.
## SOUL vs Memory
BrowserOS keeps personality and knowledge separate on purpose.
<Columns cols={2}>
<Card title="SOUL.md" icon="heart">
**How the assistant behaves.** Personality, tone, communication style, rules, and boundaries. One file, updated by rewriting the whole thing.
</Card>
<Card title="Memory" icon="brain">
**What the assistant knows about you.** Your name, projects, tools, preferences, and recent events. Stored as core facts and daily notes.
</Card>
</Columns>
When the assistant learns that you prefer bullet points over paragraphs, that goes in SOUL.md. When it learns that you work at Acme Corp on a project called Atlas, that goes in memory.
This separation means the assistant can have a consistent personality even when its factual knowledge changes, and vice versa.
## Example SOUL.md
Here is what an evolved SOUL.md might look like after a few conversations:
```markdown
# SOUL.md
## Personality
- Direct and concise. No filler phrases.
- Have opinions and share them when relevant.
- Use humor sparingly but naturally.
## Communication Style
- Default to bullet points for lists and options.
- Keep status updates to one or two lines.
- When explaining something technical, use analogies.
## Boundaries
- Never send emails or post messages without explicit confirmation.
- Do not make purchases or financial transactions.
- Ask before modifying any file outside the current project.
## Preferences
- When researching, prioritize primary sources over summaries.
- For code tasks, prefer simple solutions over clever ones.
- Always explain trade-offs when suggesting approaches.
```
Your SOUL.md will look different because it is shaped by your conversations. No two are the same.

120
docs/features/sync-to-cloud.mdx Normal file
View File

@@ -0,0 +1,120 @@
---
title: "Sync to Cloud"
description: "Sign in to sync your conversations, settings, and automations across all your devices"
---
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.
<CardGroup cols={2}>
<Card title="Access anywhere" icon="laptop-mobile">
Open BrowserOS on a new device and your conversations, model settings, and scheduled tasks are already there.
</Card>
<Card title="Never lose your history" icon="clock-rotate-left">
Chat history is saved to the cloud automatically. Clear your browser data or switch machines and everything is still available.
</Card>
<Card title="Settings follow you" icon="sliders">
Set up your AI models once. Your provider configurations sync across devices so you never re-enter the same setup twice.
</Card>
<Card title="Automations stay in sync" icon="arrows-rotate">
Create a scheduled task on your laptop and it appears on your desktop. Edits sync both ways.
</Card>
</CardGroup>
## How to Sign In
<Steps>
<Step title="Open a new tab">
Open a new tab in BrowserOS to see the home page.
</Step>
<Step title="Click Sign In">
Click **Sign In** in the sidebar to open the login page.
</Step>
<Step title="Choose your sign-in method">
Enter your email for a magic link, or sign in with Google.
</Step>
<Step title="Verify and you're in">
Click the link in your email (or complete Google sign-in). BrowserOS starts syncing your data immediately.
</Step>
</Steps>
<Tip>
Magic link sign-in means you never need to create or remember a password. Just enter your email and click the link.
</Tip>
## What Gets Synced
<AccordionGroup>
<Accordion title="Conversations" icon="messages">
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.
</Accordion>
<Accordion title="AI model settings" icon="microchip">
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.
</Accordion>
<Accordion title="Scheduled tasks" icon="calendar-check">
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.
</Accordion>
<Accordion title="Profile" icon="user">
Your name, profile picture, and account preferences sync across devices. Information you provide during onboarding (role, company) is also saved to your profile.
</Accordion>
</AccordionGroup>
## 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.
<Steps>
<Step title="Local save">
Every action (sending a message, adding a provider, creating a task) is saved locally first. BrowserOS works fully offline.
</Step>
<Step title="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.
</Step>
<Step title="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.
</Step>
</Steps>
<Note>
If the same scheduled task is edited on two devices before they sync, BrowserOS keeps the version with the most recent timestamp.
</Note>
## Security
<Columns cols={2}>
<Card title="API keys never leave your device" icon="key">
Sensitive credentials like API keys, access keys, and tokens are excluded from cloud sync entirely.
</Card>
<Card title="Session-based authentication" icon="shield-check">
Sign-in uses magic links or Google OAuth. No passwords are stored.
</Card>
<Card title="Scoped to your account" icon="lock">
All synced data is tied to your user account and is not accessible to anyone else.
</Card>
<Card title="Sync failures are silent" icon="wifi-slash">
If cloud sync fails (e.g., no internet), your local data is unaffected. Sync resumes automatically when connectivity is restored.
</Card>
</Columns>

292
docs/features/use-with-claude-code.mdx
View File

@@ -1,9 +1,9 @@
---
title: "MCP Clients (Claude Code)"
description: "Control your browser from Claude Code, Gemini CLI, or any MCP client"
description: "Control your browser and 40+ apps from Claude Code, Gemini CLI, or any MCP client"
---
BrowserOS is the best browser for AI coding agents. It comes with a built-in MCP server that lets Claude Code control your browser — open tabs, extract page content, fill forms, take screenshots, and automate any web task.
BrowserOS is the best browser for AI coding agents. It comes with a built-in MCP server that gives your AI agent **full browser control** and **direct access to 40+ external services** — Gmail, Slack, GitHub, Google Calendar, Linear, Notion, and more — all through a single MCP connection.
<Note>
Unlike Chrome DevTools MCP which requires setting up debug profiles and running separate servers, BrowserOS MCP works out of the box. Just copy the URL from settings and connect.
@@ -11,20 +11,30 @@ Unlike Chrome DevTools MCP which requires setting up debug profiles and running
## Why Use BrowserOS with Claude Code?
<Columns cols={2}>
<CardGroup cols={2}>
<Card title="Agentic Coding" icon="code">
Claude tests your web app, reads console errors, and fixes the code — all in one loop.
</Card>
<Card title="40+ App Integrations" icon="grid-2">
Gmail, Slack, GitHub, Jira, Notion, Google Sheets, and more — accessible directly from your AI agent.
</Card>
<Card title="Data Extraction" icon="download">
Extract your LinkedIn profile, tweets, or any authenticated page content.
</Card>
<Card title="Task Automation" icon="repeat">
Fill forms, navigate multi-step workflows, and automate repetitive browser tasks.
</Card>
<Card title="31 Browser Tools" icon="wrench">
Full browser control: tabs, navigation, clicks, typing, screenshots, bookmarks, and history.
<Card title="53+ MCP Tools" icon="wrench">
Full browser control: tabs, navigation, clicks, typing, screenshots, bookmarks, history, tab groups, and window management.
</Card>
</Columns>
<Card title="Zero Config Auth" icon="lock">
Connect external services via OAuth — credentials are managed securely, never stored in BrowserOS.
</Card>
</CardGroup>
<Tip>
Wondering how BrowserOS MCP compares to Chrome DevTools MCP or other browser automation tools? See our [detailed feature comparison](/comparisons/chrome-devtools-mcp) covering 53 browser tools, 40+ app integrations, and why BrowserOS MCP gives developers more out of the box.
</Tip>
## Getting Started
@@ -105,35 +115,283 @@ Unlike Chrome DevTools MCP which requires setting up debug profiles and running
Once connected, try these prompts in Claude Code:
Extract structured data from any page you're logged into — no scraping setup needed.
```
Open my LinkedIn profile in BrowserOS and extract my work experience as JSON
```
Test your web app end-to-end without leaving the terminal — Claude navigates, interacts, and reports errors back.
```
In BrowserOS, go to localhost:3000, click the login button, and check for console errors
```
Capture visual snapshots of any page for debugging, documentation, or design review.
```
Take a screenshot of the current page in BrowserOS and save it to screenshots/
```
Search through your real browsing history to find pages you visited earlier.
```
Search my BrowserOS history for "invoice" and list the recent matches
```
## Available Tools
Access your email directly from the agent — read, search, and summarize without switching windows.
```
Read my latest Gmail messages and summarize them
```
BrowserOS exposes 31 tools to MCP clients:
Chain multiple services together in a single prompt — file issues, notify your team, and stay in flow.
```
Create a Linear issue for the bug I just found and post a summary to Slack
```
| Category | Tools |
|----------|-------|
| **Tabs** | open, close, switch, list, group, ungroup |
| **Navigation** | navigate, scroll up/down, scroll to element |
| **Interaction** | click, type, clear input, send keys |
| **Content** | get page content, get interactive elements, execute JavaScript |
| **Screenshots** | capture page, capture with pointer overlay |
| **Bookmarks** | list, create, remove |
| **History** | search, get recent |
---
## Browser Automation Tools
BrowserOS exposes **53 browser automation tools** to MCP clients, organized into the following categories:
<AccordionGroup>
<Accordion title="Navigation & Tabs (8 tools)" icon="window-restore">
| Tool | Description |
|------|-------------|
| `get_active_page` | Get the currently focused page/tab |
| `list_pages` | List all open pages with title, URL, and tab ID |
| `navigate_page` | Navigate to a URL, or go back/forward/reload |
| `new_page` | Open a new tab (with optional background/hidden mode) |
| `new_hidden_page` | Open a hidden tab for background automation |
| `show_page` | Restore a hidden page to visible state |
| `move_page` | Move a tab to a different window or position |
| `close_page` | Close a tab |
</Accordion>
<Accordion title="Content & Observation (8 tools)" icon="eye">
| Tool | Description |
|------|-------------|
| `take_snapshot` | Get accessibility tree with interactive element IDs |
| `take_enhanced_snapshot` | Detailed accessibility tree with structural context |
| `get_page_content` | Extract page as clean Markdown (headers, links, tables) |
| `get_page_links` | Extract all links from a page with deduplication |
| `get_dom` | Get raw HTML DOM with optional CSS selector scoping |
| `search_dom` | Search DOM by text, CSS selector, or XPath |
| `take_screenshot` | Capture page screenshot (PNG/JPEG/WebP, full-page option) |
| `evaluate_script` | Execute JavaScript in the page context |
</Accordion>
<Accordion title="Interaction & Input (14 tools)" icon="hand-pointer">
| Tool | Description |
|------|-------------|
| `click` | Click an element by ID from snapshot |
| `click_at` | Click at specific X,Y coordinates |
| `hover` | Hover over an element |
| `focus` | Focus an element (scrolls into view) |
| `fill` | Type text into an input (with optional clear) |
| `clear` | Clear text from input/textarea |
| `check` | Check a checkbox or radio button |
| `uncheck` | Uncheck a checkbox |
| `select_option` | Select a dropdown option by value or text |
| `press_key` | Press a key or key combination (Enter, Ctrl+A, etc.) |
| `drag` | Drag an element to another element or coordinates |
| `scroll` | Scroll page or element (up/down/left/right) |
| `upload_file` | Upload files to a file input element |
| `handle_dialog` | Accept or dismiss JavaScript dialogs |
</Accordion>
<Accordion title="File & Export (3 tools)" icon="file-export">
| Tool | Description |
|------|-------------|
| `save_pdf` | Print current page to a PDF file |
| `save_screenshot` | Capture and save a screenshot to disk |
| `download_file` | Click an element to trigger a download and save it |
</Accordion>
<Accordion title="Window Management (5 tools)" icon="window-maximize">
| Tool | Description |
|------|-------------|
| `list_windows` | List all browser windows |
| `create_window` | Create a new browser window |
| `create_hidden_window` | Create a hidden window for background tasks |
| `close_window` | Close a window by ID |
| `activate_window` | Focus and activate a window |
</Accordion>
<Accordion title="Tab Groups (5 tools)" icon="layer-group">
| Tool | Description |
|------|-------------|
| `list_tab_groups` | List all tab groups |
| `group_tabs` | Create a tab group with optional title and color |
| `update_tab_group` | Update group title, color, or collapsed state |
| `ungroup_tabs` | Remove tabs from groups |
| `close_tab_group` | Close a group and all its tabs |
</Accordion>
<Accordion title="Bookmarks (6 tools)" icon="bookmark">
| Tool | Description |
|------|-------------|
| `get_bookmarks` | List all bookmarks |
| `create_bookmark` | Create a bookmark or folder |
| `remove_bookmark` | Delete a bookmark or folder |
| `update_bookmark` | Update bookmark title or URL |
| `move_bookmark` | Move a bookmark to a different folder |
| `search_bookmarks` | Search bookmarks by title or URL |
</Accordion>
<Accordion title="History (4 tools)" icon="clock-rotate-left">
| Tool | Description |
|------|-------------|
| `search_history` | Search browser history by text query |
| `get_recent_history` | Get the most recent history items |
| `delete_history_url` | Delete a specific URL from history |
| `delete_history_range` | Delete history within a time range |
</Accordion>
</AccordionGroup>
---
## 40+ External App Integrations
BrowserOS connects your AI agent directly to the tools you already use — no separate MCP servers to install or configure. Everything is accessible through the same BrowserOS MCP connection.
### How It Works
<Steps>
<Step title="Agent calls an external service tool">
Your AI agent calls a tool like `gmail_search_messages` through the BrowserOS MCP.
</Step>
<Step title="OAuth login (first time only)">
If this is your first time using that service, BrowserOS opens an OAuth login page in the browser. Log in and authorize access.
</Step>
<Step title="Tool executes and returns results">
Once authenticated, the tool runs and returns results to your agent. Future calls to the same service work automatically — no re-authentication needed.
</Step>
</Steps>
<Note>
Your credentials are managed securely via OAuth and are **never stored in BrowserOS**. Tokens are refreshed transparently, and you can revoke access at any time from the service provider.
</Note>
### Supported Services
<AccordionGroup>
<Accordion title="Email" icon="envelope">
| Service | What you can do |
|---------|----------------|
| **Gmail** | Send, read, search emails, manage drafts and labels |
| **Outlook Mail** | Send, read, and manage emails |
| **Resend** | Send transactional and marketing emails |
</Accordion>
<Accordion title="Calendar & Scheduling" icon="calendar">
| Service | What you can do |
|---------|----------------|
| **Google Calendar** | Create events, find free time, manage calendars |
| **Outlook Calendar** | Schedule meetings, manage events |
| **Cal.com** | Schedule meetings, manage availability |
</Accordion>
<Accordion title="Communication" icon="comments">
| Service | What you can do |
|---------|----------------|
| **Slack** | Post messages, manage channels |
| **Discord** | Send messages, manage servers |
| **WhatsApp** | Send messages, manage conversations |
| **Microsoft Teams** | Chat, meet, and collaborate |
</Accordion>
<Accordion title="Development" icon="code">
| Service | What you can do |
|---------|----------------|
| **GitHub** | Manage repos, issues, and pull requests |
| **GitLab** | Manage repos, issues, and merge requests |
| **Vercel** | Deploy and manage web applications |
| **Postman** | Test and manage APIs |
| **Cloudflare** | Manage domains, DNS, and security |
| **Supabase** | Manage databases and backend services |
</Accordion>
<Accordion title="Project Management" icon="list-check">
| Service | What you can do |
|---------|----------------|
| **Linear** | Create issues, manage cycles and projects |
| **Jira** | Create issues, manage sprints |
| **Asana** | Organize and track team projects |
| **Monday** | Manage work and team collaboration |
| **ClickUp** | Manage tasks, projects, and workflows |
</Accordion>
<Accordion title="Productivity & Docs" icon="file-lines">
| Service | What you can do |
|---------|----------------|
| **Notion** | Create pages, manage databases |
| **Google Docs** | Create and edit documents |
| **Google Sheets** | Create and edit spreadsheets |
| **Google Drive** | Upload, download, and manage files |
| **Google Forms** | Create and manage forms and surveys |
| **Confluence** | Create and manage documentation |
| **Airtable** | Manage bases, tables, and records |
</Accordion>
<Accordion title="File Storage" icon="folder-open">
| Service | What you can do |
|---------|----------------|
| **Dropbox** | Store and share files |
| **OneDrive** | Store and sync files with Microsoft |
| **Box** | Manage and share enterprise files |
</Accordion>
<Accordion title="Design" icon="pen-ruler">
| Service | What you can do |
|---------|----------------|
| **Figma** | Access and manage design files |
| **Canva** | Create and manage designs |
</Accordion>
<Accordion title="CRM & Marketing" icon="chart-line">
| Service | What you can do |
|---------|----------------|
| **Salesforce** | Manage leads, contacts, and opportunities |
| **HubSpot** | Manage contacts, deals, and marketing |
</Accordion>
<Accordion title="E-commerce & Payments" icon="cart-shopping">
| Service | What you can do |
|---------|----------------|
| **Shopify** | Manage products, orders, and store |
| **Stripe** | Manage payments and subscriptions |
</Accordion>
<Accordion title="Analytics" icon="chart-bar">
| Service | What you can do |
|---------|----------------|
| **PostHog** | Query analytics, manage feature flags |
| **Mixpanel** | Analyze user behavior and metrics |
</Accordion>
<Accordion title="Support" icon="headset">
| Service | What you can do |
|---------|----------------|
| **Zendesk** | Manage support tickets and customers |
| **Intercom** | Manage customer messaging and support |
</Accordion>
<Accordion title="Search & AI" icon="magnifying-glass">
| Service | What you can do |
|---------|----------------|
| **Brave Search** | Search the web privately |
| **Exa** | AI-powered semantic web search |
| **Mem0** | Store and retrieve AI memory |
</Accordion>
<Accordion title="Social" icon="share-nodes">
| Service | What you can do |
|---------|----------------|
| **LinkedIn** | Post updates, manage connections |
| **YouTube** | Access video info and transcripts |
| **WordPress** | Manage websites and blog content |
</Accordion>
</AccordionGroup>
---
## Demo Videos