The same interface, as its own window instead of a tab. Signed and notarised, with no server running anywhere - not even the small Go one the browser build can use.
The same as the browser build: a folder, a GitHub repository, a git remote, or a bucket to read drafts from, and a token if the destination is GitHub. Nothing else - no account with us, no licence key, no setup step the web build does not also have.
The browser build reaches a folder through the File System Access API, which is Chromium's alone - Safari has no equivalent, and never has. The desktop app's web view is Safari's own engine, so a folder on this computer would be exactly as unreachable inside it as in a Safari tab, if it went through the same door. It does not: the desktop shell talks to the real filesystem directly, over its own IPC boundary, and a folder chosen there works regardless of which engine is rendering the page around it.
A git repository gets the same treatment. In a browser there is no git at all, so reaching one needs a CORS proxy and JavaScript standing in for a real client. Here it drives the git already installed on the machine - the credential helper and ssh agent already set up are the ones it uses, and neither is asked to trust a proxy.
Built on Tauri: a universal binary for Apple Silicon and Intel, signed and notarised in CI, with the same zero-telemetry policy as everything else here - no analytics, no crash reporter, no update check that phones home before you ask it to.