cd /news/ai-tools/show-hn-better-backlog-filter-github… · home › topics › ai-tools › article
[ARTICLE · art-159157] src=github.com ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

Show HN: Better Backlog: Filter GitHub issues with decision models

BerriAI released Better Backlog, an open-source tool that filters GitHub issues using natural-language criteria evaluated by decision models, run locally on Node 22 or newer with no npm install. The tool reads issues through the user's existing GitHub CLI login, requires a TypeSafe API key or a custom gateway URL and key entered in Settings, and reloads issues every 24 hours by default with a live countdown; results are cached until the next reload. A companion CLI (node cli.mjs filter "<criterion>" --json) shares one cache and recent-filter list with the running app at 127.0.0.1:4317.

read2 min views1 publishedOct 28, 2026
Show HN: Better Backlog: Filter GitHub issues with decision models
Image: Michielbdejong (auto-discovered)

Filter GitHub issues in your own words with decision models.

Paste this into Claude Code, Codex, or any coding agent:

Set up Better Backlog for me locally from https://github.com/BerriAI/better-backlog
1. Clone it into ~/better-backlog, or pull if it is already there. It needs Node 22 or newer and no npm install.
2. Check that the GitHub CLI is logged in with `gh auth status`. If it is not, ask me to run `gh auth login`.
3. Ask me which GitHub repository to filter, as owner/name.
4. Start it in the background with `BETTER_BACKLOG_REPO=<owner/name> npm start` and open http://127.0.0.1:4317.
5. Ask me to paste my TypeSafe API key, or my gateway URL and key, into Settings on that page. Never ask for the key in chat.
6. Confirm the issues load. When I ask you to filter issues, use `node cli.mjs filter "<criterion>" --json` from the repo; `node cli.mjs --help` lists everything else.
git clone https://github.com/BerriAI/better-backlog
cd better-backlog
npm start

Open 127.0.0.1:4317. Better Backlog reads GitHub issues using your existing GitHub CLI login. If you need to sign in:

gh auth login

Choose a repository and paste your TypeSafe key in Settings. Save, type a criterion, and press Enter. Add another to narrow the list.

Prefer a gateway? Choose it in Settings, enter its URL and key, and select a decision model.

Issues reload every 24 hours, with a live countdown. Change the interval in Settings. Reload fetches fresh issues and resets the countdown.

Filter results are cached until the next reload. Recent filters sit on the left: a solid dot is fresh and opens instantly; a hollow dot reruns against the new issues.

Keys are saved in .env and issue downloads in .local/, both gitignored.

node cli.mjs filter "people asking for new providers" "opened this month"
node cli.mjs recent
node cli.mjs forget "people asking for new providers" "opened this month"
node cli.mjs issues --state closed
node cli.mjs reload

Add --json for machine-readable output and --repo owner/name to pick a repository. The CLI uses the running app when it is open, so both share one cache and one list of recent filters.

Icons from Octicons by GitHub, MIT licensed; see NOTICE. Font: Geist, SIL Open Font License.

── more in #ai-tools 4 stories · sorted by recency
── more on @berriai 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/show-hn-better-backl…] indexed:0 read:2min 2026-10-28 · —