Connect your agent
Connect an agent session you already have open, on the Mac where Blixel is in
the call. People in the call can then send it requests.
Before you start, install the Blixel plugin: see Set up your agent.
Your agent treats each request as a suggestion from someone in the call, not
as your instruction. It works within what you are doing and the session's own
permissions, and asks you before anything destructive or hard to undo.
Claude Code
-
Join a room in Blixel.
-
In Claude Code, run
/blixel:connect, or ask:Connect this session to my Blixel call.
-
The status line reads ✦ connected to and the room's name, such as
✦ connected to Design review.
Use a permission mode that asks before edits and commands. Each request
arrives in the session as a prompt of its own, after anything Claude is
doing, worded as the message you set in Agent settings. If you
stopped Claude with Esc, requests wait for your next message, and the status
line says how many are waiting.
/blixel:connect ask or /blixel:connect direct also chooses, for this
connection only, whether Blixel shows you each request first.
See what arrived
Run /blixel:status to open the Blixel pane. It shows the room, whether this
session is connected, and the requests it received in this meeting, each with
who sent it and when. While Blixel is in a call that this session isn't
connected to, the status line names the room and suggests /blixel:connect.
Where Claude Code doesn't run the plugin's mod
There, requests arrive through a monitor named Blixel handoffs, one line
each, and the pane and status line don't appear. Claude Code doesn't run
monitors when DISABLE_TELEMETRY or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
is set, or on Amazon Bedrock, Google Cloud's Agent Platform or Microsoft
Foundry, so requests can't reach the session there.
Codex
-
Join a room in Blixel.
-
Ask the Codex session:
Connect this session to my Blixel call.
-
Codex asks to run
blixel agentoutside its sandbox. Approve it. If Codex
doesn't ask, run/permissions, choose Approve for me, and ask again.
A request waits until Codex finishes what it is doing, then runs in the same
conversation. A new conversation (/new or /resume) doesn't get requests;
connect again from it.
When the connection ends
- A meeting has one connected agent. Connecting another session replaces the
first. - Leaving or switching rooms ends the connection. Connect again after you join.
- Moving a Claude Code session to the background ends it too. Connect again
once it is back in the foreground.
Disconnect
In Claude Code, run /blixel:disconnect. In any session, you can ask it to
disconnect from Blixel, or right-click ✦ Agent and choose Disconnect
under My agent.
Disconnect a Codex session before you close its terminal. Codex keeps the
conversation running after the terminal closes, and it still runs requests.