hermes-agent/plugins/memory/byterover
alt-glitch e1067dbbe5 tests: pin ink engine in _make_tui_argv npm-bootstrap tests (post-merge semantic fix)
Main's rewritten test_tui_npm_install.py tests call _make_tui_argv expecting
the Ink/npm flow unconditionally; with the dual-engine dispatch merged in,
_resolve_tui_engine() auto-selects opentui whenever ui-opentui/dist is built
in the repo, routing the call away from the path under test (first subprocess
became 'node --version' instead of 'npm run build'). Pin the engine to ink
via an autouse fixture, mirroring the existing pinning precedent in
test_tui_resume_flow.py.
2026-06-12 10:32:40 +05:30
..
__init__.py tests: pin ink engine in _make_tui_argv npm-bootstrap tests (post-merge semantic fix) 2026-06-12 10:32:40 +05:30
plugin.yaml feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623) 2026-04-02 15:33:51 -07:00
README.md feat(memory): pluggable memory provider interface with profile isolation, review fixes, and honcho CLI restoration (#4623) 2026-04-02 15:33:51 -07:00

ByteRover Memory Provider

Persistent memory via the brv CLI — hierarchical knowledge tree with tiered retrieval (fuzzy text → LLM-driven search).

Requirements

Install the ByteRover CLI:

curl -fsSL https://byterover.dev/install.sh | sh
# or
npm install -g byterover-cli

Setup

hermes memory setup    # select "byterover"

Or manually:

hermes config set memory.provider byterover
# Optional cloud sync:
echo "BRV_API_KEY=your-key" >> ~/.hermes/.env

Config

Env Var Required Description
BRV_API_KEY No Cloud sync key (optional, local-first by default)

Working directory: $HERMES_HOME/byterover/ (profile-scoped).

Tools

Tool Description
brv_query Search the knowledge tree
brv_curate Store facts, decisions, patterns
brv_status CLI version, tree stats, sync state