CLI commands

Each group of commands has its own help. This page summarizes them; for every
option, run blixel help <group> <command>, or blixel schema <group> <command> for a description in JSON.

Group	What it does	Needs
`auth`, `connection`	Signs the CLI in and out, and chooses a server.
`room`	Lists, creates and invites to rooms; shows who is in a room and which room the app is in.	A sign-in; the app for `room current`
`chat`	Sends to and reads the chat of the app's meeting.	The app, in a meeting
`window`	Lists, shares and stops sharing windows in the app's meeting.	The app, in a meeting
`transcript`	Lists, searches, reads, exports and follows the transcripts this Mac recorded.
`event`	Watches for things that happen in Blixel, such as a transcript ending.
`hook`	Manages hooks: commands the app runs when an event happens.	The app for `rerun` and `test`
`agent`	Connects a Claude Code or Codex session to the app's meeting.	The app, in a meeting
`schema`	Describes every command as JSON.

The CLI never launches the app, joins a room or starts transcription.

Rooms

blixel room list
blixel room presence <room-id>
blixel room create "Design review" --policy allowlist
blixel room invite <room-id>
blixel room current

room invite prints the room's invite link. Treat it like a password: anyone
with it can join. room current shows the app's meeting, including the
meeting_id that chat, window and agent commands ask for.

Chat and windows

blixel chat send "Notes are posted" --meeting-id <meeting-id>
blixel chat read --meeting-id <meeting-id>
blixel window list --meeting-id <meeting-id>
blixel window share <handle> --meeting-id <meeting-id>

A message is sent as you, the way the app's Send does. Windows are captured
by the app, with its Screen Recording permission. If the app has since left
that meeting or joined another, the command changes nothing.

Transcripts

blixel transcript list
blixel transcript search "release decision"
blixel transcript export <id> --format md
blixel transcript follow --current

These read the transcripts on this Mac, with or without the app running.

Events and hooks

blixel event types
blixel event watch --type transcript.ended
blixel hook add standup --type transcript.ended --command ~/bin/summarize.sh
blixel hook list

event types lists every event with what it carries. A hook runs your command
once for each matching event while the app is open; you can also manage hooks
in Settings › Hooks. See Run a command on an event
and Events.

Each request to an agent writes handoff.sent on the sender's Mac and
handoff.received on the agent owner's Mac. Both carry ids and how the request
was made (spoken, typed or mixed), never its text.

Agents

blixel agent connect
blixel agent status
blixel agent disconnect

Run these from inside a Claude Code or Codex session; the Blixel plugin runs
them for you. See Connect your agent.