ByteRover CLI 3.8.3

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: v3.8.2...v3.8.3

ByteRover CLI 3.8.2

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: v3.8.1...v3.8.2

ByteRover CLI 3.8.1

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: v3.8.0...v3.8.1

ByteRover CLI 3.8.0

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: v3.7.1...v3.8.0

ByteRover CLI 3.7.1

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: v3.7.0...v3.7.1

ByteRover CLI 3.7.0

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: v3.6.1...v3.7.0

ByteRover CLI 3.6.1

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: v3.6.0...v3.6.1

ByteRover CLI 3.6.0

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: v3.5.1...v3.6.0

ByteRover CLI 3.5.1

A small patch that improves how ByteRover's MCP tools communicate with coding agents.

🌟 Highlights

🔧 Smarter MCP tool descriptions

The cwd parameter on brv-curate and brv-query MCP tools now clearly tells the calling agent when a project path is required (Claude Desktop, hosted MCP) vs. optional (Cursor, Cline, Zed, Claude Code). This reduces failed tool calls from agents that previously omitted or guessed the path.

No action needed on your side — just upgrade and brv restart.

What's Changed

✨ Features

• Improve MCP tool descriptions so coding agents reliably pass the project path — by @bao-byterover in #423

📚 Docs & Chores

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

🙏 Contributors

Thanks to @bao-byterover for shipping this patch.

Full Changelog: v3.5.0...v3.5.1

ByteRover CLI 3.5.0

This release adds Claude Desktop as a first-class connector, cleans up how the installer handles its bundled Node.js, and patches a security advisory.

🌟 Highlights

🖥 Claude Desktop — connect ByteRover to the Claude Desktop app

If you use the Claude Desktop app, you can now plug ByteRover into it so Claude can search and save into your context tree directly — the same memory you already use from brv.

One command to set it up:

• brv connectors install "Claude Desktop" — or pick Claude Desktop from /connectors inside the REPL.

Works on macOS and Windows (including Microsoft Store / MSIX installs) — the two platforms Anthropic ships Claude Desktop for. After installing, fully quit Claude Desktop from the tray or menu bar and reopen it — a window-level restart isn't enough for it to pick up the new connector.

📦 Cleaner installer layout

Previously, install.sh placed its bundled Node.js in the same directory it added to your PATH, which could silently shadow the node on your system — breaking nvm, project-pinned Node versions, and anything else that resolves node through PATH.

Now the bundled Node lives in lib/ and only the brv symlink sits in bin/, so your system node is untouched. Just reinstall to pick up the new layout — no config changes needed.

🛡 Security update

Updated basic-ftp to close a high-severity npm advisory. Upgrade recommended.

What's Changed

✨ Features

• Claude Desktop connector with MCP support and auto-mode on macOS and Windows (including MSIX / Microsoft Store) — by @bao-byterover in #406
• Isolate bundled Node.js so install.sh no longer shadows the system node on PATH — by @bao-byterover in #413

🐛 Fixes

• Patch high-severity basic-ftp advisory — by @bao-byterover in #417
• Strip ANSI codes in query-renderer test assertions — by @cuongdo-byterover in #411

📚 Docs & Chores

• Update CHANGELOG.md and CLAUDE.md for the 3.5.0 release — by @bao-byterover

🙏 Contributors

Thanks to everyone who shipped this release: @bao-byterover and @cuongdo-byterover.

After upgrading, run brv restart to reload the daemon.

Full Changelog: v3.4.0...v3.5.0