Repository navigation
v0.6.0
tmag 0.6 delivers a prompt now, through each agent's own channel, and takes the panes tmux names.
Send through the agent's own channel
tmag sendis the one delivery verb. By default and with--replyit delivers now: through Claude Code's cross-session inbox, tmag's extension in Pi and oh-my-pi, or the Codex daemon's control socket. An idle session starts a turn; a working one reads the prompt at its next step, and the Codex daemon joins the active turn. A prompt is never typed into a busy pane.--waittakes a turn of its own once the session is idle, andtmag read ID --lastreturns that turn's reply.- An agent's prompt goes through the session's channel in any state, with the pane only as an idle fallback, and its first line names the proven sender. A person's prompt carries no sender line: it is typed into an idle pane, and goes through the channel while the session works and always to a Codex daemon thread.
replyis delivered now through the asker's channel. - An inbox is proven when its listener is the agent process that named it, checked again under the session's lock. A Claude Code background session is reached through its inbox.
- Claude Code applies its own inbound controls: a session that bypasses permission prompts holds a sent prompt for its person unless its
crossSessionInboundisaccept.
tmux targets and peers started in tmux
- Every verb takes any target-pane tmux takes on the current server (
%N, thework:1.0thatlistprints, a window name,{last}), resolved by tmux itself, orSERVER:%Nfor a pane of another server.list,inspectand every verb's report name such a paneSERVER:%Ntoo. A target tmux cannot find is refused. tmag waiton a pane lasts until its agent shows a session, so an agent can start a peer in a tmux window of its own and work with it through tmag. Thepeersskill teaches this, starting tmux ascommand tmuxpast any shell alias; until the session shows, the other verbs refuse the paneunboundwith anext:line that says to wait.tmag inspectlists a session's open requests with the id thattmag requestandtmag answertake.
Smaller changes
- tmag recognises Claude Code run as
claude.exe, as its npm package runs it, and its background supervisor's processes. tmag doctornamesmonitor-bell offandallow-set-title offwith theset -gline that restores each, and changes nothing.- The installer publishes the binary with one atomic rename. An interrupted install no longer leaves a lock that stops the next one.
- Agent configuration reached through a symlink is read.
- A tmag installed with mise is no longer a supported channel: the plugin keeps its binary in its own
bin/.
Contract
- A
Sendevent reportsviainboxbesidepaneandservice. The schema staystmag/v2, and the state directory keeps its layout: 0.5 state carries over as it is.
Website
- tmag has a landing page, with onboarding and best practices in English and Chinese, published from each release: https://chralpha.github.io/tmux-agent-experience/
Checked against Claude Code 2.1.319, Codex 0.167, Pi 1.5.0 and oh-my-pi 18.18.6.
Upgrading
prefix + U updates the plugin, which fetches the 0.6.0 binary on its next load; then prefix + M-a brings the agent plugins and the peers skill to 0.6.0. Codex asks again to approve tmag's hooks (/hooks). See Installation and Updates.
What's Changed
- fix(proc): recognize Claude Code run as claude.exe by @ChrAlpha in #12
- test(e2e): run panes under /bin/sh and leave no core dumps by @ChrAlpha in #13
- feat: send through each agent's own channel by @ChrAlpha in #14
- feat: take tmux targets, wait for peers started in tmux, and thin tmag by @ChrAlpha in #15
- fix(cli): list open requests in tmag inspect by @ChrAlpha in #16
- fix: name panes of other servers and start peers through command tmux by @ChrAlpha in #17
- docs: add a landing page published from each release by @ChrAlpha in #18
Full Changelog: v0.5.1...v0.6.0