Merged
Conversation
Previously the cache_guid → email mapping was built once at Chrome startup, before sync initialized — so cache_guid didn't exist yet and the mapping was always empty on first run. Now the proxy scans Preferences files on demand when a client_id is first seen, then caches the result. Works correctly for: - First-time sync (cache_guid appears after sync init) - Multiple profiles (scans all Profile dirs on miss) - New accounts added mid-session
…erences Chrome generates cache_guid in memory and starts syncing before writing transport_data_per_account to disk. For profiles with a single logged-in account, use that email directly instead of returning unknown.
ClientToServerMessage.share contains the user's email on every request. This eliminates the need for LD_PRELOAD account mapping to identify users — the server can now work correctly without the payload proxy.
Chrome sends the signed-in account email in ClientToServerMessage.share on every request. This eliminates the need for LD_PRELOAD injection, HTTP proxy, and Preferences file mapping entirely. - Remove crates/payload/ (LD_PRELOAD .so, HTTP proxy, account mapping) - Remove docs/account-mapping.md - Server reads email from msg.share, falls back to anonymous@localhost - Remove auth middleware (no longer needed) - Remove tower dependency - Update CLAUDE.md and README.md
loyalpartner
added a commit
that referenced
this pull request
Apr 18, 2026
* refactor: lazy-load account mapping on cache miss instead of startup Previously the cache_guid → email mapping was built once at Chrome startup, before sync initialized — so cache_guid didn't exist yet and the mapping was always empty on first run. Now the proxy scans Preferences files on demand when a client_id is first seen, then caches the result. Works correctly for: - First-time sync (cache_guid appears after sync init) - Multiple profiles (scans all Profile dirs on miss) - New accounts added mid-session * fix: fallback to single-account email when cache_guid not yet in Preferences Chrome generates cache_guid in memory and starts syncing before writing transport_data_per_account to disk. For profiles with a single logged-in account, use that email directly instead of returning unknown. * feat: read user email from protobuf share field instead of header ClientToServerMessage.share contains the user's email on every request. This eliminates the need for LD_PRELOAD account mapping to identify users — the server can now work correctly without the payload proxy. * refactor: remove LD_PRELOAD payload, use protobuf share field for auth Chrome sends the signed-in account email in ClientToServerMessage.share on every request. This eliminates the need for LD_PRELOAD injection, HTTP proxy, and Preferences file mapping entirely. - Remove crates/payload/ (LD_PRELOAD .so, HTTP proxy, account mapping) - Remove docs/account-mapping.md - Server reads email from msg.share, falls back to anonymous@localhost - Remove auth middleware (no longer needed) - Remove tower dependency - Update CLAUDE.md and README.md * docs: remove LD_PRELOAD references from README and architecture docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.