Blog· 3 min read
Introducing Stoic Browser: one calm window for every product you run
Stoic Browser 0.1.0 is out for macOS, Windows and Linux. It gives each product its own workspace and logins, lets your coding agents work inside them, and replays your browser chores on a schedule.
If you run more than one product, your browser probably looks like this: a Chrome profile per product, each signed in to its own Stripe, Google and X accounts, and twenty tabs open before your first coffee. Stripe, analytics, Search Console, the support inbox, reviews. For every product, every day. And after all that looking, you can still miss the one number that moved.
Stoic Browser is built for that morning. Version 0.1.0, the first public build, is out today for macOS, Windows and Linux.
One workspace per product
Each workspace runs in its own isolated session, so every product keeps its own logins. You sign in to Stripe as product A in one workspace and as product B in another, and neither knows about the other. No more signing out to sign in as someone else, and no more posting from the wrong account.
A workspace holds its own tabs, pinned tabs and layout. Split layouts put the dashboard next to the page you are fixing: one pane, two columns, three stacked panes or a 2×2 grid, and the layout is still there tomorrow. You can bring your existing logins along, too: import bookmarks and history from Chrome, Brave, Firefox or Safari straight into the workspace they belong to, and on a Mac, cookies and saved passwords from Chrome or Brave.
The numbers you check, extracted for you
Crawl Mode turns "go look at the dashboard" into something the browser does. Click a table, a list of cards, a metric or a block of text on any signed-in page, check the fields, test it, and Stoic Browser extracts it again every 15 minutes, hour, 6 hours or day, or on a custom cron. It runs in a hidden window that uses the workspace's logins, so it sees what you would see.
There is a built-in crawler for your Ahrefs dashboard, and public sources for RSS feeds, subreddits and JSON endpoints.
Automations that run while you are away
The automation harness turns a routine into steps — go to a page, click, fill a form, extract a value, take a screenshot — and puts it on a schedule. You can build one in three ways:
- Record it. Press Record and use the site normally. Clicks, typing and navigation become editable steps.
- Build it by hand. Add steps from the catalog and fill in their fields.
- Ask the agent. Describe the routine in the chat, let the agent do it once, and save what it did as an automation.
Scheduled runs happen in a hidden window with the workspace's logins, and replaying recorded steps does not call a model, so a daily check costs nothing to run. Every number an automation extracts becomes a tracked value, with its change since the last run and a sparkline.
An agent chat with a real browser
The agent chat drives the coding CLIs you already have installed — Claude Code, Codex, OpenCode and others — and hands them browser tools over MCP: snapshot a page, click, type, take a screenshot, read the console. You pick the model and pay for it directly; there is no Stoic account in between.
It also works the other way round. MCP access lets an external client such as Claude Code, Cursor or VS Code use Stoic Browser as a browser tool server. Each connection gets its own credential, a capability preset (read only, browse, operate or full) and a list of workspaces it may use. The agent drives a hidden pane in a workspace that is already signed in and never sees a password, and every call is logged.
Local first
Workspaces, chats, automations and run history live in one SQLite file on your machine, and there is no Stoic account or cloud to sync them to. When you use an agent, requests go from your machine straight to the CLI or model provider you chose. Anonymous usage stats stay off until you say yes, and they never describe what you browse.
Get it
Stoic Browser is free for two workspaces, one monitored source and one saved automation, with no account and no license key. Every release ships for:
- macOS — Apple silicon and Intel
- Windows — an installer, or a portable build that needs no install
- Linux — AppImage and .deb
The Mac app, the Windows installer and the AppImage update themselves from GitHub Releases, so the build you install today keeps up with what ships next.