Sol Browser

About Sol Browser

Sol makes the browser the IDE. Its starting observation is that developers spend the day drowning in tabs — PR reviews, planning docs, API documentation, dashboards, localhost servers — and then switch back to an editor and leave all of that context behind. Coding agents made it worse: every worktree you add multiplies the context you have to hold in your head, and each one comes with its own new set of tabs. Sol's answer is to make the tab the core primitive of a development environment. Your agent runs in a tab. Your terminal is a tab. Your diff viewer is a tab. That means Claude Code, running in a terminal, in the browser, can sit in the same viewport as the PR it's implementing and the docs page it needs. Tabs split, reorder, and organize like they do in any browser, and Sol borrows groups and spaces from Arc and maps them onto worktree orchestration — creating a new worktree spawns a new group with a chat tab anchored to it, so parallel agents stay visually separated instead of blurring together. The defaults are opinionated but every primitive is programmable: you can script how tabs are arranged when you open a project or a worktree. The bet behind the architecture is that a browser is already secure, extensible, and capable of running rich applications, so building on it means the workspace can evolve as agents evolve rather than being redesigned every year.

Key Features

Sol Browser Pros & Cons

Who Is Sol Browser Best For?

Tags