The earlier review correctly identified a reachable default self-update and a notice that can appear after the update runs. Under the current self-update rule, installing a newer release of this same package from npm with explicit off-switches is suspicious, not a block; the login CI check and metadata host checks are benign safeguards.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI startup schedules a detached check for an eligible global npm installation when the check is due; the worker updates only if npm reports a newer version.
Impact
A newer CLI release can replace the globally installed version and run on later invocations without a separate update command.
Mechanism
The worker fetches the latest dist tag from the npm registry and runs npm to install @oxygen-agent/cli at that version. Automatic updates can be disabled with --disable-auto, OXYGEN_NO_AUTO_UPDATE=1, or the saved setting.
Evidence
dist/index.jsdist/auto-update.jsdist/cli-install.jsdist/commands/update.jsglobal npm installation of @oxygen-agent/cli
Network endpoints1
/-/package/@oxygen-agent%2Fcli/dist-tags