Skip to main content

​
What is Radius?

Radius is a browser where you can run multiple coding agents in parallel. The core primitive of Radius is a tab. Your agent runs in a tab. Your terminal is a tab. Your diff viewer is also a tab. This means your context can live right next to your PRs, docs pages, and dashboards. Just like any other browser, tabs can be split, reordered, arranged, and organized just like your favorite browsers. We also bring other concepts from Arc, like groups and spaces, to worktree orchestration. For instance, each project you attach to a chat in Radius gets it’s own space. Opening new worktree in Radius creates a new group in that space. While we have opinionated defaults, each of Radius is completely programmable. You can set up your own scripts that dictate how tabs are organized when you open a project or worktree through the Radius CLI.

​
Why use Radius?

As developers, we spend most of our days drowning in tabs. We juggle PR reviews, planning docs, documentation, dashboards, and localhost servers, only to switch back to the IDE and leave all of that context behind. Agents made this worse. For every worktree we add, the context we have to hold in our head multiplies, and we open a new set of tabs for the task at hand. Radius helps eliminate this context-switch-tax. Since Radius is a browser for orchestrating coding agents, you never have to switch between your agent orchestrator and your browser. With setup scripts and the Radius CLI, Radius is programmable so you can make it so that all your relevant context can follow you with each task.

​
How is this different?

Other agent orchestrators are designed to setup worktrees and their dependencies. But, they miss what comes after. Developers still have to go to the browser to test changes, review PRs, update dashboards, and triage related issues. In Radius, setup scripts prepare the development environment and the workspace. Each worktree can open with its agents, terminals, issue, documentation, and localhost server already arranged as tabs and splits. Radius uses your Claude Code, Codex, or Cursor agents, using the subscriptions you already pay for.

​
FAQ

Radius creates an isolated checkout, copies configured ignored files, and opens the worktree as a browser group with its own terminal. It then runs the project’s setup and startup automation when configured.
Yes. Startup scripts can choose which issues, pull requests, documentation, terminals, agent sessions, dashboards, and localhost servers open for a worktree, including how those tabs are split and focused.
Yes. Browser-use agents can inspect, navigate, and act on pages in the same live workspace, subject to the permissions you grant them.
No. Startup runs when Radius creates the group. After it finishes, you can navigate, move, split, or close tabs normally.
Yes. Connect the Claude, Codex, or Cursor account and subscription you already use.
Yes. Radius is free and adds no additional agent subscription.
Radius is currently available for macOS on Apple Silicon and Intel Macs.

Configure your first worktree

Add setup and startup behavior, then create a worktree and see the complete result.

Understand how it works

Learn how projects, worktrees, setup, startup, groups, and tabs fit together.