Skip to content

Release history

byterover-cli releases

ByteRover CLI (brv) - The portable memory layer for autonomous coding agents (formerly Cipher)

All releases

27 shown

No immediate action
v3.16.1 Breaking risk
Auth

Stay signed in

No immediate action
v3.16.0 Breaking risk

Task cancel + update opt-out

No immediate action
v3.15.1 Breaking risk

Review toggle restored + cache cleanup

Config change
v3.15.0 Breaking risk
Breaking upgrade

Configurable settings

No immediate action
v3.14.0 Breaking risk

Review queue in web UI

No immediate action
v3.13.0 Breaking risk

Billing UI improvements + credit alerts

v3.12.0 Breaking risk
Security fixes
  • Dependency refresh cleared several `npm audit` advisories
Notable features
  • Per‑project tasks history in `brv webui` with filters, pagination, bulk delete and provider/model attribution (up to 1000 entries)
  • Synthesized files now receive full semantic frontmatter (title, summary, tags, related, keywords, timestamps)
Full changelog

ByteRover CLI 3.12.0 turns the Tasks page in brv webui into a per-project history. Every curate, query, and review you run is now saved across daemon restarts, with filters, pagination, bulk delete, and provider/model attribution. The release also fixes a sync regression that caused brv push to ship dangling related: references, and tidies up frontmatter so synthesized files render properly in the dashboard.

What's Changed

✨ Added

  • Tasks history in brv webui. Past curate, query, and review tasks now persist per project across daemon restarts (up to 1000 entries), with filters (status, date range, duration), pagination, per-task event log, bulk delete, clear-completed, and provider/model attribution on each row. By @bao-byterover and @ncnthien in #622

🚀 Changed

  • Synthesized files get full semantic frontmatter. brv dream synthesize now writes title, summary, tags, related, keywords, createdAt, and updatedAt alongside its existing synthesis fields, so dashboard context cards no longer render with empty preview slots. Existing synthesized files keep their old shape until regenerated. By @RyanNg1403 in #621
  • Consistent flow-style YAML in dream writes. brv dream's synthesize and consolidate steps now emit tags: [a, b, c] arrays like brv curate, so brv vc diffs stop reflowing brackets on every consolidate pass. By @RyanNg1403 in #621

🐛 Fixed

  • brv push no longer ships dangling related: links. *.abstract.md and *.overview.md entries are excluded from sync, but brv dream's cross-reference step and brv curate used to leave them in related:, so pushed parents landed on the remote with broken sibling references. Both write paths now filter excluded entries before write, and brv curate's update path also cleans pre-existing stale entries when it touches a doc. By @cuongdo-byterover in #618
  • Security dependency refresh. Refreshed package-lock.json to clear several npm audit advisories. By @bao-byterover in #623

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work with no migration. New semantic frontmatter applies forward only: older synthesized files keep their previous shape until they are regenerated.

🙏 Contributors

Thanks to @bao-byterover, @RyanNg1403, @ncnthien, and @cuongdo-byterover for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.11.0...v3.12.0

v3.11.0 Breaking risk
Security fixes
  • Security dependency refresh: updated package-lock.json to clear several npm audit advisories
Notable features
  • Added two new LLM providers: DeepSeek (chat and reasoner) and Z.AI's GLM Coding Plan subscription tier
  • Recall metadata (`matchedDocs`, `tier`, `durationMs`, `topScore`) now included in `brv query --format json` output
Full changelog

v3.11.0 adds two new ways to power your agent: DeepSeek (chat and reasoner models) and Z.AI's GLM Coding Plan subscription. It also unblocks Claude Opus 4.7, which started rejecting some calls from earlier brv versions, and tightens up a few rough edges in the provider picker and web UI.

What's Changed

✨ Added

  • Two new LLM providers: DeepSeek and GLM Coding Plan. Pick DeepSeek (deepseek-chat, deepseek-reasoner) or Z.AI's GLM Coding Plan subscription tier in brv providers connect or the web provider picker. The existing glm provider stays for pay-per-token users, so subscription and pay-as-you-go tiers no longer collide. By @ngduyanhece in #604
  • Recall metadata in brv query --format json. The JSON envelope now includes matchedDocs, tier, durationMs, and topScore, so scripts and IDE bridges can show evidence of what an answer was drawn from. By @danhdoan and @RyanNg1403 in #610

