Blog

The best company brain tools for coding agents (2026)

Published: October 5, 2026

We make Harbor, and it is first on this list. Every other entry was checked against its own public pages on 1 October 2026, with the review steps checked again on 5 October, and each one says where it does something better than we do.

The short answer: if your team's decisions live in Slack threads and pull request reviews and you want them in every coding session, with a count per rule of how often it was served and how often an answer cited it, that is Harbor. If you want answers on demand from every system you run, with enterprise controls today, look at Unblocked. If you want one governed playbook written into every agent's own rule files, look at Packmind. For open-source memory you host, Cognee. For memory as local files your agents keep, ByteRover. For the fastest automatic memory in Claude Code, Mem0's plugin.

What counts as a company brain for coding agents?

A company brain holds what a company decided and hands the relevant part to whoever is doing the work. For an engineering team in 2026, the busiest reader is the coding agent, so this list only includes tools that Claude Code, Cursor or Codex can actually read. We judged each one on eight questions:

Where the rules come from. Written by hand, saved by agents, or learned from where the team decides.
Who decides what gets in. Automatic, a review step, or a gate you set.
How it reaches the agent. Files in the repo, context added at the start of a session, or a tool the agent has to think to call.
Only what applies, or everything. Whether the agent gets the rules for its task or the whole file.
What happens when a rule goes stale. Whether anything notices that the code moved on.
Whether you can see what got used. Not what was stored or sent, but what an answer used.
Whether it can stop an action. A rule the agent reads is advice; a block is a guarantee.
Agents, licence, price and availability. Including whether you can start today.

Start with what you have: CLAUDE.md, AGENTS.md and Cursor rules

Before any tool, there are the files every agent already reads. A CLAUDE.md holds instructions Claude Code loads at the start of every session. AGENTS.md is the shared format that Codex, Cursor, Copilot, Antigravity CLI and about twenty other tools read, and Claude Code reads it too when a project has no CLAUDE.md. Cursor adds .cursor/rules, where each rule can apply always, by file pattern or on request.

They are free, they live in git, and for a small team they are the right place to start. Their limits show up as the team grows. Someone has to write every line, every agent gets the whole file, nothing notices when a line stops being true, and Anthropic's own docs describe them as context rather than enforced configuration. We have written up why a growing CLAUDE.md stops working and how AGENTS.md and CLAUDE.md differ. Every tool below is an answer to one or more of those limits.

1. Harbor

Harbor learns the rules your team decides in Slack, pull request reviews and docs, and gives each Claude Code, Cursor or Codex session the ones that apply to its task before the agent writes a line. What a session finds out goes back in, and you set the gate: Manual holds everything for a person, Hybrid (the default) adds routine rules and holds the rest, and a rule that contradicts a live one always waits for a person.

Best for: engineering teams whose decisions live in threads and reviews, and who want every agent to start with them.
Rules come from: Slack, GitHub, GitLab, Notion, Confluence, Jira, Linear, Google Drive and Granola, plus what agent sessions record.
Reaches the agent: hooks add the rules that apply at the start of each session. The same rules are on an MCP server, the CLI and /harbor in Slack.
Where it is ahead: every rule shows how often it was served and how often an answer cited it, so you can delete the ones nobody uses (served vs cited). Block rules refuse a destructive command before it runs. When a push deletes the file a rule is about, the rule is retired, or flagged if other repos still use it.
Watch out for: Harbor is in early access, and we let teams in by hand. It wires three agents, not ten. The service is hosted only, and there is no SSO or enterprise plan yet.
Price: Free costs nothing for your whole team, on one source. Pro is $24 per person a month billed yearly ($30 monthly), and Premium $36 ($45). The CLI, harborloop, is MIT licensed.

2. Unblocked

Unblocked is a context engine for engineering teams. It reads about 45 sources, from code and pull requests to Slack, Teams, docs, issue trackers, CI and runtime tools, reconciles them and answers people and agents with citations. It now also learns conventions it sees repeated in pull request review feedback.

