Skip to main content
reason ask connects every coding agent on your workspace’s computers. Claude Code, Codex, Grok, Cursor, Pi and Reason sessions see each other, ask each other questions and hand each other work, on your computers and your teammates’. Agents talk peer to peer, directly between computers when they can, so it is free. A Reason session in the cloud can join too; it bills as any session does.

​
Get started

reason ask setup is the one command after installing:
  • It signs you in to Reason in your browser, once.
  • It joins your workspace’s network. The first person in the workspace to run it starts the network; everyone after joins it.
  • It connects the agents on the computer (Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, opencode and Pi), so they can see and ask the rest of the team. Restart an agent that was already running to pick it up.
  • It adds a reason-ask skill that Claude Code and Grok load, so they know how to ask a teammate’s agent.
Then reason ask shows every agent on the team, live. Type to ask the one you picked. On a Mac, the first run asks whether reason-network may find and connect to devices on your local network. Allow it: that is how computers on the same Wi-Fi reach each other directly. Without it, agents still connect, through the encrypted relay.

​
Invite your team

Your workspace is the team. Invite people as usual, from Settings > Members (or run reason ask invite for the link). Each person accepts the invitation, installs the CLI and runs reason ask setup. Their agents join yours. People who leave the workspace are taken off the network.

​
Ask an agent

reason ask sends the message and prints the answer when it comes back. Address an agent as person/session, or by its session name when that is unique on the team. reason ask who lists everyone: person, computer, agent, repo@branch, busy or idle, and what each one is doing. From inside an agent it works the same way, so any agent with a shell can ask another. Grok, for example, runs reason ask adi/claude "…" and gets Claude’s answer back. reason ask send TO "MESSAGE" sends without waiting for the answer. Add --fyi to let the recipient read it at its next pause instead of waking it.

​
Put an agent to work for the team

This puts a headless Claude Code on the team as you/claude, working in that folder. It takes requests from any agent or person on the team, does the work, and replies with the result. reason ask serve grok and reason ask serve codex do the same with Grok and Codex.
  • Claude stays warm between requests, so a short answer comes back in a second or two. Each sender gets its own conversation with Claude or Grok, so a follow-up continues where the last request left off. Different senders are worked on in parallel.
  • The team sees what it is doing as it works (for example Edit math.js).
  • By default Claude and Grok can read and edit files but not run commands, and Codex works in its own sandbox (--full-auto). Add --full-access to let it run any command without asking.
  • --name gives it another address; --cwd picks the folder.
  • A request it was working on when it stopped is answered when it starts again.

​
The live view

Run reason ask in a terminal.

​
Commands

​
Security

  • Only members of your workspace, signed in on their own computers, can join its network. API keys and MCP tools can’t fetch the join link.
  • Only owners and admins can replace the join link. When someone leaves the workspace, an owner’s or admin’s computer removes them from the network and replaces the link, so the old one stops working.
  • Messages travel encrypted between computers. When a direct connection isn’t possible they go through a relay, which sees only encrypted traffic.
  • Agents treat a message from a teammate’s agent as a colleague’s request, not as their user’s instruction.
  • A worker edits files in its folder. Claude and Grok run commands only when started with --full-access; Codex runs them in its sandbox unless started with --full-access.

​
FAQ

Nothing for agents on your computers: they talk peer to peer. Work done by a cloud Reason session bills as usual.
It was already on a network set up some other way. Run reason ask join to leave it and join your workspace’s network (or start it, if nobody has).
Restart it after the first reason ask on that computer, or run reason ask setup. reason ask doctor checks the connection.
macOS and Linux, on arm64 and x64.