🐛 Fixed

  • Reasoning streams correctly for DeepSeek-R1 and Reasoner. Thinking output now shows up live and is carried back into follow-up turns. Previously the second turn of any multi-step query failed with a reasoning_content must be passed back error from DeepSeek. By @ngduyanhece in #604
  • Claude Opus 4.7 no longer fails with a 400 error. Opus 4.7 rejects temperature, top_p, and top_k; the CLI now drops those before sending to Anthropic and OpenRouter (and warns once). Opus 4.6 and other Claude models are unchanged. By @cuongdo-byterover in #612
  • Signing in to the GLM Coding Plan no longer rejects valid keys. API-key validation now tries each known model in turn instead of giving up after the first model-not-found, so a real key is no longer reported as invalid. The "Get your API key" link in both the TUI and the web UI also points straight to the key page. By @ngduyanhece in #604
  • OpenClaude icon shows up in brv webui. The LocalWebUI agent grid used to render OpenClaude as a missing icon; it now uses a monochrome SVG that matches the other connectors. By @cuongdo-byterover in #613
  • Security dependency refresh. Refreshed package-lock.json to clear several npm audit advisories. By @bao-byterover in #614

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work without any migration.

🙏 Contributors

Thanks to @ngduyanhece, @danhdoan, @RyanNg1403, @cuongdo-byterover, and @bao-byterover for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.10.3...v3.11.0

v3.10.3 Breaking risk
⚠ Upgrade required
  • After upgrading, run `brv restart` to align the CLI and background daemon versions; REPL header and MCP tool replies will indicate a mismatch.
Full changelog

This release makes daemon-version mismatches visible. After you upgrade brv, the background daemon can keep running on the older version with no obvious way to tell. The REPL header and MCP tool replies now flag the drift so you know to run brv restart.

What's Changed

🐛 Fixed

  • No more silent daemon-version mismatches. After upgrading brv, the background daemon could keep running on the older version and you'd have no way to tell, leading to confusing "why doesn't this new feature work?" moments. The REPL header now shows [outdated, daemon vX.Y.Z] next to the version when this happens, and replies from the MCP tools (brv-query, brv-curate) include a short note when the daemon and CLI are mismatched. Run brv restart to align, or restart your IDE for the MCP side. By @bao-byterover in #592

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work without any migration.

🙏 Contributors

Thanks to @bao-byterover for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.10.2...v3.10.3

v3.10.2 Breaking risk
Notable features
  • `brv curate` performance improvement: batches LLM calls and reuses prompt parts, saving 8‑30% token cost
Full changelog

This release makes brv curate noticeably faster and cheaper, and clears up two ByteRover sign-in rough edges: connecting now activates the provider right away, and slow networks no longer get falsely flagged as signed out.

What's Changed

🔄 Changed

  • brv curate is faster and cheaper. Curate now batches its smaller LLM calls together and reuses the unchanging parts of the prompt across calls. Anthropic users save 21-30% on token cost, OpenAI users around 8%, and big-folder curates finish noticeably sooner. By @danhdoan in #601
  • Clearer sign-in error for ByteRover. When you try to use ByteRover without being signed in, the error now lists every option: brv login for interactive shells, plus a signup URL, an API-key URL, and brv login --api-key for headless or CI environments. By @bao-byterover in #595

🐛 Fixed

  • ByteRover provider activates on connect. Picking ByteRover used to leave it "connected but inactive", so brv curate would still say "no provider connected". Activation now happens right away. By @RyanNg1403 in #596
  • No more spurious "signed out" on slow networks. The startup auth check timed out after 500 ms, well below a real round-trip on home Wi-Fi, mobile, or VPN. Timeout is now 4 seconds with a single retry, so transient blips no longer look like a logout. By @RyanNg1403 in #596

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work without any migration.

🙏 Contributors

Thanks to @bao-byterover, @danhdoan, and @RyanNg1403 for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.10.1...v3.10.2

