mirror of
https://github.com/AgentSeal/codeburn.git
synced 2026-10-31 19:40:54 +00:00
9a624cc2e7
Cursor 3.27 can store its app session as cursor-safe-storage:v1 ciphertext (Chromium v10, key in the "Cursor Safe Storage" keychain item), behind Cursor's own cursor.storage.authTokenEncryptionAtRest flag. CodeBurn read it as an expired login. The CLI and the menu bar now unlock it with that item and run the usual JWT checks; the newline `security -w` appends is trimmed before the KDF. Keychain consent is user-initiated, as for Claude: the first read happens on `codeburn import cursor --sync`, `codeburn quota`, or Retry/Reconnect on the menu bar's Cursor quota. Background syncs and dock refreshes read only after one such read succeeded, reuse the opened token per blob, and the first refused read switches that off again. Status never reads the keychain. No service-only keychain lookup, since after a Deny it asks again. Windows and Linux say CodeBurn cannot unlock the session there yet; the desktop app, VS Code and the Windows tray show the new `locked` line in all locales. Docs describe the prompt and what Always Allow grants. Closes #1801 |
||
|---|---|---|
| .. | ||
| en.lproj | ||
| fr.lproj | ||
| ja.lproj | ||
| ko.lproj | ||
| ProviderIcons | ||
| zh-Hans.lproj | ||
| zh-Hant.lproj | ||