burn451
Manage your reading queue from the terminal.

Save articles. Triage them. Let the rest burn.
CLI for Burn 451 — the reading triage system with a 24h countdown.
Why
You have 47 tabs open. You'll "read them later." You won't.
Burn 451 gives every saved article a 24-hour countdown. Read it or lose it. burn451 brings that system to your terminal — save URLs, check what's burning, search your history, see your triage stats. No browser required.
Install
npm install -g burn451
Quick start
burn451 login bmcp_your_token_here
burn451 flame
burn451 save https://karpathy.bearblog.dev/verifiability/
burn451 stats
Commands
burn451 login <token> | Authenticate (token from burn451.cloud/settings) |
burn451 flame | Show articles burning soon (< 6h remaining) |
burn451 list [filter] | List bookmarks: flame (default), vault, spark, all |
burn451 save <url> | Save URL to Flame (24h countdown starts) |
burn451 search <query> | Search across all bookmarks |
burn451 stats | Your reading triage statistics |
Examples
burn451 flame
burn451 list vault --limit=50
burn451 search "MCP server"
echo "https://simonwillison.net/2026/Apr/8/muse-spark/" | xargs burn451 save
Authentication
Two ways to authenticate:
Option 1: Login command (persistent)
burn451 login bmcp_your_token
Option 2: Environment variable
export BURN_MCP_TOKEN=bmcp_your_token
burn451 flame
Get your token at burn451.cloud/settings → MCP Server section.
How it works
burn451 CLI → Burn 451 API (Supabase) → Your reading queue
↕
~/.burn451/config.json (token)
~/.burn451/session.json (cached JWT, 5min TTL)
No intermediate server. Your CLI talks directly to Burn's API with your token. Session is cached locally for 5 minutes to avoid repeated token exchanges.
Part of the Burn ecosystem
Roadmap
License
MIT — see LICENSE