What happened?
An opt-in env var (WIGOLO_CHROME_PROFILE_PATH, meant for authenticated fetches) copies your entire actual Chrome profile - cookies, saved logins, history - to a temp folder, and that copy is never used by the code that's supposed to consume it (dead code path) and never cleaned up. privacy leak, but only if you deliberately set that specific variable since default install never touches it. WIGOLO_CDP_URL with self launched chrome works.
I didn't experience this bug, claude code found it while I had it check it before installing, just FYI.
Command / tool call
No response
wigolo version
0.1.43-beta.0
OS + Node version
win11
Output of npx wigolo doctor (if relevant)
Logs / error output
What happened?
An opt-in env var (WIGOLO_CHROME_PROFILE_PATH, meant for authenticated fetches) copies your entire actual Chrome profile - cookies, saved logins, history - to a temp folder, and that copy is never used by the code that's supposed to consume it (dead code path) and never cleaned up. privacy leak, but only if you deliberately set that specific variable since default install never touches it. WIGOLO_CDP_URL with self launched chrome works.
I didn't experience this bug, claude code found it while I had it check it before installing, just FYI.
Command / tool call
No response
wigolo version
0.1.43-beta.0
OS + Node version
win11
Output of
npx wigolo doctor(if relevant)Logs / error output