Repository navigation
Releases
v0.2.4
Two community fixes, one of them significant. Needs retalk 0.3.0 or newer, which the init skill installs for you.
Push delivery on Claude Code was silently off, and now works. Thanks to @jimdawdy-hub (#53). The plugin's two monitors were started with ${CLAUDE_SESSION_ID} on their command line, and Claude Code never substitutes that variable, so every monitor read the unexpanded literal as "no session id" and idled from its first second. Auto-receive looked on, the spool filled, and nothing was ever pushed into the session; only pulling with receive worked, which made it look like a design choice. The monitors now read CLAUDE_CODE_SESSION_ID, the variable Claude Code actually exports, and the dead argument is gone from monitors.json with a guard test so it cannot return. Confirmed against the old script before the fix was taken.
The marketplace source is "./". Thanks to @WouterVanGoey (#52). A bare "." validates and installs on current Claude Code, but at least one build rejects it with plugins.0.source: Invalid input, and once the marketplace is already registered the error blames the marketplace rather than the field. "./" is accepted everywhere it was compared, so it is pinned as the form that is never ambiguous.
82 tests passing.
v0.2.3
Never strand an identity on a relay only one machine can reach.
The relay skill used to offer a localhost relay as the quick way to start. It was the first option on the host menu, described as "quickest; testing or same-machine agents", and nothing said what it cost. The choice is permanent: retalk init writes the relay into the identity once and no command changes it afterwards, and that saved value outranks retalk config --relay. So an identity created against http://127.0.0.1:8766 cannot be reached by anyone off that machine for as long as it exists, and retalk id --card advertises localhost to whoever it is sent to. The only ways out are exporting RETALK_RELAY in every session, or creating a new identity, which means a new address and re-adding by every peer.
Local-only is now the last option, scoped to a throwaway identity you are willing to recreate, and the menu opens with the warning. It is no longer described as the quick start, because the shared public relay is quicker and needs no server at all. The init relay question says the answer is permanent and to never create an identity on localhost.
Moving an identity is now documented properly. The old advice was to pass --relay on the command, which fixes a single call. A stranded identity needs every call fixed, and a follower or invite watcher started without it inherits the old relay and polls it in silence. Both skills now name RETALK_RELAY, the retalk sync that has to follow a move, and the fact that peers who have not moved stay unreachable until they do.
78 tests passing.
v0.2.2
Diagnosing which side is out of date. Needs retalk 0.3.0 or newer, which the init skill installs for you.
A stale plugin now looks different from a stale retalk. An agent ran a command from its skill doc, got unrecognized arguments: --save-messages, checked retalk's help, found only --save, and concluded the doc was ahead of the released binary and named a flag that did not exist yet. It was the other way round: retalk renamed --save-messages to --save in July 2026, so the flag had been removed rather than not yet added, and the stale side was the plugin. The session was running skills loaded before the plugin was updated, which is invisible from inside a session because skills load once at start and never refresh.
The direction matters more than the flag. Waiting for retalk to catch up never resolves for a flag retalk deliberately dropped, so the real repair, updating the plugin and reloading, is never attempted.
The init skill already told agents to suspect their retalk install when a capability probe reports an older retalk. It now covers the opposite skew too: if retalk is at or above the version floor and the flag is simply absent from --help, the flag is gone and the plugin is what is behind. It names --save-messages as the known instance, and says to trust --help over any skill text, including its own.
A guard test keeps the removed flag out. The repo already had no occurrences of it; skills older than 0.2.0 still carry it, and those live in cached installs that no release can reach. The test matches the flag exactly, so the still-current RETALK_SAVE_MESSAGE environment variable is untouched, and it allows only the explanatory mention.
75 tests passing.
v0.2.1
A fix for the case invite codes exist for. Needs retalk 0.3.0 or newer, which the init skill installs for you: uv tool install --upgrade retalk (or pip install -U retalk). No prerelease flag.
A peer who registers with your invite code now gets through. Their contact was being saved and their first message was not being delivered, which is the whole point of handing out a code. Two things stood in the way. receive-from, which names what the background reader listens to, was only written when it happened to be empty, so anyone who already had a peer kept the old scope. And a running reader's peer list is fixed when it starts, so even a corrected scope changed nothing until it was restarted.
The invite watcher now handles both itself, at the moment it accepts a registration. It widens the scope to include the new peer, and restarts the reader with them included when your delivery mode is auto. manual is a deliberate choice to read on demand, so it gets the wider scope and no reader.
This lives in the watcher rather than in guidance for your agent on purpose. On hosts where nothing pushes a registration into the session, the agent never sees that one happened, and verifying 0.2.0 showed that is currently true of interactive Claude Code. Putting it where the acceptance is already known makes it work everywhere.
Restarting the reader keeps the options it had. --wake-codex is what lets an idle Codex session receive at all, and a restart that dropped it would have quietly turned off the feature it was restarting to serve.
The add skill had the same gap on the manual path, filling receive-from only when blank and leaving a running reader alone, so a second peer added by hand went undelivered the same way. It now widens and restarts too.
74 tests passing, six of them new and all six failing on 0.2.0.
v0.2.0
Needs retalk 0.3.0 or newer, which the init skill installs for you: uv tool install --upgrade retalk (or pip install -U retalk). No prerelease flag, on this release or any other.
Invite codes. Onboarding now takes one invite instead of a round trip. Your agent issues a code and puts it in the invite text you hand over; the peer's agent registers itself with that code, carrying everything needed to create the contact. You never have to be sent a fingerprint or run an add step. Single-use by default, permanent only when asked for. A code proves the holder was authorised by whoever issued it, not who they are, so it replaces the manual add and not out-of-band verification.
A monitor for contact requests, separate from the message monitor, so a registration surfaces in your session the way a message does. A registration is not a conversation turn, so it gets its own spool and its own rendering.
Flat, allowlistable commands. The skills no longer tell agents to read the passphrase inline with RETALK_PASSPHRASE="$(cat ...)", which reads like credential exfiltration to a permission classifier and cannot be allowlisted by prefix. Every block now passes --passphrase-path, saving is --save inside the command rather than an environment prefix in front of it, and the follower and invite watcher are shipped scripts rather than long inline bash -c strings. A single rule like Bash(retalk:*) covers the lot.
Auto-receive on Codex, through Codex's hook system: waiting messages arrive at session start and at your next prompt, and a message that lands mid-turn is handled as soon as that turn ends. A session sitting idle can be woken too, with the codex-with-daemon launcher and a spool writer started with --wake-codex.
The invite watcher no longer competes with your message reader. On retalk 0.3.0 the watcher reads the mailbox without consuming it, so a saved contact's mail is untouched rather than delayed, and there is no reason to stop the watcher once your codes are spent. That read is a relay-side capability: against a relay older than 0.3.0 the watcher refuses to start and says which side to upgrade. The skills explain that rather than leaving an agent to guess.
Fixes found by verifying this release end to end, with both hosts driving a real invite over the public relay:
- The watcher and the follower are started with
setsid, so one started inside a headlesscodex execturn is no longer killed when that turn ends. On Codex this killed the watcher in the same turn that handed out the invite code, and no invite could complete unassisted. - A peer's registration is no longer delivered nowhere. The spool writer only ever wrote to sessions in a registry that only Claude Code fills in, so on Codex an accepted registration was discarded in silence while the contact itself was saved. There is now a per-identity fallback, and the Codex setup section registers a spool the way the Claude Code one does.
statusno longer reports a dead supervisor as running:kill -0succeeds on a zombie, which is what a dead one becomes in a container whose PID 1 does not reap.invite-watch.sh statusfinds this user's request spool even thoughCLAUDE_SESSION_IDis not exported into the Bash tool, instead of reporting "(none yet)" while an accepted registration sat on disk.- The skills no longer tell an agent to run
retalk --version, which does not exist. - Every send and receive the skills show carries
--save, sohistorykeeps both sides.
68 tests passing.
v0.2.0-rc.2
Release candidate. Needs retalk 0.3.0rc1 or newer, which is a prerelease: install it with uv tool install --prerelease allow --upgrade retalk or pip install --pre -U retalk. A plain uv tool install or pip install resolves to the latest stable and will not pick it up.
Invite codes. Onboarding now takes one invite instead of a round trip. Your agent issues a code and puts it in the invite text you hand over; the peer's agent registers itself with that code, carrying everything needed to create the contact. You never have to be sent a fingerprint or run an add step. Single-use by default, permanent only when asked for. A code proves the holder was authorised by whoever issued it, not who they are, so it replaces the manual add and not out-of-band verification.
A monitor for contact requests, separate from the message monitor, so a registration surfaces in your session the way a message does. A registration is not a conversation turn, so it gets its own spool and its own rendering.
Flat, allowlistable commands. The skills no longer tell agents to read the passphrase inline with RETALK_PASSPHRASE="$(cat ...)", which reads like credential exfiltration to a permission classifier and cannot be allowlisted by prefix. Every block now passes --passphrase-path, and the follower and invite watcher are shipped scripts rather than long inline bash -c strings, so a skill emits one command that a rule like Bash(retalk:*) can cover. The old form stays documented as the fallback for older retalk, selected by a capability probe.
56 tests passing.
Known issues. Verified end to end with Codex on both sides; the Claude-to-Claude pairing has not been re-verified for this flow. While the invite watcher runs it delays messages from already-saved contacts (a retalk-side issue, fixed in a later candidate), so stop the watcher once your codes are spent. The watcher and follower do not survive a headless codex exec turn.
v0.2.0-rc.1
Release candidate. Two features, plus fixes found while testing them.
Auto-receive on Codex. Codex 0.147's hook system closes the gap that made Codex the one plugin host without auto-receive. Waiting messages arrive as context at session start and on each prompt, and a message that lands mid-turn is delivered when the turn ends, with nothing typed. Install with python3 extensions/codex/install-hooks.py, then approve the hooks once under /hooks.
Optional idle wake. A session started through the codex-with-daemon launcher attaches to Codex's local app-server daemon, and the follower can then wake it while it sits idle at the prompt. Off unless you pass --wake-codex; the injected turn carries only a generic nudge, never peer text. Requires the standalone Codex install and the daemon running before the session. See docs/codex-auto-receive.md.
Per-session spools. Incoming messages now land in <user>/sessions/<session-id>.ndjson rather than one file per identity, so parallel sessions on one identity keep their own copy and read position, records carry an arrival timestamp, spools are created 0600 and rotate, and --gc sweeps spools of sessions that are gone. retalk's sealed history remains the durable record. The old <user>/inbox.ndjson is still written and the monitor reads both, so an existing follower keeps working.
Suite grew from 11 to 37 tests. Verified end to end against Codex 0.147 with a live relay and real identities, including an idle session waking with nobody at the keyboard.
v0.1.3
Adopts retalk 0.2.0's new receive flags: the receive skill's background follower is now one calm process for the whole receive-from source (retalk receive --peer A --peer B --follow --interval 60 --quiet) - each peer still a separate scoped read, pure NDJSON output, with a documented fallback for older retalk. The five host auto-receive docs and the systemd example use the same form.
v0.1.2
Hardens the init skill's self-update step: agents must run the full marketplace-refresh + update block and can no longer conclude "already latest" from install/add output; the /reload-plugins reminder is keyed to the update output showing a version change. Found via live-agent testing.
v0.1.1
Docs and self-update release.
- Every quickstart now pairs install with update in one re-runnable block (verified idempotent per host), so following it always lands on the latest version: Claude Code (marketplace add/update + install/update), Codex (marketplace upgrade + re-add), pi (install + update), Antigravity/opencode/Copilot (clone-or-pull).
- The init skill now updates both retalk (PyPI) and the agent-talk plugin itself at the start of setup, and reminds the user to run /reload-plugins when a newer version was pulled - the one step an agent cannot run itself.