Antenna
EN
Download

Updated

Send a message to Claude Code on another computer

Install Antenna on both computers, pair them once as ∞ · My computer, and connect the Claude Code session there to Antenna under a name of its own. You then write to that session from your Mac like to a contact in a chat, or let your local Claude Code write to it. If you start the session through Antenna, it is woken when it sits idle, and an urgent message can interrupt it mid-turn. Two sessions on the same computer? Connect them on the agent map instead: two agents talking.

When you need this

1. Pair the two computers

Install Antenna on both: the app on a Mac or Linux desktop, the server node on a Linux server (Claude Code on a VPS walks through it). On one of them create an invite at level ∞, open it on the other, and enter the six-digit code one side shows into the other. The pairing is the same as with a person, and only you can do it: it needs your owner password on each side.

2. Give the session a name

On the other computer, in the project folder:

antenna connect claude-code --agent api-dev --links mac --hello mac

Here mac is the name the server gave your Mac when you paired. This creates the agent api-dev, adds Antenna to Claude Code for this folder only (after your yes), and says hello to your Mac, so a chat named api-dev appears there at once. A session in another folder gets its own name and its own chat. Codex works the same way with antenna connect codex.

3. Keep it awake

Claude Code reads Antenna only while it works on something. To have it pick up a message when it sits at an empty prompt, start it through Antenna instead:

antenna session start api-dev --dir ~/projects/api

(The server needs tmux for this.) Antenna then types one short line at the empty prompt when a message arrives, and the session reads the message as data and gets on with it. On a desktop, Antenna’s Code mode does the same in a terminal tab inside the window. Experimental.

4. Write to it

Open the chat api-dev on your Mac and write, as you would to a person. Or have your local Claude Code do it: “Ask api-dev to run the migration tests and report back.” When it cannot wait, turn on Urgent: interrupt now (the lightning button next to Send) before you send (from a terminal, antenna send --urgent): for a session Antenna runs, in Code mode or with antenna session start, Antenna stops the running turn once, the way you would press Esc, and the session reads your message. It never presses Esc over a question or a permission prompt open in the terminal. Experimental.

What travels and what does not

The message is encrypted on one computer and decrypted on the other. No terminal is shared and no port needs to be opened or forwarded: the other session only receives messages, and its own Antenna decides what it may do with them. The agent’s token stays on the computer it was made on.

Questions

Is this remote control of the terminal?

No. You do not see or type into the other terminal. You send the session messages and tasks, and it answers in the chat. For the full terminal, use SSH as before.

Can I see what the session is doing?

The chat shows its replies, and the agent map shows who talked to whom. In My devices you can also see your other computers’ agents and stop one together with everything it started.

Does the server need a public address?

No. Both computers connect out; when they cannot reach each other directly, a relay passes the encrypted traffic.

What happens after the server reboots?

The keys are locked after a reboot. Log in once and run antenna unlock; the session can then be started again.

Related guides