What makes byterover-test notable?

1.1K downloads. Trust evidence available

How should byterover-test be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

byterover-test

Queries and curates knowledge in ByteRover context tree. Use when user asks to remember information, add context, search patterns, query implementations, or manage project knowledge. Triggers on phrases like "remember this", "add to context", "how does X work", "what are the patterns", "store this", "save this knowledge", "curate", "brv query", "check context tree". Skill: byterover-test Owner: RyanNg1403 Summary: Queries and curates knowledge in ByteRover context tree. Use when user asks to remember information, add context, search patterns, query implementations, or manage project knowledge. Triggers on phrases like "remember this", "add to context", "how does X work", "what are the patterns", "store this", "save this knowledge", "curate", "brv query", "check context tree". Ta

OpenClaw

View on ClawHub

Rank

Safety

Downloads

1.1k

Updated

Apr 15, 2026

Version

1.2.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 4/15/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Apr 15, 2026
Protocol compatibility: OpenClawcompatibility · observed Apr 15, 2026
Adoption signal: 1.1K downloadsadoption · observed Apr 15, 2026
Latest release: 1.2.1release · observed Jan 27, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install kn78m6bsbgwt197d802754qhbn7zzcfw:byterover-test

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-ryanng1403-byterover-test/snapshot"

Documentation

CLAWHUB

16,899 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: byterover
description: Queries and curates knowledge in ByteRover context tree. Use when user asks to remember information, add context, search patterns, query implementations, or manage project knowledge. Triggers on phrases like "remember this", "add to context", "how does X work", "what are the patterns", "store this", "save this knowledge", "curate", "brv query", "check context tree".
---

# ByteRover Context Tree

A project-level knowledge repository that persists across sessions. Use it to avoid re-discovering patterns, conventions, and decisions.

## Why Use ByteRover

- **Query before working**: Get existing knowledge about patterns, conventions, and past decisions before implementing
- **Curate after learning**: Capture insights, decisions, and bug fixes so future sessions start informed

## Quick Reference

| Command | When | Example |
|---------|------|---------|
| `brv query "question"` | Before starting work | `brv query "How is auth implemented?"` |
| `brv curate "context" -f file` | After completing work | `brv curate "JWT 24h expiry" -f auth.ts` |
| `brv status` | To check prerequisites | `brv status` |

## When to Use

**Query** when you need to understand something:
- "How does X work in this codebase?"
- "What patterns exist for Y?"
- "Are there conventions for Z?"

**Curate** when you learned or created something valuable:
- Implemented a feature using specific patterns
- Fixed a bug and found root cause
- Made an architecture decision

## Curate Quality

Context must be **specific** and **actionable**:

```bash
# Good - specific, explains where and why
brv curate "Auth uses JWT 24h expiry, tokens in httpOnly cookies" -f src/auth.ts

# Bad - too vague
brv curate "Fixed auth"
```

**Note:** Context argument must come before `-f` flags. Max 5 files.

## Best Practices

1. **Break down large contexts** - Run multiple `brv curate` commands for complex topics rather than one massive context. Smaller chunks are easier to retrieve and update.

2. **Let ByteRover read files** - Don't read files yourself before curating. Use `-f` flags to let ByteRover read them directly:
```bash
# Good - ByteRover reads the files
brv curate "Auth implementation details" -f src/auth.ts -f src/middleware/jwt.ts

# Wasteful - reading files twice
# [agent reads files] then brv curate "..." -f same-files
```

3. **Be specific in queries** - Queries block your workflow. Use precise questions to get faster, more relevant results:
```bash
# Good - specific
brv query "What validation library is used for API request schemas?"

# Bad - vague, slow
brv query "How is validation done?"
```

4. **Signal outdated context** - When curating updates that replace existing knowledge, explicitly tell ByteRover to clean up:
```bash
brv curate "OUTDATED: Previous auth used sessions. NEW: Now uses JWT with refresh tokens. Clean up old session-based auth context." -f src/auth.ts
```

5. **Specify structure expectations** -

_meta.json

{
  "ownerId": "kn78m6bsbgwt197d802754qhbn7zzcfw",
  "slug": "byterover-test",
  "version": "1.2.1",
  "publishedAt": 1769486222999
}