v3.10.1 Breaking risk
Notable features
  • Per‑project `brv review --disable`/`--enable` to opt out of human‑in‑the‑loop prompts
  • `brv curate` now returns immediately, with summary rebuild running in background
Full changelog

This release cuts the wait at the end of brv curate, adds a per-project switch to opt out of human-in-the-loop reviews, and tightens up two error paths: brv vc status / pull now name the files in the way, and OpenAI-compatible provider setup catches bad URLs before they break the REPL.

What's Changed

✨ Added

  • brv review --disable / --enable, per project. Opt a project out of the human-in-the-loop review prompts and backup writes, or turn them back on. Run brv review with no flags to see the current state. brv review pending / approve / reject are unchanged. By @RyanNg1403 in #563

🔄 Changed

  • brv curate returns to your prompt right away. The final summary-rebuild step now runs in the background instead of making you wait. Nothing is skipped, just moved off your wait time (about 18 seconds saved on a typical run). By @cuongdo-byterover in #582

🐛 Fixed

  • Clearer brv vc status and brv vc pull errors. status now catches a few staged-then-edited file states it used to hide. When a pull, checkout, or merge would overwrite local changes, the error lists the affected files instead of the generic "local changes would be overwritten" message. By @bao-byterover in #577
  • OpenAI-compatible providers fail loudly when the URL is wrong. First-time setup for Ollama, LM Studio, and similar providers now checks the base URL up front and shows the error inline. Bad URLs no longer pre-select a placeholder llama3 model or hang the REPL on disconnect / reconnect. By @RyanNg1403 in #549

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work without any migration.

🙏 Contributors

Thanks to @cuongdo-byterover, @bao-byterover, and @RyanNg1403 for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.10.0...v3.10.1

v3.10.0 Breaking risk
Security fixes
  • Patched high-severity advisory in postcss and other dependencies
Notable features
  • Connect OpenClaude as an agent
  • Faster first-run startup
  • Styled brv login confirmation page
Full changelog

This release adds OpenClaude as a connectable agent, polishes the brv login browser flow, and fixes a handful of reliability and billing rough edges, including a cold-start hang, a brv restart glitch under nested shell wrappers, and over-counting on multi-folder brv curate runs.

What's Changed

✨ Added

  • Connect OpenClaude as an agent. Run brv connectors install "OpenClaude", or pick it from /connectors in the REPL. By @DatPham-6996 in #548

🔄 Changed

  • Prettier brv login confirmation page. The browser tab shown after sign-in now matches the brv dark theme, with a styled error page if sign-in fails. By @cuongdo-byterover in #566
  • Faster, more reliable first-run startup. The first brv command after install or restart connects more consistently and no longer hangs when the sign-in provider is slow. By @bao-byterover in #546

🐛 Fixed

  • brv restart works inside nested shell wrappers. Previously, launching brv through several layers of wrapper scripts (a shell alias, an npm script, a CI runner) could leave the daemon stuck on restart. Fixed on macOS, Linux, and Windows. By @bao-byterover in #547
  • brv curate counts as one operation, not many. Curating multiple folders at once was being billed once per folder, which could push fresh free-tier accounts past their limit in a single run. Now grouped correctly. By @cuongdo-byterover in #571
  • Security update. Patched postcss and several other dependencies to address a high-severity advisory. By @bao-byterover in #570 and @ncnthien in #558, #572

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work without any migration.

🙏 Contributors

Thanks to @bao-byterover, @cuongdo-byterover, @DatPham-6996, and @ncnthien for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.9.0...v3.10.0

v3.9.0 Breaking risk
Notable features
  • brv vc diff command for viewing staged/unstaged changes and comparing branches/commits with --format json support and /vc diff in REPL
  • Configuration page in brv webui for git identity (user.name, user.email) and origin remote with one-click ByteRover account seed
  • Improved first-run tour with guided highlights and Try again action for failed tasks instead of auto-opening composer
Full changelog

This release rounds out the brv webui first-run experience and fills key gaps in brv vc. The new Configuration page lets you set up your git identity and remote in the browser, brv vc diff finally lets you see what changed in your context tree, and the guided tour now teaches by walking you through the dashboard instead of jumping ahead.

