Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

AI helpers

AI is optional and off until you turn it on: Burrow uses no provider, not even an installed claude or codex CLI, until you enable one (ai-enable in the config file) or sign in to one in Settings. Generation happens while you write, you review it, and generated text is always disclosed when you publish.

Providers

You use your own accounts:

ProviderHow you sign in
Anthropic APIAPI key (stored in the Keychain)
OpenAI APIAPI key (stored in the Keychain)
Cloudflare Workers AIAccount ID and API token. Defaults to Gemma 4.
Local Claude Code or CodexUses your installed claude or codex CLI and whatever account it’s signed in to
Your blyg serverIts /generate endpoint, if enabled
ChatGPT accountSign in with ChatGPT. Unofficial: this uses the same sign-in as OpenAI’s Codex CLI, which OpenAI doesn’t offer to third-party apps. It may break or be blocked at any time.

Not offered: signing in with a claude.ai (Pro/Max) subscription. Anthropic’s terms don’t allow third-party apps to use claude.ai logins. To use a Claude subscription, install Claude Code and pick the local Claude Code provider.

Connecting and generating

  1. Turn a provider on. Either open Settings › AI (⌘, then “AI accounts…”) and switch on Claude Code or Codex, paste an API key, or sign in, or add it to the config file:

    ai-enable = codex
ai-enable = claude-code
ai-provider = codex        # which one ⌘G uses (optional)

    API keys go straight to the Keychain and are never shown again: Settings shows “key saved” and a Remove button.

  2. In a post, write a gap: [TK]one sentence on why, in my voice[/TK].

  3. With the caret inside it, press ⌘G. The status bar shows generating… (codex); esc cancels. The answer is written in place as [TK]instruction[=]output[/TK]. Press ⌘G inside it again to regenerate.

The config keys ai-model and ai-provider-model pick models, and ai-style-prompt adds your own instructions to every prompt (“Write plainly. British spelling.”). See Configuration.

The helpers

⌘G anywhere outside a gap opens the helpers:

HelperWhat it does
Fill a gap hereInserts an empty [TK][/TK] at the caret for you to fill in.
Shorten to fit 1000Also ⇧⌘G. Rewrites a fragment to fit, shown as a word diff: ⏎ accepts, esc rejects.
Continue this thoughtWrites on from the caret.
Outline a threadDrafts the outline of a new thread.
ProofreadTypos and grammar only, applied as a plain edit.
AI replyFrom a post you’re reading: a reply stub with a first draft.

Each generating helper writes its text as a TK span, so the preview tints it and it’s disclosed like any gap.

Disclosure

Generated text is always disclosed as generated when you publish. Burrow records which model wrote each gap and sends it to your blyg with the text (blygger-studio 0.28 or later; see Server requirements). If your blyg’s studio is older, Burrow warns you before publishing generated text, and Cancel is the default. Proofreading isn’t generated prose and isn’t disclosed.

If generated text in a thread holds a quote (![[id]] on its own line) that the gap’s instruction didn’t ask for, the publish sheet warns you: publishing would quote that post and notify its author (see TK: gaps for later).

When you read other blygs, text they mark as generated is the publisher’s own disclosure: Burrow shows it, and says it isn’t verified (see Generated text).

How the providers, sign-in, prompts and provenance work inside is in blyg-ai.