Use the Bri CLI for notes and links
The CLI surface is intentionally small: publish Markdown, manage note state, manage quick links, inspect configuration, and run the MCP server.
Publishing commands
123bri publish --path ./note.md bri publish --stdin --title 'Generated note' bri slug --path ./note.md
bri slug is a local preview. It does not contact Bri or reserve a slug. bri publish requires a key with write permission unless you are using a signed-in web session through the dashboard.Note commands
12345bri notes list bri notes read <username> <slug> bri notes update <note-id> --path ./replacement.md bri notes delete <note-id> bri notes delete <note-id> --permanent
The delete default is a soft delete.
--permanent removes the note immediately and should be treated as irreversible.Version history is available for changes made through Bri:
123bri notes history <note-id> bri notes version <note-id> <version-id> bri notes restore-version <note-id> <version-id>
Restoring a prior version changes external state and requires write permission. Use
--json when a script needs stable structured output.Ask about a note
The AI command streams a concise answer grounded in one note:
1bri notes ask <username> <slug> --question 'What is the launch date?'
Use
--stdin for a question generated by another process. The endpoint is rate-limited, and it returns an error when AI is not configured or the note cannot be read.Quick links
Quick links are short redirects managed from the same account:
1234bri links list bri links create --key docs --target https://bri.fyi/docs --label 'Bri docs' bri links update <link-id> --target https://example.com/new-target bri links delete <link-id>
Link keys become short paths on Bri. Keep keys readable and avoid putting secrets in either the key or target URL.
Configuration and diagnostics
1234bri config list bri config set siteUrl https://bri.fyi bri doctor bri self-update --check-only
The local config file is
~/.config/bri/config.json. Supported values include apiKey, endpoint, siteUrl, username, timeoutMs, maxBytes, retries, copy, open, and color.For a single command, use environment variables instead:
1BRI_API_KEY='bri_your-key-here' bri notes list --json
The effective precedence is command-line flag, environment variable, saved config, then the production default. Never commit the saved config file or an exported key.