Skip to content

v0.2.0

Choose a tag to compare

@xhluca xhluca released this 14 Aug 22:01
· 4 commits to main since this release
55465f9

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 headless codex exec turn 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.
  • status no longer reports a dead supervisor as running: kill -0 succeeds on a zombie, which is what a dead one becomes in a container whose PID 1 does not reap.
  • invite-watch.sh status finds this user's request spool even though CLAUDE_SESSION_ID is 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, so history keeps both sides.

68 tests passing.