🌟 Highlights

⚙️ Configuration page in brv webui

A new Configuration page in the dashboard lets you set up the two things you used to need a terminal for: your git identity and your origin remote.

  • Git identity (user.name, user.email) for the context tree, with a one-click button that seeds both from your signed-in ByteRover account.
  • Origin remote for pushing your context tree, editable from the same screen.

A small status dot tells you at a glance whether identity is set: amber when it's missing, green once it's filled in. If a provider or remote action fails, the error toast deep-links straight back to the matching section so you don't have to hunt for it.

🔍 brv vc diff: see what changed in your context tree

brv vc diff shows you exactly what's changed since your last commit (both staged and unstaged work) and lets you compare any two branches or commits. It's also wired up as /vc diff in the REPL, and --format json makes it easy to feed into other tools.

It pairs naturally with brv vc status: status shows you which files moved, diff shows you what moved.

🎯 Click-through first-run tour

The first-run tour used to drop you straight into the task composer before you had context for what to type. Now it highlights the Tasks tab and the New task button with a glowing arrow, dims the rest of the page, and lets you click through at your own pace. If your first task fails, a Try again action prefills the composer so you can retry without retyping.

What's Changed

✨ Added

  • brv vc diff for staged / unstaged changes and branch / commit compare; /vc diff in the REPL; --format json. By @bao-byterover in #543
  • brv vc remote remove to delete a git remote from the CLI. By @bao-byterover in #542
  • Configuration page in brv webui for git identity and origin remote, with one-click ByteRover seed and a Delete button on remotes. By @wzlng in #545

🔄 Changed

  • First-run tour now highlights and walks you through the Tasks tab and "New task" button instead of auto-opening the composer. Failed tasks offer Try again with a prefilled composer. By @wzlng in #545
  • ByteRover pinned at the top of the provider picker with a "Native" badge; sign-in opens directly with no extra confirmation step. By @wzlng in #545

🐛 Fixed

  • Google default model updated to gemini-3-flash-preview (was gemini-3.1-flash-lite-preview). By @cuongdo-byterover in #553
  • brv dream no longer reorders frontmatter fields in synthesized notes, so brv vc diffs stop showing churn that wasn't a real edit. By @RyanNg1403 in #544

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place, then run brv restart to reload the daemon.

✅ No Breaking Changes

All changes are backward compatible. Existing context trees, provider configs, and connected agents continue to work without migration.

🙏 Contributors

Thanks to @bao-byterover, @wzlng, @cuongdo-byterover, and @RyanNg1403 for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.8.3...v3.9.0

v3.8.3 New feature
Notable features
  • Browser sign-in by default in brv login
  • Provider descriptions in picker
  • WebUI works with hidden installation folders
Full changelog

A small quality-of-life release. brv login now opens your browser by default, the provider picker tells you what each provider does, and brv webui works correctly when brv is installed under a hidden folder like ~/.nvm or ~/.asdf.

🌟 Highlights

🔐 Browser sign-in by default

Just run brv login and sign in in your browser. On CI or a remote shell, use brv login --api-key <key> instead. SSH and non-interactive shells are detected automatically and skip the browser, so the command never hangs waiting on a window that won't open.

The provider list also shows a short description for each provider in brv providers list and the web picker, so you can pick by what it does instead of guessing from the name.

🪟 brv webui works under hidden install folders

If brv lives under a hidden folder like ~/.nvm/... or ~/.asdf/..., refreshing a web UI page like /contexts used to return 404. Fixed.

What's Changed

  • brv login defaults to browser sign-in. Use --api-key for CI. By @wzlng in #533
  • Provider picker shows a short description for each provider. By @wzlng in #533
  • Fixed "Logged in as undefined" after sign-in when the server doesn't return your email. By @wzlng in #533
  • Fixed brv webui 404 on page reload when installed under hidden folders. By @wzlng in #528

🚀 Upgrade

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer, then brv restart.

🙏 Contributors

Thanks to @wzlng for shipping this release.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.8.2...v3.8.3

v3.8.2 Breaking risk

Web UI styling bug fixed in published CLI builds.

