FAQ

FAQ

Does the plugin store my CSDN password? No. It never asks for it. You log in once in a real Chromium window, and the session cookie lives in a local Playwright profile under %LOCALAPPDATA%\CSDN-Draft-Publisher\.

Can it publish articles for me? No, by design. The automation only looks for the save-draft button and explicitly avoids publish controls. You review and publish on csdn.net yourself.

Does it work on mobile? No. The bridge requires Node.js APIs and a local Python process, so the plugin is desktop-only (isDesktopOnly: true).

I have multiple vaults — do they fight over the bridge? They share the same port. Whichever starts first owns the bridge; other vaults reuse it. Toggling the service off in one vault only stops a bridge that vault started.

Where are my logins stored? In Chromium browser profiles under %LOCALAPPDATA%\CSDN-Draft-Publisher\, one per account. Clearing login state in the settings removes the corresponding profile.

Does it upload local images? Not automatically. Local image references in your note are detected and reported so you don't forget them, but you upload images through CSDN's own editor or use hosted URLs.

What data leaves my machine? Only what CSDN itself receives when you save a draft. The bridge listens on 127.0.0.1, there is no telemetry, and no note content goes anywhere else.

Is the automation against CSDN's rules? The plugin automates your own logged-in session to save drafts — the same actions you would perform by hand. It never auto-publishes and never interacts with accounts other than yours. That said, it is an independent open-source tool, not affiliated with CSDN.