DIYgod d8835acd02 fix(desktop): route the remaining main-process requests through Chromium and keep the CLI token out of logs ...

After the API bridge moved to `net.fetch`, several main-process requests still used
Node's `fetch`, which ignores the app's proxy settings: the update manifest and policy,
the main-process API client, file downloads, text-to-speech, page fetching for the
reader, and the Eagle, qBittorrent and custom integration requests. They now go through
`net.fetch` as well. The readability package takes a `fetch` implementation for that;
downloads hand it to ky. Requests that manage cookies by hand pass
`credentials: "omit"`, so Chromium does not keep them too.

A failed CLI login sync used to be logged with the whole command line, token included.
The command is now described with the token redacted, and the command's output is
scrubbed the same way.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-18 17:40:26 +08:00

..

configs

fix(styles): avoid DaisyUI border token collision

2026-07-25 20:17:55 +08:00

internal

fix: report the API as unreachable only when a probe confirms it

2026-09-18 16:18:30 +08:00

readability

fix(desktop): route the remaining main-process requests through Chromium and keep the CLI token out of logs

2026-09-18 17:40:26 +08:00