(1/2) agmsg 1.5.0 is out, and this one is for people who run their agents in Orca (@orca_build). If you have three or five Claude Code or Codex sessions open in Orca tabs, each in its own worktree, the tabs don't know about each other. You are the one carrying results from one to the next. That carrying is the part agmsg does. From 1.5.0, agmsg treats Orca as a terminal it knows how to work with, next to tmux and herdr. An agent in an Orca tab can join a team, find the other agents, read a tab's screen (peek), and nudge one when a message lands (poke). It can also open a new tab and start an agent there, close it, and put the agent's name on the tab. Poke checks Orca's own composer draft first, so it won't type over something you're in the middle of writing. Nothing to configure; it detects Orca from the environment. What that gets you: your Orca tabs become teammates. The Codex tab asks the Claude Code tab to review a diff, then goes back to its own work. The reply lands in its inbox and wakes it. Each agent keeps its own context, so "pick up where we left off yesterday" works, and the whole exchange is a history you can read. Orca has its own orchestration for a coordinator dispatching workers, as far as I can tell from the docs. agmsg is the other shape: no coordinator required, any agent can message any other by name, and the same team can include a tmux pane, an agent on another machine, or a human. Orca tabs are one more place a teammate can live. Nothing changes if you don't use Orca. Underneath, the terminal drivers got better: each operation now asks the terminal's driver what it can do, so a new terminal is one driver file, and Orca is the first added that way. The v2 delivery layer rides on those drivers, so this is groundwork for it too. The driver sits on Orca's own CLI, so thanks to the @orca_build team for exposing it. If you're on the Orca side and want to look at the driver, it's in the release below. github.com/fujibee/agmsg/rel… #agmsg ---------- (2/2) Also in this release: - fix now repairs more of the crashed Codex agent cases, and says so when the Codex sandbox refuses - install.sh --agent-type no longer rewrites the shared SKILL.md's type - Codex: incoming messages no longer stick to the old conversation after /clear - uninstall.sh now cleans up a custom CODEX_HOME and the skills it put into OpenCode and Grok If you run agmsg inside Orca and something snags, an issue with the tab layout and the agent you were using is usually enough to reproduce it.