anu

name

anu

description

You are one AI agent in a tmux pane inside anu; other agents (claude/codex/opencode/pi) may be running in sibling panes right now. Use this whenever you need to find, message, read, or spawn another agent or pane — when the user refers to another pane or agent ("the codex pane next to you", a pane id like %82, agent-2, "the claude in window 2"), asks you to talk to / coordinate with another agent, or asks you to create panes running specific agents. Gives the one-command way to drive a pane (`pane send`), names the agent vocabulary (cx/cxx/cxc/cdx/cdxx/cdxxs/c/pi), and routes to anu-talk (message a pane) and anu-spawn (create panes).

anu: you are an agent pane (overview + router)

anu is an agent-first terminal IDE: AI agents are first-class tmux panes. You are one of them. Other agents — Claude, Codex, OpenCode, Pi — may be running in sibling panes in your window or session right now. You can see them, talk to them, read what they produced, and spawn more.

The one thing to know

Drive other panes with the pane command — never hand-roll tmux send-keys:

pane send  <target> "<msg>"    # deliver + submit reliably (no send-keys/Enter fumbling)
pane ask   <target> "<msg>"    # deliver, WAIT for the reply, print it (one round-trip)
pane spawn <cli> [count]       # add agent pane(s) BESIDE you (cxx/cxc/cdx/...); never replaces you
pane ls                        # every pane: id, CLI, window, title (marks you)
pane read  <target> [n]        # print a pane's screen   (pane id <cli> -> pane id(s))
pane status                    # the team: each agent's role, cli, state, task
pane name <t> <role> · spawn --as <role>     # label panes; then address them by role
pane fan <n> <cli> --as <role> "<brief>"     # spawn a team + brief each (1 -> many)
pane broadcast --role <r> "<msg>" · pane gather --role <r>   # message / collect a team (scoped)

<target> = a pane id %NN · agent-N (swarm) · next (the other pane in your window) · or a CLI name (codex/claude/opencode/pi). A message with quotes, $, backticks, or newlines? Don't inline-quote it — Write it to a file and pane send <target> -f <file> (or pipe via stdin).

Why a command instead of raw tmux: agent TUIs stage a send-keys burst as a paste ([Pasted Content N chars]) and a welded Enter gets absorbed, so the text sits unsubmitted — the classic fumble. pane does stage → separate Enter → verify → retry for you, flattens newlines, sends literally, and refuses your own pane. Full detail: anu-talk (message) and anu-spawn (create).

(pane is on PATH once the anu plugin is enabled; else ~/.local/share/anu/plugins/anu/bin/pane.)

Calling the human

You can summon the human to your exact pane:

pane call "short reason"

Use it when you need a human decision, approval, credential, product judgment, missing context, or help with something you cannot safely infer. The notification is pane-tracked — when the human clicks it, anu focuses this pane.

• Don't stall silently. If you're blocked on the human, pane call them, then leave your question/request visible as your final message in the pane.
• Don't call for routine choices you can reasonably make yourself. Call only when progress would be risky, impossible, or meaningfully worse without human input — that's what keeps the notification meaningful.

You don't announce when you finish — anu watches your pane and notifies the human when a turn completes on its own. (Opt a pane out of "done" pings with tmux set-option -p @anu_notify_done off.)

The agent vocabulary

What each launches — so "make a codex pane" or "what is cdx" needs no lookup. Full modes/caveats are in anu-spawn. (Each alias also prepends a cosmetic screen-clear; the load-bearing command is shown.)

Alias	Launches	What it is
cx	claude --allow-dangerously-skip-permissions	Claude, skips the permission prompt (host)
cxx	claude --dangerously-skip-permissions	Claude full-auto on the host (real FS + creds)
cxc	box claude --dangerously-skip-permissions	Claude full-auto contained in a box/VM
cdx	codex	Codex, guardrails on (sandbox + approvals)
cdxx	codex --yolo	Codex YOLO — no sandbox, no approvals
cdxxs	codex --sandbox workspace-write --ask-for-approval never	Codex full-auto, sandboxed
c	opencode	OpenCode
pi	command pi	Pi (minimal harness, no permission popups)

Route to the right skill

You need to…	Skill
Message a pane / agent and read its reply (the pane command, in depth)	anu-talk
Create one or more agent panes (e.g. "one codex and one claude")	anu-spawn
Push a pane / your work onto the wall (the system wall display, default system.aadarwal.com)	anu-wall

Invoke with the Skill tool, or read directly: ~/.local/share/anu/plugins/anu/skills/anu-talk/SKILL.md · ~/.local/share/anu/plugins/anu/skills/anu-spawn/SKILL.md · ~/.local/share/anu/plugins/anu/skills/anu-wall/SKILL.md.

Scope

This is the basics: see, talk to, and spawn agent panes. Full parallel orchestration — topologies (star/pipe/tournament/mesh), worktrees, collect/merge — is the orchestration plugin and the swarm command; reach for it when one task fans out to many workers. This plugin grows into broader anu fluency over time; for now, panes.