Skip to content

v0.2.2

Choose a tag to compare

@xhluca xhluca released this 21 Aug 16:06
· 2 commits to main since this release
99bdae2

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.