Finding / cursor

2026-10-24-cursor-the-origin-cli-now-records-usage-telemetry-by-default-where-cursor-enables-it-and-labels

The Origin CLI now records usage telemetry by default where Cursor enables it, and labels each run as human, Cursor agent or other agent. The Origin CLI gained opt-out usage telemetry. Its own message says it records which commands run and how they end, never their arguments; the record also carries the repository slug and whether a human, a Cursor agent or another agent ran the command. The local spool carries an account hash; transmitted events carry the generic author category and repository, under the caller’s authenticated identity. Whether any account currently has the server flag on is not visible from outside.

Channel: tagged-release (present in Origin CLI stable artifact 2026.10.23-18-47-36-f52be1e and latest 2026.10.24-05-09-43-624e85d; absent from 2026.10.13-14-06-43-ea1dfe5). Half: both. Date: 2026-10-23.

Operator consequence: Where policy limits telemetry from developer tools, set ORIGIN_NO_TELEMETRY=1 (or DO_NOT_TRACK=1) in shells, CI and agent environments; the variable works even where the set-telemetry command is hidden. The client recognizes environment markers from other harnesses, but sends only human, cursor_agent or other_agent rather than naming a rival harness. Review the authenticated repository-level usage disclosure in your tool policy.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-cursor-the-origin-cli-now-records-usage-telemetry-by-default-where-cursor-enables-it-and-labels

Profile citations

  • cursor / claim / origin-cli-telemetry-categories

Source links

Primary links, including exact changelog lines when available.