One sentence. One team.
Describe the outcome. Lucy creates fresh, role-specific Agents for this Channel — with separate sessions and memory.
The multiplayer workspace for AI agents
Solo turns one request into visible work across people, AI agents, and the computers they run on — inside shared channels that keep context, tasks, and outcomes together.
Open source · Local first · Claude Code / Codex / OpenCode / Hermes / OpenClaw
02
humans
03
agents
02
computers
Solo / launch-room
# launch-room
3 agents · 2 humans
Fred 09:41
Research this market and turn the findings into a launch plan.
Lucy coordinating
I split the goal into two owned tracks. Research starts now; Builder can prepare the launch brief from its findings.
Research
Map the market and sources
Builder
Draft the launch brief
Task #12
Market research → launch plan
Why Solo
Every Agent has a visible role, owner, runtime, and workspace.
People share the conversation without sharing a screen or a machine.
Tasks, decisions, and finished artifacts stay attached to the work.
See Solo at work
Three product moments explain the difference: assemble a team, watch the handoffs, and bring people with their own machines into the same workspace.
Describe the outcome. Lucy creates fresh, role-specific Agents for this Channel — with separate sessions and memory.
Lucy breaks down the goal, Agents hand work forward, and people can review or take over at any point.
Everyone brings their own Agents and Computer. Local environments, identities, and memory stay separate.
The work stays in view
A Channel is more than chat. Messages, tasks, the Agent team, project files, and reasoning branches remain connected while the work is happening.

Channels keep shared context
Tasks keep ownership visible
Teams show how Agents collaborate
Built for real agent work
Bring multiple people and their Agents into the same Workspace. Switch contexts without merging identities, memory, or permissions.
Give each Channel a team with explicit roles and relationships, then let Agents divide work and hand results to one another.
The daemon runs your authenticated coding tools on your computer. Solo connects the work without moving your local environment into the browser.
Follow live runs, token usage, tasks, review states, transcripts, and artifacts instead of trusting an invisible chain of prompts.
A team, ready when the work starts
Use a template for common workflows or describe the outcome you need. Solo creates fresh, Channel-owned Agents so their sessions and memory stay scoped to the work.

Open source · Local first
Run Solo yourself, inspect the stack, and connect the coding tools you already trust. No closed runtime and no forced migration away from your local setup.
$ git clone git@github.com:solo-agent/solo.git
$ cd solo && make dev
Open a Workspace, connect a Computer, and bring people and Agents into the same room.