Best for: larger engineering organisations that want answers on demand across many systems, with SSO, SCIM and SOC 2 Type II now.
Who decides: nobody approves rules. Anyone in the organisation can correct or remove a shared memory.
Reaches the agent: the agent calls its MCP tools or CLI when it decides to, or when you ask it to. Its docs suggest a line in your CLAUDE.md telling agents to use it.
Where it is ahead: the widest source coverage here, conflict handling across sources, and the most mature enterprise controls. It also sells code review and a CI failure agent.
Watch out for: nothing is in the session until the agent asks, analytics count tool calls rather than which rules were used, and there is no free plan.
Price: $29 per user a month billed yearly, $35 monthly, after a 21 day trial.

The two overlap more than any other pair on this list. Read Harbor vs Unblocked for the rows side by side.

3. Packmind

Packmind keeps one engineering playbook of standards, commands and skills, and writes it into each agent's own files across your repos: .claude/rules, .cursor/rules, Copilot instructions, AGENTS.md and more.

Best for: organisations with many repos and several agent tools that want one versioned source of truth for their rule files.
Who decides: edits go live directly, or as Change Proposals that the team reviews before they apply. That review workflow is the closest thing on this list to a gate, and it is on the Enterprise plan.
Reaches the agent: as files committed to the repo, loaded whole or by file pattern, the way the native files are.
Where it is ahead: renders to ten agent formats, is open source under Apache 2.0, self-hosts, and has an Enterprise linter that catches rule violations before a commit.
Watch out for: rules change only when someone proposes a change. Mining Slack and pull requests is done with example skills you run yourself, not inside the app.
Price: the open-source edition is free. Enterprise, which carries the review workflow and the linter, is priced on request.

4. Cognee

Cognee is an open-source memory engine that builds a knowledge graph from documents, code and agent sessions. Cognee Cloud adds a hosted Company Brain.

Best for: teams that want graph memory they can host themselves, even air-gapped, and builders putting memory into their own product.
Rules come from: mostly what agent sessions record. In Cloud, Slack, GitHub and Google Drive are live, and its docs list more sources as coming.
Reaches the agent: its Claude Code and Codex plugins add recalled context to every prompt through hooks. Cursor and others use its MCP server.
Where it is ahead: Apache 2.0 with a real self-host story, the deepest Claude Code integration of the memory vendors, and a Memory Coverage view that scores how well memory answered.
Watch out for: extraction is automatic with no review step, and usage is priced in tokens, so cost grows with how much it processes.
Price: free up to 1M tokens, then $1 per 1M tokens and $5 for each extra workspace. Enterprise runs in your cloud.

5. ByteRover

ByteRover is shared project memory for coding agents. A desktop app and an agent skill save decisions, fixes and rules as context files in spaces you can share with teammates.

Best for: individuals and small teams who want memory as files they can read and edit, and agencies that need a separate space per client.
Rules come from: what you ask your agents to save. It does not read Slack, pull requests or docs today.
Who decides: through its company brain plugin, what an agent learns is filed as a proposal that stays pending until someone reviews it in ByteRover.
Reaches the agent: through its skill, when the agent is asked to check. Every recall shows the files it came from.
Where it is ahead: ten agents named, from Claude Code and Codex to Gemini CLI, Copilot and Windsurf, plus SOC 2 Type II.
Watch out for: cleanup is a list of proposals the agent has to apply. Its site says MIT, while its CLI repository carries the Elastic License 2.0.
Price: free, then Pro at $15 a month billed yearly or $19 monthly.

6. Mem0's coding plugin

Mem0 is a memory layer for the agents and apps you build. Its plugin for Claude Code, Codex, Cursor and others captures what happens in a session and sorts it into personal memory and a project pool that everyone on the repo reads and writes.

Best for: the fastest automatic memory across sessions, and teams already building their product's memory on Mem0.
Who decides: extraction is automatic, with no review step documented.
Reaches the agent: the plugin adds up to five memories before the first reply, and the agent can search for more.
Where it is ahead: one install to start, newer facts supersede older ones on every plan, and a large ecosystem of 31 integrations.
Watch out for: a wrong project memory reaches the whole repo, it learns nothing from Slack or reviews, and the plugin needs the hosted platform even though the library is open source.
Price: free, then $19 and $249 a month by request volume.

Built for other jobs

Four products come up in the same searches and do a different job:

