Cookie Auth Chrome Reader
Phase 16 Step 16.4 completed on 2026-05-21.
Next: Safari binarycookies reader
What Changed
- Chrome profile discovery now covers modern
Network/Cookies stores and keeps deterministic Default / Profile * ordering.
- The Chrome reader copies non-temp cookie stores before opening SQLite read-only, then queries provider cookie targets and maps fallback states without exposing secrets.
- Cookie decryption is injected through
ChromeCookieDecrypting, so tests use synthetic encrypted values and never touch real Keychain or browser data.
- Provider config now includes Claude
sessionKeyV2, Anthropic domains, and ChatGPT authjs token aliases.
Validation
swift test --filter CookieProviderConfigTests --filter ChromeCookieReaderTests passed 9 tests.swift test built cleanly and ran 400 tests; the remaining failures are the planned Step 16.5 Safari notImplemented contracts.
Residual Risk
- Production Chrome AES/Keychain decryption still needs a concrete decryptor before end-to-end browser cookie extraction is complete.
- Safari binarycookies parsing remains the next implementation step.