The default background update changes a global CLI installation without a separate update request, which is a user-visible software-management risk. The registry requests retrieve version metadata, and I found no install hook or evidence of data exfiltration.
Static reason
No blocking static signals were detected.
Trigger
Once, on the first chat.message, when a global XP-Gate installation exists and is outdated.
Impact
The global CLI can be replaced with a newer release without a separate update request from the user.
Mechanism
It checks the npm dist-tags endpoint and runs npm install -g for the latest @boyingliu01/xp-gate version unless autoUpgrade is explicitly false in the XP-Gate config.
Evidence
index.ts~/.xp-gate/xp-gate-version-check.json~/.xp-gate/opencode-plugin-version-check.json~/.xp-gate/upgrade-notice.jsonglobal npm installation of @boyingliu01/xp-gate
Network endpoints2
registry.npmjs.org/-/package/%40boyingliu01%2Fxp-gate/dist-tags/-/package/@boyingliu01%2Fopencode-plugin/dist-tags