Zep builds dated context graphs, one per user or account, for customer-facing agents you build with its SDKs. It has the strongest model of time anywhere on this page. Its Context MCP server now opens a user's memory to off-the-shelf agents too; writes are on by default and an admin can make a connection read-only. See Harbor vs Zep.
Devin keeps its organization's knowledge as skills, after Knowledge notes were moved into a knowledge plugin per scope, and admins can have Devin change the organization's plugins, approving each change (release notes, 25 September 2026). It is memory for Devin, not for Claude Code, Cursor or Codex.
Gyld is a company brain for business operations: email, CRM, books and databases, reachable from coding agents over MCP but with nothing specific to code. $100 a month per workspace.
Supermemory's company brain was open-sourced in September 2026 as a Slack teammate you host on Cloudflare. Its own guide says the self-hosted build has no MCP server or API yet, so a coding agent cannot read it.

Newer entrants that call themselves a company brain for agents, including Hyper, Memory Store and Almanac, launched this year. We have not reviewed them here yet.

Side by side

	Rules come from	Who decides	Reaches the agent	Shows what was used	Blocks a command
CLAUDE.md and AGENTS.md	Whoever writes them	Whoever commits	The whole file, every session	No	No
Harbor	Slack, PRs, docs and sessions	A gate you set	Rules that apply, at session start	Served and cited, per rule	Yes
Unblocked	About 45 sources	Automatic	When the agent calls a tool	Tool calls per agent	Not documented
Packmind	A playbook you write	Direct edits, or review on Enterprise	Rule files in the repo	Which version is where	No, but a pre-commit linter on Enterprise
Cognee	Sessions, plus 3 sources in Cloud	Automatic	Every prompt, through hooks	Citations, coverage scores	No
ByteRover	What agents are asked to save	A reviewer, for its company brain plugin	When the agent checks	Sources on each recall	Not documented
Mem0's plugin	Session activity	Automatic	Up to five memories at the start	What was added or served	Not documented

Read the “Who decides” column again. A month ago a review step was rare. Now Packmind, ByteRover and Devin each have one, and Zep can make a connection read-only. A gate is becoming table stakes. The column that still separates these tools is “Shows what was used”: whether you can see, per rule, what reached a session and what an answer cited. A cite is evidence the rule was used, not proof it was obeyed.

How to choose

Your rules fit in one file and one person keeps it: stay with CLAUDE.md and AGENTS.md.
You want one playbook, versioned and reviewed, in every agent's own format: Packmind.
You want answers on demand across every system, with SSO and SOC 2 today: Unblocked.
You want to host the memory yourself, under an open licence: Cognee.
You want agent memory as files you own: ByteRover. The fastest automatic memory: Mem0's plugin.
You want the decisions from Slack and reviews in every session, with a count of which rules were served and cited, and a gate you set: Harbor, in early access.

Every comparison we keep is on one page, each dated and sourced to the other product's own site. If a line here is out of date, tell us and we will fix it.

Questions

What is the best company brain for coding agents?

It depends on where your decisions live and what you need to see. For decisions made in Slack threads and pull request reviews, served to every session, with a count per rule of how often it was served and cited, Harbor. For answers on demand across many systems with enterprise controls, Unblocked. For one versioned playbook written into every agent's rule files, Packmind. For open-source memory you host, Cognee.

Is a CLAUDE.md or AGENTS.md file enough?

For a small team with rules one person can keep, often yes. They are free and live in git. They stop scaling when nobody has time to write every decision down, when every agent gets the whole file whatever the task, and when nothing notices that a line has stopped being true.

What is the difference between agent memory and a company brain?

Agent memory keeps what an agent noticed, usually for one person or one repo. A company brain holds what the team decided, from the places it decides, and decides who approves a fact before every agent on the team is served it.

Which company brain tools work with Claude Code, Cursor and Codex?

All six on this list reach Claude Code, Cursor and Codex. Harbor wires those three with hooks and an MCP server. Unblocked, Cognee, ByteRover and Mem0 name more agents, and Packmind writes rule files for ten agent formats.

Are there open-source company brain tools?

Cognee and Packmind's core are open source under Apache 2.0 and can be self-hosted. Mem0's memory library is Apache 2.0, though its coding plugin needs the hosted platform. Harbor's CLI is MIT licensed and the service is hosted.