Skip to content

fix(qoder): send desktop machine fingerprint on CN check-in - #259

Merged
caigee-cmd merged 2 commits into
mainfrom
fix/qoder-cn-desktop-checkin-headers
Oct 2, 2026
Merged

caigee-cmd merged 2 commits into
mainfrom
fix/qoder-cn-desktop-checkin-headers

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

  • Qoder CN daily check-in now sends the desktop campaign headers: Cosy-MachineOS, Cosy-MachineHostname, and the runtime-info fingerprint (Cosy-MachineToken, Cosy-MachineType, Cosy-MachineCode).
  • The worker no longer reuses the machine id as Cosy-MachineToken when the local runtime-info bridge is available.
  • Missing or failed fingerprint lookup still falls back to the previous machine id headers so check-in is not blocked.

Test plan

  • node --test worker/test/checkin.test.mjs (20 passed)
  • Local runtime-info produced distinct token/type/code headers
  • Restart a CN worker and run one manual check-in against a real account

The campaign service expects the desktop runtime-info headers, not the worker machine id reused as Cosy-MachineToken.
@caigee-cmd
caigee-cmd merged commit 3f11511 into main Oct 2, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant