Even if the cookie parameter is passed, it will still be read from the browser #84

New issue

Closed

opened 2026-02-13 17:27:48 -06:00 by mirrors · 3 comments

mirrors commented

2026-02-13 17:27:48 -06:00

Owner

Originally created by @infstellar on GitHub (Sep 4, 2025).

Since I have two users, even if I initialize the GeminiClient with the cookie of User B, it will still get the cookie from the browser logged in as User A.
This problem was resolved after I uninstalled browser-cookie3. It doesn't seem to be a major issue.

Originally created by @infstellar on GitHub (Sep 4, 2025). Since I have two users, even if I initialize the GeminiClient with the cookie of User B, it will still get the cookie from the browser logged in as User A. This problem was resolved after I uninstalled browser-cookie3. It doesn't seem to be a major issue.

mirrors

2026-02-13 17:27:48 -06:00

closed this issue
added the
enhancement
label

mirrors commented

2026-02-13 17:27:48 -06:00

Author

Owner

@yeucodonvn commented on GitHub (Sep 8, 2025):

me too, i had to remove it because i use chromium it doesnt recognize it

@yeucodonvn commented on GitHub (Sep 8, 2025): me too, i had to remove it because i use chromium it doesnt recognize it

mirrors commented

2026-02-13 17:27:48 -06:00

Author

Owner

@infstellar commented on GitHub (Sep 9, 2025):

This seems to be because when calling await self.client.init, the cookies are fetched again and the previously passed-in cookies are not used.

@infstellar commented on GitHub (Sep 9, 2025): This seems to be because when calling `await self.client.init`, the cookies are fetched again and the previously passed-in cookies are not used.

mirrors commented

2026-02-13 17:27:48 -06:00

Author

Owner

@HanaokaYuzu commented on GitHub (Oct 15, 2025):

Fixed in v1.16.0

@HanaokaYuzu commented on GitHub (Oct 15, 2025): Fixed in v1.16.0