Repository navigation
Agent updates: a registry version lower than the pin is offered as an Upgrade #148
Description
The problem
An agent added from the registry can be offered a downgrade labelled as an upgrade. If the registry's version for an agent is lower than the version the agent is pinned to, Patchbay reports an update: the Settings card, the Agent View's agent chip and the startup notice all offer it, and the confirmation asks "Upgrade ?".
Nobody has reported this yet. It follows from the code, and it can happen for real: a registry entry can move back, as asked for the opencode entry in agentclientprotocol/registry#716 (2.x back to 1.19.5). Someone pinned to 2.2.5 would be told 1.19.5 is an upgrade.
Cause
agentUpdates in src/orchestrator/agent-updates.ts compares the two versions for equality only, so any different version counts as an update, even though the function's own comment says an entry exists "only where there is something newer". test/agent-updates.test.ts covers a version ahead of the pin and the cases with nothing to offer, but not a version behind it.
Expected
An update is reported only when the registry's version is newer than the pin. A lower registry version is never offered as an Upgrade, on any of the three surfaces. A test covers it.
Activity
hussain commentedon Nov 6, 2026
Fixed in f2da66a — ships with 0.90.2. An update is now reported only when the registry's version is newer than the pin, so an entry that moves back shows nothing on the Settings card, the agent's chip or the notice. Upgrade checks the same fact after its fresh registry read, so a chip shown before the entry moved back says there's no newer version and leaves the agent as it is, instead of downgrading it.