FAQ

Why is it called Burrow, when everything says “blygger”?

Burrow is a blygger client: a client for the Blygger protocol. It was called Blygger Desktop up to 0.6.0. Only the name you see changed. The bundle ID, the blygger command, the config path (~/.config/blygger/config), the BLYGGER_* environment variables, the data folder and the Keychain items kept the old name, so existing installs carry on without migrating. See The rename.

My app is still called Blygger.app in Finder.

That’s expected if it updated itself from 0.6.0 or earlier: the updater replaces the app where it is, so the file keeps its name while being Burrow inside. Run the one-line installer to get Burrow.app, or rename it while it isn’t running. See Blygger.app → Burrow.app.

Can I use Burrow with a stock Blygger blog?

Yes. Burrow 0.13 needs blygger-studio 0.47 or later, stock and unpatched. Sign in with your browser, an API token from the studio’s Client access page, or your studio password. On an older blyg everything syncs except posts with labelled links ([[id | label]]), which an older studio doesn’t understand: they wait until the blyg is updated, and publishing one offers to write the links bare. See Server requirements.

Is my data safe? Where is it?

Your posts live on your blyg; Burrow keeps a local copy in ~/Library/Application Support/org.blygger.desktop/, so everything works offline. Scratch notes and the notes drawer stay on your Mac until you make them drafts. Your sign-in (browser grant, token or password) and AI keys are in the macOS Keychain, never in a file, and never logged.

Burrow is vibecoded and provided as is, with no warranty. Keep backups of your blyg.

Does Burrow send anything anywhere else?

Only what a feature needs, when you use it:

• your blyg, with your sign-in;
• other blygs’ public files, without your token, when you open a profile or a quoted post you don’t hold;
• GitHub, about once a day, to check for updates (auto-update = off stops it);
• the AI provider you switched on, only when you ask it to generate;
• the filter lists for the browser pane’s content blocking, about once a week (content-blocking = false stops it);
• the sites behind links you open, images in posts, and YouTube (through youtube-nocookie.com) when you click a video.

Burrow has no analytics or telemetry.

Why can’t I delete a published post?

Blygger doesn’t delete published work. Post › Withdraw… withdraws it: the post stays listed as withdrawn, visibly, and that can’t be undone. Drafts and scratch notes can be deleted (⇧⌘⌫).

Why can’t I fork this post?

Forking descends only from pinned versions. Pick a pin in the post’s version pill (‹ vN ▾ ›, or press [), then Fork this pin. If the post has no pins, it can’t be forked. Your own posts fork the same way, from ⌘Y: pick a pinned version, then Fork this pin.

How do I undo my edits to a published post?

Discard changes (⌥⌘Z, Post › Discard Changes…, or the toolbar’s eraser) puts the editor back to the version your blyg has published, after asking. The public post doesn’t change. On Windows it has no key: use the Post menu or the toolbar. See Discard changes.

What’s the text after | in a link?

The link’s label: [[id | Gardens, not streams]] reads “Gardens, not streams” on the published page. Edit it to rename the link. The [[ picker writes it for you, from the post’s heading or title. In a quote, ![[id | note]], it’s a note only you see. Labels need blygger-studio 0.47; on an older blyg the picker writes bare links. See Labelled links.

Why is a post waiting with “labelled links need studio 0.47”?

Your blyg runs a studio older than 0.47, which can’t show labelled links, so Burrow holds that post (and only that post) until the blyg is updated. Publishing it offers ⏎ to write its links bare and publish now. Burrow’s status bar has an Update your blyg link. See Server requirements.

Why won’t my quote go in?

Quotes (![[id]], or ![[id | note]]) only go in threads; ⌘T makes a fragment a thread. A partial quote’s passage must be in the quoted post exactly as written; the preview flags one that isn’t, and publishing refuses it.

Why doesn’t Burrow show follower counts or likes?

Blygger shows responses as a list, never a count, and following is private. Burrow follows the protocol’s rules: no counts anywhere social. The one exception is the lineage glyph, which says how many posts a post draws on and how many draw on it, the same numbers the web Studio shows.

Do I need to sign in again after updating?

Usually not. Only if your sign-in was made before your blyg ran blygger-studio 0.39, and you read on more than one Mac: studio 0.39 keeps read state behind its own permission (reading:state), which an older sign-in doesn’t have. Until you sign in again, posts you read are marked read on this Mac and wait to be sent; everything else syncs as usual, and Burrow says once that read state is waiting. To sign in again: Burrow › Disconnect… (keep the local copy), then connect with Sign in with browser and allow every permission. With an API token, make a new one in the studio’s More › Client access that includes reading:state.

Why did Burrow open the sign-in sheet by itself?

Your blyg refused Burrow’s sign-in: an API token expired (they last 30 days) or was revoked, a browser sign-in ended, or the server changed (a blyg that moved from the old patched Worker to a stock studio no longer takes the old owner token). Burrow stops syncing rather than retrying, keeps every change on your Mac, and says why. Sign in with your browser, or paste a new token from the studio’s More › Client access, and what waited is sent.

Can I bring my feeds from another reader?

Yes. Blyg › Import Subscriptions from OPML… (or Import OPML… on the Subscriptions screen, ⇧⌘S) reads the OPML file most feed readers export: tick the feeds you want, and Burrow subscribes them a few at a time, files them in an Imported feeds folder in the Reader, and keeps them out of your public blogroll. Blyg › Export Subscriptions as OPML… goes the other way. See Import and export subscriptions.

Can I sign in with my Claude Pro/Max subscription?

Not directly: Anthropic’s terms don’t allow third-party apps to use claude.ai logins. Install Claude Code and switch on the local Claude Code provider instead. See AI helpers.

macOS says Burrow “can’t be opened” or “Not Opened”.

Releases aren’t notarized yet. The one-line installer avoids this; for a browser download, see Downloading from the Releases page.

How do I report a bug?

Burrow › About Burrow › Copy build info copies the version, commit, update status and what your server supports (no paths, no token). Paste it into a GitHub issue.