Harbor vs ByteRover

ByteRover keeps what your agents save. Harbor learns what your team decided.

ByteRover is memory that you and your agents curate, kept as files you own and shared by space. Harbor learns from where the team already decides, in Slack threads, PR reviews and docs, and serves the rules that apply. ByteRover covers more agents and runs locally. Harbor captures from other people's work, counts what was used and blocks risky commands.

Harbor is in early access, and we let teams in by hand. Every line about ByteRover is from its own pages, read on 1 October 2026.

Why teams pick Harbor

Decide what gets in. See what gets used.

Three things Harbor does for the team behind the agents, each beside what ByteRover's own pages say about the same job.

You set the gate

Manual, Hybrid or Auto. Whatever you pick, a contradiction waits for a person.

In ByteRoverSpaces set who can read and write, from owner to viewer. Through its company brain plugin, what an agent learns is a proposal that stays pending until someone reviews it.

You see what got used

Every rule shows how often it was served and how often an answer cited it.

In ByteRoverEach recall shows the sources it came from.

You block a risky command

Block rules refuse it before it runs, in Claude Code, Cursor and Codex.

In ByteRoverNot part of the product.

Side by side

Harbor and ByteRover, row by row.

HarborByteRover
What it isA company brain for a team's coding agents. It learns the rules your team decides and serves the ones that apply to each session.Shared memory for coding agents: a desktop app, a CLI and agent skills that save decisions, fixes and rules as context files and share them across agents and teammates.
Where the knowledge comes fromSlack, GitHub, GitLab, Notion, Confluence, Jira, Linear, Google Drive and Granola, plus what agent sessions record.What you and your agents choose to save during sessions.
Who decides what gets inYou set the gate. Manual holds everything for a person, Hybrid adds routine rules and holds the important ones, Auto adds everything else. A contradiction always waits for a person.Spaces set who can read and write, from owner to viewer. Through its company brain plugin, what an agent learns is a proposal that stays pending until someone reviews it.
How it reaches the agentHooks add the rules that apply to the session before the agent writes a line. The same rules are on an MCP server, the CLI and /harbor in Slack.Agents query memory through its skills, and each recall comes with links to its sources.
When a decision changesWhen a push deletes the file a rule is about, the rule is retired, or flagged if other repos still use it. A newer decision that contradicts a rule waits for a person.A cleanup pass proposes merges and pruning, and the agent applies them.
Seeing what was usedEvery rule shows how often it was served and how often an answer cited it.Each recall shows the sources it came from.
Stopping a risky commandBlock rules refuse a command before it runs, in Claude Code, Cursor and Codex, and hand the agent something to run instead.Not part of the product.
AgentsClaude Code, Cursor and Codex.Ten named, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot and Windsurf.
Open source and hostingThe CLI, harborloop, is MIT licensed on npm. The service is hosted.Its CLI repo is under the Elastic License 2.0, though its site says MIT. Local-first with cloud sync, and on-prem on Enterprise.
PriceIn early access: join the waitlist and we let teams in by hand. Free costs nothing for your whole team on one source, Pro is $24 per person a month billed yearly or $30 monthly, and Premium is $36, or $45 monthly.A free tier, then Pro at $15 a month billed yearly, $19 monthly. Enterprise is custom.
Best forEngineering teams who want every coding session to start with what the team decided.Developers who want agent memory as local files they own and edit.

ByteRover's side comes from its own pages, read on 1 October 2026: byterover.dev · ByteRover CLI · ByteRover plugin · ByteRover docs. Out of date? Tell us.

Which one

Pick the one built for your job.

Pick Harbor if

  • You want rules captured from where the team decides, not only from what an agent was told to save.
  • You want to see, rule by rule, which ones agents were served and which ones they used.
  • You want a rule retired when a push deletes the code it was about.
  • You want block rules that stop a destructive command before it runs.
Get early access

Pick ByteRover if

  • You want memory as local files you own and can edit.
  • You run agents beyond Claude Code, Cursor and Codex.
  • You do client work and need a walled-off workspace per client.
  • You need SOC 2 Type II today.
Can I run Harbor and ByteRover together?

Both put shared rules in front of coding agents, so most teams would pick one. The split is whether the rules come from your agents or from your team.

Can I start with Harbor today?

Harbor is in early access, and we let teams in by hand: leave an address and the people who build it will write to you. ByteRover can be signed up for today.

Is Harbor open source?

The CLI, harborloop, is MIT licensed on npm. The service is hosted. ByteRover: Its CLI repo is under the Elastic License 2.0, though its site says MIT. Local-first with cloud sync, and on-prem on Enterprise.

Where do the claims about ByteRover come from?

From ByteRover's own public pages, read on 1 October 2026, which are listed under the table. Products move, so if a line is out of date, tell us and we will fix it.

Decide once.
Every agent knows.

Nothing to migrate and nothing to write. Two weeks in, you see which rules your agents were given and which ones they cited. Leave an address and the people who build it will be in touch.

or talk to us