Full changelog

This release fixes a styling bug in brv webui. If you upgraded to v3.8.0 or v3.8.1 and the web UI looked broken, this release makes it look right again.

🌟 Highlights

🎨 Web UI styles now render correctly from the installed CLI

After installing with curl -fsSL https://byterover.dev/install.sh | sh, opening brv webui showed dialogs and side sheets unstyled: no backdrop, wrong position, missing borders. Still usable, but clearly broken.

v3.8.2 fixes this. The web UI now looks the same from the installed binary as it does in development. Only users on the published CLI were affected. Source and submodule builds were fine. (#513)

What's Changed

🐛 Fixed

  • Web UI styles missing in the published build. Tailwind was scanning the wrong folder for the shared UI package, so classes used by dialogs and sheets got stripped from the final CSS. Fixed by pointing Tailwind at the right path. By @wzlng in #513

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place.

After upgrading, run brv restart and reopen brv webui. No need to re-run brv connectors install.

✅ No Breaking Changes

All changes are backward compatible. No migration needed.

🙏 Contributors

Thanks to @wzlng for the fix.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.8.1...v3.8.2

v3.8.1 Maintenance

Maintenance rebuild with corrected release pipeline configuration.

Full changelog

This release is a maintenance rebuild of v3.8.0 - no code or behavior changes. v3.8.1 reships the v3.8.0 feature set with our refreshed release pipeline configuration so the distributed binary is built against the correct settings.

Why 3.8.1?

v3.8.0 was packaged before our release pipeline configuration was fully updated, so the published binary shipped with stale build settings. v3.8.1 is a clean rebuild from the same source with the correct configuration baked in.

If you installed v3.8.0, please upgrade to v3.8.1. New users can install v3.8.1 directly and get the full v3.8.0 feature set - see the v3.8.0 release notes for what's included.

Upgrade

curl -fsSL https://byterover.dev/install.sh | sh

After upgrading, run brv restart to reload the daemon.

What's Changed

📚 Docs & Chores

  • Rebuild of v3.8.0 with refreshed release pipeline configuration - by @bao-byterover

After upgrading, run brv restart to reload the daemon.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.8.0...v3.8.1

v3.8.0 Breaking risk
Security fixes
  • Patched high-severity npm advisory in @hono/node-server and hono
Notable features
  • brv webui: browser dashboard for browsing memory, reviewing changes, running curate and query
  • Guided first-run setup tour for new users
  • Connected agents now wait for brv curate completion by default
Full changelog

This release brings ByteRover to the browser. Run brv webui to open a local dashboard where you can browse your project's memory, review changes, run curate and query, and manage providers without leaving the tab. Connected agents (Claude Code, Cursor, Codex, Copilot) also get smarter this release: brv curate now waits for its work to finish by default, so follow-up questions see the data that was just saved.

🌟 Highlights

🌐 brv webui: a browser dashboard for ByteRover

Run brv webui to open a local dashboard at http://localhost:7700. From the browser you can:

  • Browse and edit your context tree (the notes and memory ByteRover builds for your project)
  • Review and commit pending changes with full brv vc integration
  • Run curate and query directly from the browser
  • Manage LLM providers and connected agents
  • Switch between projects without restarting

The dashboard still loads when the daemon isn't running, with a clear recovery screen. Use --port <n> to pick a different port, and your choice is remembered across runs. (#465)

🎓 Guided first-run tour

If you're new, the web UI walks you through setting up a provider, running your first curate and query, and connecting an agent. Skipped it? "Restart the tour" lives in the Help menu. (#465)

🤝 Connected agents now wait for brv curate by default

The skill template installed by brv connectors install now tells Claude Code, Cursor, Codex, Copilot, and other connected agents to let brv curate finish before moving on, so follow-up queries see the new data. Agents only fire-and-forget (--detach) when you explicitly ask.

Action required: re-run brv connectors install <agent> for each connected agent to pick up the new guidance. (#479)

What's Changed

✨ Added

  • brv webui: browser dashboard over your project memory, version control, providers, agents, and project switcher. Loads even when the daemon is offline, persists a custom --port across runs. By @ncnthien in #465
  • Guided first-run tour in the web UI. Walks new users through provider setup, first curate, first query, and agent connection. Restartable from the Help menu. By @ncnthien in #465

🔄 Changed

  • Connected agents now wait for brv curate by default. The installed skill template blocks on curate completion unless you explicitly opt into --detach. Re-run brv connectors install <agent> to update. By @bao-byterover in #479
  • OpenAI OAuth default model is now gpt-5.4-mini for better non-code curate quality. Existing configurations are preserved; the new default only applies to new sign-ins. By @bao-byterover in #496
  • MiniMax default model is now MiniMax-M2.7. By @zeki893 in #488
  • Complete frontmatter on context files. Markdown files written by brv curate and brv dream now always include all seven semantic fields: title, summary, tags, related, keywords, createdAt, updatedAt. Older files without them still load fine, so no migration is needed. By @RyanNg1403 in #468

🐛 Fixed

  • ByteRover OAuth login now resumes provider setup. Picking ByteRover while signed out used to bounce you back to the provider list after login; it now continues the setup automatically. By @AmElmo in #466
  • No more "Connecting to ByteRover…" hang after a fresh login. Provider connect sees new credentials immediately instead of waiting up to 5 seconds for a cache refresh. By @cuongdo-byterover in #493

🛡️ Security

  • Patched high-severity npm advisory in @hono/node-server and hono. By @bao-byterover in #507

🚀 Upgrade & Install

Fresh install (macOS / Linux):

curl -fsSL https://byterover.dev/install.sh | sh

Existing users: re-run the installer above to upgrade in place.

After upgrading, run brv restart to reload the daemon. If you have connected agents, refresh each one to pick up the new curate-blocking behavior:

brv connectors install <agent>   # claude-code, cursor, codex, copilot, ...

✅ No Breaking Changes

All changes are backward compatible. Older context trees load without migration; provider configuration is preserved across the upgrade.

🙏 Contributors

Thanks to everyone who shipped this release: @ncnthien, @AmElmo, @RyanNg1403, @zeki893, @cuongdo-byterover, and @bao-byterover.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.7.1...v3.8.0

v3.7.1 Mixed
Notable features
  • Agent skill template updated with query and curate history section for connected agents
  • Extended .gitignore excludes macOS, Windows, Linux system files and editor swap/backup patterns
Full changelog

This patch release cleans up brv vc noise: runtime ranking data no longer churns your tracked notes, and OS / editor temp files are now ignored by default. It also refreshes the agent skill template so connected coding agents know where to look up your past queries and curates.

🌟 Highlights

🧹 brv vc status stays clean after queries and curates

Until now, every brv search, brv query, or agent curate quietly updated ranking data (things like how often a note was accessed and how recent it is) inside the markdown files themselves. That meant brv vc status was always full of churn that didn't reflect anything you actually wrote.

v3.7.1 moves all of that ranking data into a separate per-project file kept outside your tracked notes. Your markdown now only holds the things you actually edit (title, tags, summary, related links, and the body), and your version control stays quiet between real edits.

While we were in the area, brv dream synthesize also stopped writing maturity: draft into the top of new synthesis files. That field now seeds the sidecar too, so freshly generated summaries land clean.

No action needed. Older context trees with ranking fields still living in the markdown will continue to load. Leftover fields are simply ignored on read, so nothing breaks and no migration is required.

🤖 Connected agents now know about your query and curate history

Coding agents that connect to ByteRover via brv connectors install (Claude Code, Cursor, Codex, Copilot, and others) get an updated skill file with a dedicated new section for history and recall metrics. When an agent is debugging a knowledge gap, it now reaches for brv query-log view, brv query-log summary, and brv curate view (including the resolution-tier breakdown and time / status filters) instead of guessing.

To pick this up on an existing connector, re-run:

brv connectors install <agent>

🙈 OS and editor temp files no longer clutter brv vc status

The context-tree .gitignore now excludes the usual operating-system and editor noise:

  • macOS: .DS_Store, ._*
  • Windows: Thumbs.db, ehthumbs.db, Desktop.ini
  • Linux: .directory, .fuse_hidden*, .nfs*
  • Editors: *.swp, *.swo, *~, .#*, *.bak, *.tmp

Patterns auto-sync into existing projects on the next brv vc command, so no manual .gitignore edit is needed.

What's Changed

🐛 Fixes

  • Runtime signals sidecar: move access / recency / maturity ranking out of markdown frontmatter into a per-project sidecar so brv vc status stays clean - by @danhdoan in #447, #448, #449, #450, #452, #453, #455, #456, #457
  • Synthesis files no longer leak maturity: draft into frontmatter: brv dream synthesize now seeds the sidecar instead - by @RyanNg1403 in #458
  • Extend context-tree .gitignore with macOS / Windows / Linux system files and editor swap / backup / temp patterns - by @bao-byterover in #463

✨ Improvements

  • Agent skill template, dedicated section for query and curate history: connectors now teach agents about brv query-log view, brv query-log summary, brv curate view, the resolution-tier taxonomy, and time / status filters - by @DatPham-6996 in #445

📚 Docs & Chores

  • Update CHANGELOG.md and bump version to 3.7.1 - by @bao-byterover

🙏 Contributors

Thanks to @danhdoan, @RyanNg1403, @DatPham-6996, and @bao-byterover for shipping this release.

After upgrading, run brv restart to reload the daemon.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.7.0...v3.7.1

v3.7.0 Security relevant
Security fixes
  • Patched high-severity npm advisory via basic-ftp and hono upgrades
Notable features
  • Added darwin-x64 (Intel Mac) native installer support
Full changelog

This release adds Intel Mac support to the native installer so ByteRover CLI installs out of the box on x86_64 Macs, and patches a high-severity npm advisory in our transitive dependencies.

🌟 Highlights

🍎 Intel Mac (darwin-x64) install support

Until now, running our one-line installer on an Intel Mac stopped with an "Apple Silicon only" error. v3.7.0 publishes a darwin-x64 tarball alongside the existing builds, so the same command now works everywhere:

curl -fsSL https://byterover.dev/install.sh | sh

Nothing changes for users already on Apple Silicon, Linux x64, or Linux ARM64 - their install path is unchanged.

🔒 Security dependency update

Bumped basic-ftp and hono to clear a high-severity advisory flagged by npm audit. No action needed beyond upgrading -behavior is identical.

What's Changed

✨ Features

  • Add darwin-x64 (Intel Mac) tarball build target and enable it in the installer - by @leehpham in #440

🔒 Security

  • Patch high-severity npm advisory by bumping basic-ftp and hono - by @bao-byterover in #443

📚 Docs & Chores

  • Update CHANGELOG.md and bump version to 3.7.0 - by @bao-byterover

Supported platforms

macOS ARM64, macOS x64 (Intel), Linux x64, Linux ARM64.

After upgrading, run brv restart to reload the daemon.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.6.1...v3.7.0

v3.6.1 Maintenance

Minor fixes and improvements.

Full changelog

This release is a maintenance rebuild of v3.6.0 - no code or behavior changes. v3.6.1 reships the v3.6.0 feature set with our refreshed release pipeline configuration so the distributed binary is built against the correct settings.

Why 3.6.1?

v3.6.0 was packaged before our release pipeline configuration was fully updated, so the published binary shipped with stale build settings. v3.6.1 is a clean rebuild from the same source with the correct configuration baked in.

If you installed v3.6.0, please upgrade to v3.6.1. New users can install v3.6.1 directly and get the full v3.6.0 feature set - see the v3.6.0 release notes for what's included.

Upgrade

curl -fsSL https://byterover.dev/install.sh | sh

After upgrading, run brv restart to reload the daemon.

What's Changed

📚 Docs & Chores

  • Rebuild of v3.6.0 with refreshed release pipeline configuration - by @bao-byterover
  • Add AGENTS.md to document Codex integration for contributors - by @leehpham

After upgrading, run brv restart to reload the daemon.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.6.0...v3.6.1

v3.6.0 New feature
Notable features
  • brv dream — background context-tree cleanup with merge, summarize, and archive passes; idle-triggered with --undo support
  • brv query-log view — query history viewer with filtering (status, tier, since, before, limit) and detail mode
  • brv query-log summary — aggregated metrics including coverage, cache hit rate, and top topics in multiple formats
Full changelog

This release introduces brv dream — an idle-time cleanup that keeps your context tree tidy — and brv query-log, so you can finally see what you've asked and how well it was answered.

🌟 Highlights

🌙 brv dream — tidy up your context tree while you're away

Over time, your context tree collects duplicates, stale drafts, and cross-topic connections that never quite got written down. brv dream cleans it up in the background so you don't have to.

When it runs, it does three things:

  • Merges notes that say the same thing.
  • Writes short summaries that connect ideas across topics.
  • Archives stale entries that haven't been useful.

It runs on its own when the CLI has been idle for a while, or whenever you run brv dream yourself.

Safe by default. Anything the model isn't sure about is held for you to review with brv review pending before it takes effect. If you don't like what a run did, brv dream --undo reverts the last one.

Flags: --force / -f (skip the time and activity gates), --detach (queue and exit without waiting), --undo, --timeout <seconds>, --format json.

📊 brv query-log — see what you've asked before

Every brv query is now saved locally, so you can look back at past questions and how they were answered — no extra setup, nothing leaves your machine.

Two subcommands do the work:

  • brv query-log view — lists recent queries, with filters --status, --tier, --since, --before, --limit, plus --detail to also show the matched docs for each entry, and --format json for scripting.
  • brv query-log summary — aggregated metrics (coverage, cache hit rate, top topics) over a window you set with --last, --since, or --before. Pick the shape you want with --format text, json, or narrative — the last one reads like a plain-English recap, great for a daily review.

Nothing changes for your existing brv query workflow — logs are written automatically.

What's Changed

✨ Features

  • brv dream — background context-tree cleanup with merge, summarize, and archive passes; idle-time auto-trigger; brv review pending integration; and --undo / --detach support — by @RyanNg1403 and @danhdoan in #436
  • brv query-log view and brv query-log summary — query history viewer and aggregate recall-metrics summary — by @bao-byterover in #375

📚 Docs & Chores

  • Consolidate IAM / Cogit / LLM base-URL env vars into BRV_IAM_BASE_URL, BRV_COGIT_BASE_URL, and BRV_LLM_BASE_URL (developer-only, no user impact) — by @hieuntg81 in #397
  • Update CHANGELOG.md and bump version to 3.6.0 — by @bao-byterover

🙏 Contributors

Thanks to everyone who shipped this release: @RyanNg1403, @danhdoan, @bao-byterover, and @hieuntg81.

After upgrading, run brv restart to reload the daemon.

Full Changelog: https://github.com/campfirein/byterover-cli/compare/v3.5.1...v3.6.0

v3.5.1 New feature
Notable features
  • Improved `brv-curate` and `brv-query` tool descriptions to clarify project path requirements by environment
v3.5.0 Mixed
Security fixes
  • High-severity npm advisory in basic-ftp dependency
Notable features
  • Claude Desktop connector with MCP support on macOS and Windows
  • Bundled Node.js isolated to prevent PATH shadowing
v3.4.0 Security relevant
Security fixes
  • Critical axios vulnerability fixed by pinning to 1.15.0
Notable features
  • `brv swarm` unified search across Obsidian, markdown, GBrain, OpenClaw, and ByteRover context tree
  • `brv swarm query --explain` flag showing which tools were queried and why
  • `brv swarm curate` with automatic provider selection and ByteRover fallback
v3.3.0 New feature
Notable features
  • brv search BM25 command for zero-cost knowledge retrieval
  • --timeout flag for brv curate and query (300-3600 seconds)
  • Cleaner legacy-sync experience with deprecation notices
v3.2.0 New feature
Notable features
  • Git-style worktree links with pointer files
  • Cross-project knowledge sources with read-only access
  • Resolver-aware brv status with linked worktree detection
v3.1.0 New feature
Notable features
  • Adaptive knowledge scoring with hierarchical propagation
  • Knowledge abstracts auto-generation to reduce context consumption
  • Session-learning extracting patterns from REPL usage

Beta — feedback welcome: [email protected]