coreCerebrum

A brain your whole team shares

Your chat app remembers one person's preferences. coreCerebrum remembers your team's solved work, and hands it to the next person and the next session before they start digging.

Example recall. File names are illustrative.

How does team memory work?

Memory is a first-class store, separate from any one transcript or laptop.

  1. Capture

    Say "we decided", "the convention is" or "gotcha" while you work. It is saved without a command.

  2. Distill

    Raw notes become clean memories. A new decision supersedes the old one, and nothing is hard-deleted.

  3. Find

    Hybrid search fuses meaning and keyword results and reranks them, so a vague question still lands.

  4. Recall

    A memory router surfaces the relevant decisions and gotchas on the prompt that needs them.

  5. Maintain

    A nightly job archives the obsolete, fades the stale and checks again for duplicates.

What does it remember?

The things that are not visible in the code and not written in any README, kept while the reasoning is still fresh.

  • Decisions

    Why approach A beat approach B, recorded at the time it was decided.

  • Gotchas

    The quirk that cost an hour once, so it never costs an hour again.

  • Conventions

    Project rules the team follows that no linter will tell you about.

  • Bug log

    Each entry records the error, its root cause and the fix. It opens before an edit to a file that has failed before.

Current docs, served into the session

Ask for a library and the docs service crawls its real documentation from the README, the docs folder and llms.txt, indexes it, and serves focused answers into the session. Each project's declared libraries are warmed up on startup so they are ready before you ask.

  • No rate limits and no stale snapshots
  • The same memory and docs reach Cursor through two MCP servers
  • Agents reach memory in session with search, save, knowledge and related tools
One card, one worktree, one branch.

Shared where it helps, private where it matters

The configuration is shared because everyone benefits from it. Client work, personal overlays and local session history stay on your machine by design.

What is shared with the team and what stays local
Shared with the teamStays local
Skills, commands and review agentsYour composed settings
Hooks and guard rulesPersonal overlay and preferences
Team memory you publishSession history and transcripts
Documentation syncClient data and project profiles

Team sync is opt-in per project. Turn it off and coreCerebrum is a fully capable single-user board.

Stop paying twice for the same work

Start with a Memory seat at $30 a person, add Build for the people who run agents, and see the difference on your own work. No charge for 30 days.

No charge for 30 days. Your card is billed starting month 2.