byterover by junsuzuki1973/openclaw-skill-byterover
npx skills add https://github.com/junsuzuki1973/openclaw-skill-byterover --skill byteroverByteRover 是一个上下文工程平台,可让您为编码智能体整理上下文——包括模式、决策和学习成果。它能自动同步团队成员间的上下文,并消除手动管理 Markdown 文件的需求。
API 凭证存储在 ~/.clawdbot/byterover-config.json 中:
{
"apiKey": "your_byterover_api_key_here",
"team": "your_team_name",
"space": "your_space_name"
}
ByteRover CLI 需要 Node.js 20+ 和 libsecret 来存储凭证。此技能使用 Docker 来提供一个包含所有依赖项的隔离环境。
cd ~/.openclaw/workspace/skills/byterover
docker-compose up -d
使用 API 密钥登录:
docker-compose exec byterover brv login --api-key $BRV_API_KEY
初始化项目:
docker-compose exec byterover brv init --headless --team "$BRV_TEAM" --space "$BRV_SPACE"
ByteRover is a context engineering platform that lets you curate context for your coding agents—patterns, decisions, and learnings. It automatically syncs context across team members and eliminates manual markdown file management.
API credentials are stored in ~/.clawdbot/byterover-config.json:
{
"apiKey": "your_byterover_api_key_here",
"team": "your_team_name",
"space": "your_space_name"
}
ByteRover CLI requires Node.js 20+ and libsecret for credential storage. This skill uses Docker to provide an isolated environment with all dependencies.
cd ~/.openclaw/workspace/skills/byterover
docker-compose up -d
Login with API Key:
docker-compose exec byterover brv login --api-key $BRV_API_KEY
Initialize Project:
docker-compose exec byterover brv init --headless --team "$BRV_TEAM" --space "$BRV_SPACE"
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
docker-compose exec byterover brv status --headless --format json
查询上下文:
docker-compose exec byterover brv query "What are the testing strategies?" --headless --format json
整理上下文:
docker-compose exec byterover brv curate "Make sure to document API authentication patterns" --headless --format json
推送更改:
docker-compose exec byterover brv push --headless --format json
拉取更改:
docker-compose exec byterover brv pull --headless --format json
ByteRover CLI 支持无头模式以用于自动化和脚本编写。无头模式禁用交互式提示,并支持机器可读的 JSON 输出。
--headless 的命令brv init (需要 --team 和 --space)brv statusbrv querybrv curatebrv push (自动跳过确认)brv pull使用 --format 控制输出:
text (默认):人类可读的文本输出json:用于机器解析的 NDJSON (换行分隔的 JSON)对于无头环境,使用 API 密钥代替 OAuth 浏览器流程:
brv login --api-key $BRV_API_KEY
上下文树 是 ByteRover 的结构化知识系统,它将项目上下文组织到各个领域:
提示您的编码智能体:
使用 brv query 命令检查此项目中使用了哪些认证模式
智能体将执行:
brv query "What authentication patterns are used?" --headless --format json
检查项目状态:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv status
从终端添加上下文:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv curate "Document the API rate limiting strategy"
查询特定知识:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv query "How do we handle rate limiting?"
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/status.sh
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv status --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/query.sh
QUERY="${1:-project overview}"
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv query "$QUERY" --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/curate.sh
CONTEXT="${1}"
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv curate "$CONTEXT" --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/sync.sh
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
echo "Pulling latest context..."
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv pull --headless --format json
echo "Pushing local changes..."
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv push --headless --format json
构建镜像:
cd ~/.openclaw/workspace/skills/byterover
docker-compose build
启动容器:
docker-compose up -d
停止容器:
docker-compose down
查看日志:
docker-compose logs -f
进入容器 shell:
docker-compose exec byterover bash
ByteRover 提供多种集成方法:
现代、可发现的技能文件,智能体可以自动检查和执行。
用于广泛智能体兼容性的模型上下文协议工具。
为旧版集成生成的规则文件。
NDJSON 格式,包含消息类型:
log:进度消息output:主要输出内容error:错误消息warning:警告消息result:最终操作结果BRV_API_KEY - ByteRover API 密钥BRV_TEAM - 团队名称BRV_SPACE - 空间名称BRV_HEADLESS - 启用无头模式 (true)BRV_FORMAT - 输出格式 (json/text)构建失败:
登录失败:
容器退出:
docker-compose logs查询无结果:
brv init 初始化项目brv curate 添加上下文brv pull 同步MIT
由 Jun Suzuki 为 OpenClaw 创建
有关 ByteRover 的更多信息,请访问:https://docs.byterover.dev/
每周安装数
135
代码仓库
首次出现
2026年2月15日
安全审计
安装于
gemini-cli132
github-copilot130
opencode130
codex129
openclaw129
cursor129
Check Status:
docker-compose exec byterover brv status --headless --format json
Query Context:
docker-compose exec byterover brv query "What are the testing strategies?" --headless --format json
Curate Context:
docker-compose exec byterover brv curate "Make sure to document API authentication patterns" --headless --format json
Push Changes:
docker-compose exec byterover brv push --headless --format json
Pull Changes:
docker-compose exec byterover brv pull --headless --format json
ByteRover CLI supports headless mode for automation and scripting. Headless mode disables interactive prompts and supports machine-readable JSON output.
brv init (requires --team and --space)brv statusbrv querybrv curatebrv push (auto-skips confirmation)brv pullUse --format to control output:
text (default): Human-readable text outputjson: NDJSON (newline-delimited JSON) for machine parsingInstead of OAuth browser flow, use API key for headless environments:
brv login --api-key $BRV_API_KEY
The Context Tree is ByteRover's structured knowledge system that organizes project context into domains:
Prompt your coding agent:
Use brv query command to check what authentication patterns are used in this project
Agent will execute:
brv query "What authentication patterns are used?" --headless --format json
Check project status:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv status
Add context from terminal:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv curate "Document the API rate limiting strategy"
Query specific knowledge:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv query "How do we handle rate limiting?"
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/status.sh
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv status --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/query.sh
QUERY="${1:-project overview}"
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv query "$QUERY" --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/curate.sh
CONTEXT="${1}"
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv curate "$CONTEXT" --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/sync.sh
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
echo "Pulling latest context..."
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv pull --headless --format json
echo "Pushing local changes..."
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv push --headless --format json
Build image:
cd ~/.openclaw/workspace/skills/byterover
docker-compose build
Start container:
docker-compose up -d
Stop container:
docker-compose down
View logs:
docker-compose logs -f
Enter container shell:
docker-compose exec byterover bash
ByteRover provides multiple integration methods:
Modern, discoverable skill files that agents can inspect and execute automatically.
Model Context Protocol tools for broad agent compatibility.
Generated rule files for older integrations.
NDJSON format with message types:
log: Progress messagesoutput: Main output contenterror: Error messageswarning: Warning messagesresult: Final operation resultBRV_API_KEY - ByteRover API keyBRV_TEAM - Team nameBRV_SPACE - Space nameBRV_HEADLESS - Enable headless mode (true)BRV_FORMAT - Output format (json/text)Build fails:
Login fails:
Container exits:
docker-compose logsQuery returns no results:
brv initbrv curatebrv pullMIT
Created for OpenClaw by Jun Suzuki
For more information about ByteRover, visit: https://docs.byterover.dev/
Weekly Installs
135
Repository
First Seen
Feb 15, 2026
Security Audits
Installed on
gemini-cli132
github-copilot130
opencode130
codex129
openclaw129
cursor129
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
36,300 周安装