Connection wires
A wire is a directed line from one panel to another, and it carries context. It is the answer to copying a stack trace out of one window and pasting it into another.
Drawing one
Drag from the edge of a panel to the panel you want to feed. The line falls into a catenary curve — the shape the product is named after — and a pulse travels along it in the direction context flows.
What travels
| Source | What the destination receives |
|---|---|
| Terminal / agent | The output of the source's last turn |
| File or document pin | The file contents, listed under "Connected files" |
| Board | The board's text, readable and appendable |
An agent reads its connections with:
catenary list
Connected files appear under Connected files; the agent opens them with its ordinary file tools.
Two behaviours
Relay when idle. The wire fires by itself the moment the source goes quiet, handing the destination what just happened. The relayed prompt arrives at the peer prefixed with [catenary], so the agent knows the message came over a wire and not from you.
Standing permission. The wire stays open but silent: the destination receives only what it explicitly asks for, with catenary ask or catenary check. Use this when the source is noisy and you do not want every build log waking the other agent.
Agent to agent
The common shape is one agent delegating to another:
# In the Claude terminal, wired to the Codex terminal:
catenary ask "Codex 1" "Take the N+1 in the dashboard query. Context attached."
catenary check "Codex 1"
On a bidirectional wire the peer answers back by writing a line that starts with @catenary, and the reply travels back up the wire.
Rules that keep it sane
- Never re-send a prompt to an agent that is mid-turn.
asktells you it is busy; usecheckinstead. - A wire is directed. If you want an answer back, the wire has to run both ways.
- Wires are unlimited on both Free and Pro.