{"version":"2.1.265","anchor":"oauth-token-refresh-lock-telemetry-reordered-lock-helper-r","canonical_anchor":"oauth-token-refresh-lock-telemetry-reordered-lock-helper-r","heading":"OAuth token refresh lock telemetry reordered \/ lock helper renamed","tier":"internal","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/oauth-token-refresh-lock-telemetry-reordered-lock-helper-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### OAuth token refresh lock telemetry reordered \/ lock helper renamed\n\nOAuth token refresh lock now reports its \"acquired\" event later, closer to the actual read check\n\n**What**\n\nWhen Claude Code refreshes an OAuth (login) token, it briefly locks a file to coordinate with other processes. The `tengu_oauth_token_refresh_lock_acquired` telemetry event that marks this used to fire right after the lock file was acquired; it now fires later, immediately before the strict read-check that follows. The internal helper that acquires the lock was also swapped for a different one.\n\n**Why**\n\nThis is an internal reordering of when a telemetry event fires relative to the lock's actual use, which affects how accurately the event reflects the state of the lock at the time it's recorded.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}