Repository navigation
v0.5.0
tmag 0.5 knows two more coding agents, Pi and oh-my-pi, next to Claude Code and Codex.
Pi and oh-my-pi
- Neither has hooks, so tmag ships an extension for each that reports what changes, in order and without holding up the agent. Their panes show their sessions on process proof, with states, bells, the picker, the status line and
jump, as for the other agents. sendandinterruptreach them through their pane, andread --lastreads the reply from their session file (pi-jsonl). A dialog of a Pi extension, oh-my-pi'sasktool and its tool approvals block the session; they are answered only in the agent.- They work with the other agents: the
peersskill comes to them too, and tmag proves their tools as callers throughPI_SESSION_ID. - A Pi or oh-my-pi run for another program (rpc, json and print modes) is a service: no pane shows it and nothing types into the program that runs it.
- Checked against Pi 1.5.0 and oh-my-pi 18.18.6.
Setup
prefix + M-ainstalls tmag's packages in Pi and oh-my-pi from the tmux plugin's own directory (pi install,omp plugin install), so they always match the binary and update with the plugin. It needs the tmux plugin, installed through TPM;tmag doctorsays when it is missing.tmag doctorchecks all four agents at once, andtmag uninstalllists the commands that remove Pi's and oh-my-pi's packages, before the plugin they come from.
Contract
- A session's end is reported as
SessionEndfor every agent. Pi's and oh-my-pi's other events keep their own names, such asmessage_endandagent_settled. agenttakes the valuespiandomp, andtranscript.formatthe valuepi-jsonl.
Upgrading
prefix + U updates the plugin, which fetches the 0.5.0 binary on its next load; then prefix + M-a brings the agent plugins to 0.5.0 and connects Pi and oh-my-pi where they are installed. Codex asks again to approve tmag's hooks (/hooks). See Installation and Updates.
What's Changed
Full Changelog: v0.4.0...v0.5.0