TROUBLESHOOTING.md

# ByteRover Troubleshooting

## Quick Diagnosis

```bash
brv status
```

## User Action Required

These errors require user intervention (agent cannot fix):

| Error | User Action |
|-------|-------------|
| "No ByteRover instance is running" | Start `brv` in separate terminal |
| "Not authenticated" | Run `/login` in brv REPL |
| "Project not initialized" | Run `/init` in brv REPL |
| "Connection failed" | Restart `brv` (Ctrl+C, then `brv`) |

**Template response:**
> Please [action] in your brv terminal, then I'll retry the command.

## Agent-Fixable Errors

| Error | Fix |
|-------|-----|
| "Context argument required" | Add text before `-f`: `brv curate "text" -f file` |
| "Maximum 5 files allowed" | Reduce to 5 or fewer `-f` flags |
| "File not found" | Verify path with `ls`, use relative paths from project root |
| "No relevant context found" | Try different query phrasing, or curate knowledge first |

## Architecture

ByteRover uses client-server architecture:
- User runs `brv` to start server (interactive REPL)
- Agent commands (`query`, `curate`, `status`) connect to server
- Server must be running for commands to work

## Exit Codes

| Code | Meaning |
|------|---------|
| 0 | Success |
| 1 | General error |
| 2 | Connection error |

## Getting Help

- Email: [email protected]
- Discord: https://discord.com/invite/UMRrpNjh5W

WORKFLOWS.md

# ByteRover Workflows

## Pattern 1: Research Before Implementation

Use when starting new features or working in unfamiliar areas.

**Workflow:**
```
Query existing knowledge → Implement following patterns → Curate new decisions
```

**Example: Adding a new API endpoint**

```bash
# 1. Query for existing patterns
# Be SPECIFIC to get faster, more relevant results
brv query "What middleware chain is used for authenticated API endpoints?"
brv query "What is the standard error response format for API routes?"

# 2. Implement following discovered patterns
# ... write code ...

# 3. Curate decisions made
# Don't read the file first - let ByteRover read it via -f flag
brv curate "Added /api/users/profile endpoint. Uses authMiddleware for JWT validation, returns UserProfileDTO. Error handling follows ApiError pattern" -f src/api/routes/users.ts
```

**Example: Implementing a new React component**

```bash
# 1. Query patterns - specific questions save time
brv query "What data fetching hook pattern is used in list components?"
brv query "Are CSS modules or styled-components used for component styling?"

# 2. Implement
# ... write component ...

# 3. Curate with file reference - ByteRover reads the file
brv curate "Created UserAvatar component. Uses React Query for data fetching, CSS modules for styling. Follows existing pattern in src/components/common/" -f src/components/UserAvatar.tsx
```

## Pattern 2: Debug and Document

Use when fixing bugs to capture learnings and prevent recurrence.

**Workflow:**
```
Query known issues → Debug and fix → Curate root cause and solution
```

**Example: Fixing a race condition**

```bash
# 1. Query for context - be specific about the symptom
brv query "Are there known race condition patterns or AbortController usage in data fetching hooks?"

# 2. Debug and fix
# ... investigate, find root cause, implement fix ...

# 3. Curate the learning with structured format
brv curate "Bug: stale data after rapid navigation. Cause: useEffect cleanup not cancelling requests. Fix: AbortController with cleanup. Pattern: always abort fetch in useEffect cleanup" -f src/hooks/useUserData.ts
```

**Example: Fixing an authentication issue**

```bash
# 1. Specific query about the problem area
brv query "How are credentials and cookies configured in the API client fetch calls?"

# 2. Fix
# ... debug and fix ...

# 3. Curate with emphasis on the gotcha
brv curate "Bug: unexpected logouts. Cause: fetch missing credentials option. Fix: added 'credentials: include' to fetch config. IMPORTANT: all API calls must include credentials for cookie-based auth" -f src/lib/api-client.ts
```

## Pattern 3: Multi-File Changes

Use when changes span multiple files to maintain context.

**Example: Adding a new feature across layers**

```bash
# 1. Query architecture - specific about the layers
brv query "How are full-stack features organized across API routes, service layer, and React components?"

# 2. Implement across files
# ... write code ...

# 3. Cu

Github ReposUpdated 5h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.