Skip to content

Releases

v2.12.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 20:06

Dependencies

  • @modelcontextprotocol/sdk 1.32.1 → 1.32.2.

Documentation and listings

  • A new README tour (docs/crbro-tour.gif, also as an MP4): memory across sessions, corrections that replace old facts, warnings on values that may be out of date, no_answer, secrets kept out, open items above the prompt, editing in crbro-memory view, and npx crbro-memory install. It is drawn by code; its sources are in docs/media/tour, so it can be redrawn when a feature changes.
  • README: Codex in the client badge, a clearer opening paragraph, view, export and import under Using it, the nightly performance gate and the 2.12 test count under Measurements. docs/features.md lists what 2.11 and 2.12 added.
  • The npm description and keywords and the MCP Registry description now say what CRBRO does today.
  • The desktop bundle's privacy link pointed at a README anchor that no longer exists; it now points at docs/privacy.md.
  • docs/releasing.md: npm trusted publishing is set up for the release workflow, and after each release the GitHub release is republished under the maintainer's account, because Glama only builds releases published by a person.

v2.12.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 18:41

Search

  • A recall spends a third less CPU on a real brain: the full text of the entry a part of a long entry came from is now found in a table built once per neuron, not by hashing every entry on each lookup. Steady-state recall with the semantic layer on a 563-neuron brain: p50 94 → 57 ms, p90 164 → 76 ms.
  • The search index (tens of MB, serialised with the event loop held for ~0.4 s) is written after 30 s of quiet and at the latest 5 minutes after the first unsaved change, instead of 5 s after every change. crbro_consolidate and exit still write at once. (A binary index format was measured and not adopted: 51 MB against 63 MB of JSON, but it loads 3-4 times slower.)
  • crbro_inspect view=status shows semantic.coverage (vectors against chunks): after an upgrade the layer fills in the background and recall answers keyword-only (semantic: "warming") until they match.

crbro-memory view

  • Edit the text of an entry from the page. A fact is replaced with supersedes (the old one is retired in the same call, its keywords kept); a pattern, preference, error, debt or decision is written new and the old text retired after (a decision keeps its rationale). Nothing is deleted: the old text stays in the file and leaves recall.
  • Merge one neuron into another from the page: it previews what moves, then runs crbro_forget merge_into; the source's copy stays in quarantine and the page says how to undo it.

Performance gate

  • benchmarks/perf/nightly.mjs (npm run perf) and .github/workflows/perf.yml (every night and on demand): the real server over stdio on a synthetic brain of realistic size (~500 neurons, ~7,000 entries), semantic layer included, with budgets for sizes, boot and recall latency and for the upgrade case (recall while the vectors fill in). It is the test that would have caught the 2 s recalls of the first minutes after upgrading to 2.11.0.

Tests

  • A daemon test that rebuilds a 151-neuron brain gets a 30 s timeout instead of the 5 s default, which it broke when the suite ran under load.

v2.11.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 02:49

One release for the whole 13-11-2026 audit: faster and steadier startup, search
that finds Spanish words, smaller answers, safer data and secrets, a unified
installer and four new commands. Still 15 tools; every field the zero-crbro card
reads keeps its name and meaning. The search index rebuilds once on first start.

Startup and daemon

  • Daemon mode: the proxy answers initialize, ping and tools/list itself
    at once, whatever the daemon is doing, from a snapshot of the real server
    written at build time (dist/mcp-surface.json): initialize in ~80–95 ms
    instead of waiting for a daemon to be found or started (603 → 94 ms when it
    has to start one). This is what made Codex give up on a slow start.
  • A client that waits before sending initialize is no longer cut every 5 s:
    the daemon's handshake clock stops once the proxy has authenticated.
  • A proxy that had to serve in-process keeps looking for a daemon and moves
    back once one answers and no call is running; three lost daemons in a minute
    now mean a pause, not in-process for good. Getting a daemon is bounded by one
    12 s budget. After any move, the proxy repeats the conversation's last
    crbro_boot (answer kept to itself) so its project binding survives.
  • One daemon per release: the build id is a hash of the compiled code
    (dist/build-id.json, written by npm run build), so two installs of the
    same version share one daemon.
  • daemon stop / off let running calls finish (up to 10 s); a call the
    daemon had not started is sent to the next backend, and a call cut by a crash
    says it may or may not have taken effect.
  • .daemon is cleaned on every daemon start and by daemon status|stop|off:
    descriptors whose daemon does not answer at its endpoint (never judged by PID,
    which Windows reuses) and stale temporary, lock and blocked files.
  • A daemon that cannot start says why in .daemon/daemon.log and the waiting
    client stops waiting at once.
  • CRBRO_STARTUP_TRACE=1 prints the startup phases with timings to stderr and
    <brain>/.daemon/startup-trace.log.
  • A single MCP message over 32 MB gets -32600 for its id instead of being
    split into two broken messages.

Search and recall

  • Words with á, í, ú, ñ or ü are now found with or without the accent, and
    hyphenated or slashed compounds by any of their parts (memory finds
    crbro-memory). The index rebuilds once (format 8).
  • crbro_recall says no_answer: true when nothing stored clearly matches and
    returns at most three weak rows without also_matched, instead of five rows
    that read like answers. CRBRO_NO_ANSWER=0 restores the old behaviour.
  • A semantic-only match is strong above this brain's own noise line (measured
    in the background, stored with the index) instead of a fixed 0.86.
  • With several queries, the row shown is one phrasing's own row, so its
    confidence and scores agree; also_matched never repeats an entry.
  • One large neuron no longer wins by size; the bound project's neurons get a
    ×1.25 boost instead of being placed above better global matches.
  • Entries over 1,200 characters are indexed in overlapping parts and recall
    returns the part that matched (matched_part).
  • A search index that is only behind the files is refreshed, not rebuilt (boot
    with a stale index on a 500-neuron brain: 1.9 s → 0.4 s). A running server
    sees what other processes saved before every search and never overwrites a
    newer index with an older view. Classic stdio mode writes the index when the
    client leaves (at most 2 s).
  • Smaller index and memory: only searched fields are indexed, no sort data.
  • Semantic vectors are added and saved in slices while a large pass runs (the
    upgrade itself splits long entries into parts that need new vectors), so a
    process that leaves halfway keeps what it did. The pass pauses while a search
    runs, and while it lasts recall answers keyword-only with
    semantic: "warming". Measured on a 563-neuron brain right after upgrading:
    recall 0.05–0.4 s during the ~4-minute pass, instead of 1.5–3 s with 20 s
    stalls.
  • A running server's once-a-minute check of the brain's files reads their
    dates in parallel: ~0.5 s instead of ~20 s on a busy machine.
  • Semantic layer: recall waits at most 1.5 s for the model
    (CRBRO_SEMANTIC_WAIT_MS), then answers keyword-only with
    semantic: "warming"; only semantic install downloads; missing vectors are
    re-embedded and orphans pruned at start; the runtime is pinned to
    @huggingface/transformers 3.8.1 and the model files to SHA-256 hashes.
  • New Spanish retrieval benchmark gating npm run bench; the old gate's floor
    rises.

Smaller, clearer answers

  • crbro_boot is about half the size: protocols whole, then counts, open items
    (due first, then newest; 180 characters; age_days; review: true past 30
    days without a due date), closed items as titles, hot topics, session
    headlines and a shorter memory_discipline. New pending block whose
    numbers always match message, and a more line naming what was left out.
    open_items_total, recently_closed_total, active_protocols and
    sessions_note are gone; retired_tools moved to crbro_inspect view=status.
  • crbro_boot no longer fails when project_neurons names a neuron that is
    gone (listed in unknown_project_neurons). Over its budget it drops session
    headlines and hot topics before open items.
  • crbro_recall rows leave out fields at their default (temporal,
    verification, freshness, provenance), as the description says.
    relevance is {score}; relevance_score, matched_terms and query_terms
    left the MCP rows. Previews are capped at 160 characters. The "say it may be
    out of date" instruction appears once, in stale_warning. A corrupt neuron no
    longer fails the whole recall (unreadable_neurons).
  • crbro_context writes return what changed and the counts
    (return_context: true for the old reply): 22,381 → 427 characters.
  • Not-found and bad-parameter answers carry isError: true in revise, forget,
    map, space, share and learn. crbro_forget entire tokens cover the whole
    neuron and are valid only in the process that issued them.
  • crbro_learn warns (never refuses) on facts over ~600 characters and neurons
    over 300 entries or 300 KB.
  • Tool definitions (tools/list): 44,434 → under 30,000 characters.

Data integrity

  • backup --keep must be a whole number ≥ 1 ("siete" or a missing value used
    to delete every copy). Each new copy is flushed and read back before any
    rotation and is never rotated itself; a copy dated in the future no longer
    counts as the newest.
  • Tiered backup retention: the newest N copies (--keep, default 7) plus one a
    day for N days, one a week for 4 weeks and one a month for 6 months.
  • A neuron file with a byte-order mark reads normally. A file that does not
    parse no longer breaks recall, crbro_inspect, crbro_maintenance,
    crbro_consolidate or the boot's protocols: it is skipped and named with
    where a good copy is, and writes to it are refused.
  • Similar topic names no longer merge ("Sprint B" stays out of "Sprint A");
    only the same name with or without underscores, or a plural, resolves to an
    existing neuron (resolved_by: "variant", ambiguous when several match).
    "C", "C++" and "C#" are three neurons; non-Latin names get their own neuron;
    project_x no longer becomes project_project_x; types are inferred from
    whole words.
  • crbro_learn with a neuron_id that does not exist is an error instead of
    writing to whatever the topic matched. supersedes also applies when the new
    fact already exists, and the retirement reaches shared spaces.
  • Entries that differ only in whitespace or case are one entry.
  • Synapse writes take the same lock as every other write; a write never brings
    back a neuron deleted meanwhile. Decay follows elapsed time (decayed_at),
    pruned synapses get a quarantine copy, and archiving never takes protocols or
    shared neurons and keeps an archived neuron's links.
  • Quarantine retention: CRBRO_QUARANTINE_DAYS (default 180; 0 keeps copies
    forever); crbro_consolidate and crbro_maintenance prune older copies and
    report quarantine_pruned. Forgetting some entries keeps a copy of just those
    entries; repair and purge_boilerplate also keep what they remove.
  • Opt-in encryption at rest of backups and quarantine copies
    (CRBRO_ENCRYPT_AT_REST=1, AES-256-GCM, 32-byte key CRBRO_AT_REST_KEY in the
    OS keychain). Without the key nothing is written in clear and nothing deleted.
  • Heat is kept in prefrontal/heat_state.json: consolidate re-reads only
    changed neurons and never rewrites a neuron for heat (first consolidate on a
    500-neuron brain: 1.5 s → 0.36 s).
  • crbro_maintenance stale_list pages through every stale entry and
    stale_review verifies or retires many at once; the dry run adds a read-only
    hygiene report (split_partitions, merge_candidates, summary_missing).
  • The shelf-life detector no longer marks Spanish thousands ("1.200.000"),
    monthly counts or the name "Max" as volatile.

Secrets, keychain and team spaces

  • Breaking: crbro_secret get no longer returns arbitrary environment
    variables of the server process. An environment value counts only as
    CRBRO_SECRET_<NAME> or when <NAME> is listed in CRBRO_SECRET_ENV; answers
    say source: "env" | "keychain". Names must be SCREAMING_SNAKE_CASE.
  • Through MCP, overwriting a secret with a different value and removing one are
    two-step (confirm_token, then confirm); the first call writes nothing.
  • Windows keychain: a missing keys.dpapi is an error with recovery steps when a
    store existed, never an empty store (secret set NAME --force starts one on
    purpose). Every write keeps rotated sealed copies (CRBRO_KEYS_COPIES,
    default 5); secret copies lists them and secret restore <id> --yes puts one
    back after validating it.
  • Keych...
Read more

CRBRO 2.10.0

Choose a tag to compare

@Octonove Octonove released this 18 Oct 10:31

CRBRO 2.10.0

Reliability, explicit evidence, project context and read-only diagnostics. Still 15 MCP tools, compatible with existing brains and callers.

  • Locked fresh keychain writes, ownership-aware locks and atomic context/session updates.
  • Durable shared-delivery outbox, idempotent retries and recovery archives when leaving a space.
  • Repetition no longer counts as verification; structured sources and explicit user/source verification.
  • Stable project identities, aliases, connection-local scope and structured pending items.
  • Separate relevance, provenance, freshness and verification in recall results.
  • Read-only doctor --json, frozen benchmark gates and expanded regression coverage.
  • Updated dependencies; release-time audit reported no advisories.

Validation: 943 tests passed, 6 skipped; Windows and Linux CI passed. Build and frozen retrieval/security benchmarks passed.

Installation

Use npx -y crbro-memory@latest in an MCP client, or download the .mcpb asset for Claude Desktop. Restart the client/server after updating; an already-running process does not upgrade itself.

Repository history notice

Two previously exposed credentials were removed from historical test fixtures. The WordPress application password was revoked and replaced; the old SSH password was confirmed rejected. All 46 previously published npm versions were checked for those two values and their tested encodings, with no matches. This is a targeted check, not proof against every possible secret or encoding.

The main branch and historical tags were rewritten. Existing contributors should preserve their own uncommitted work and use a fresh clone; do not merge the old history back. Copies in third-party forks or caches are not removed by rewriting this repository.

The operating-system credential vault is not included in releases. Local storage does not mean a secret can never leave the machine: explicitly retrieving it into an AI conversation or using it to authenticate sends it to the relevant client/service.

2.9.1 — Shelf life, less noise

Choose a tag to compare

@Octonove Octonove released this 04 Oct 15:28

Shelf life, less noise: what 2.9.0 flagged on a real brain was mostly not a
value that may have changed. Design and measurements in
docs/design/staleness.md §15. Still 15 tools;
one parameter description changes (crbro_forget facts), no parameter does.

  • The noise it answers. Run read-only over one real personal brain, 2.9.0
    flagged 810 of 4,858 active entries (17 %) on the first day, every one an
    inferred-volatile fact, none graced. 336 were notes a miner had imported
    (agent checklists with URLs) and a large share of the rest were dated
    records of something done. The statements of state that should warn were a
    minority among them.
  • A miner line never warns. A fact with source: "miner" and no explicit
    shelf_life is permanent, inferred, shelf_reason: "miner". An explicit
    shelf_life still wins, and once a session says the same line (it gets
    verified or a second confirmation) it is judged by its text again. Lines
    mined before the miner stamped its source (1.5.x) are stored with
    source: "session" and are not reached by this.
  • A dated record of something done is history. An unmarked fact whose
    first sentence names a date (2026-06-18, 18/06/2026, 18-jun-2026, jun 2026,
    June 18, 2026…) and a finished action (completado, desplegado, publicado,
    verificado, corregido, migrado, rechazado…, "se publicó", fixed, deployed,
    released, completed, verified… or an event noun: fix, hotfix, rechazo,
    incidente, release) is permanent, inferred, shelf_reason: "history".
    Not when that sentence opens a period with its date ("desde el 18-sep",
    "since", "as of", "a partir de", "a 4-oct"), looks ahead (will, planned,
    programado, pendiente, caduca, expires, renews, "para el "), speaks of
    the present (actualmente, currently, current, ahora, último, last, latest),
    or states something before the action ("la API corre en el puerto 8443,
    desplegada el …"). And when that sentence carries a changeable value, not
    when it also says the value holds: a verb of state anywhere in it ("Fix
    (…): el webhook apunta a https://…"), a dated check of the value
    ("Comprobado el 4-oct-2026: cuesta 35 €", "Puerto 9443 verificado el …"),
    a move to a place ("Migrado el panel al puerto 9443 (18-sep-2026)",
    "Deployed to https://… on …") or a schedule ("diaria 03:00"). Actualizado,
    cambiado, configurado, updated, changed and set are not finished actions:
    they bring a new current value; cerrado, aprobado, completo, closed and
    approved count only with no value in the sentence. A line with no date is
    never history. Only the first sentence is judged; that and the other
    limits are in the design doc.
  • The legacy grace reaches inferred-volatile facts. In a brain that
    predates shelf life — manifest not stamped yet, or stamped more than a
    minute after created — an unmarked, never-verified line the detector
    infers volatile and recorded before the stamp starts counting up to 45 days
    before the stamp, staggered by its text hash like every other graced line:
    nothing volatile is flagged on upgrade day, and those lines come due spread
    over days 46–91. A fact marked volatile by hand gets no grace, and in a
    brain born with shelf life (created and stamped together) nothing changes.
    Read from created and staleness_since; nothing new is stored.
    Measured on the same brain: 806 flagged on the stamp day with 2.9.0,
    701 with the history rule alone, 0 with all of 2.9.1; 302 at +60 days and
    1,353 at +91. 816 lines read as history; 105 of the 806 never warn again
    and the rest are postponed. The grace postpones, it does not reduce: the
    imported checklists that fix 1 cannot see are still the largest group.
  • view=status says the version that runs. crbro_version is read once,
    when the server loads, not from disk on every call: a process whose files
    npx replaced reported the new version while it ran the old code. When the
    package on disk says another version, status adds installed_version and a
    version_note (restart the client to load it). The daemon's build id
    reads the same package.json through the same lookup.
  • "clave" is an adjective too. The labelled-password pattern read
    "clave:" like "password:", so any eight-letter word after it was taken for
    the value: "Decisión clave: mantener…" was stored as "Decisión clave:
    [REDACTED: password]…" — three notes on the reference brain lost a word,
    and an audit of it flagged sixteen more. After "clave" the value must now
    look like a password (three of lower case, upper case, digit, symbol);
    dates, words and shouted words are prose. "password:" and "contraseña:"
    are unchanged, and the hook keeps the same pattern list.
  • crbro_forget takes the id of every kind. Facts were matched by id,
    decisions, patterns, preferences, errors and debts only by their exact
    text — so removing a credential from a preference meant pasting the
    credential back into the conversation to name it. Now the id that
    crbro_inspect and crbro_recall show works for all of them (a
    decision's own id too), and the purge ops for shared spaces go out the
    same way.

2.9.0 — Shelf life: what may have changed comes apart

Choose a tag to compare

@Octonove Octonove released this 04 Oct 14:12

Shelf life: what may have changed since it was last checked comes apart.
From community feedback (r/mcp); design in
docs/design/staleness.md. Still 15 tools: every
change is a parameter or a field on an existing one.

  • The gap it closes. A value that changed in the world and that nobody
    retired from memory — a port, a price, a version, who holds a role — came
    back from crbro_recall with confidence: strong and nothing else.
    confirmations counted how many sessions said a line, never when one last
    looked; since hides old lines, it does not warn; maintenance's
    expired_entries only sees a line that names a day.
  • A last verification per fact. Fact.verified (ISO instant) and, for
    decisions and patterns, the entry_verified sidecar keyed like
    entry_dates. Two ways to set it, and only two: crbro_revise status=verified (a fourth value of the existing enum; facts by id or exact
    text, entries for decisions and patterns by text or entry id) when the
    agent checked a line against its source and it still holds, and a session
    learning the exact same fact again with nothing else in the call
    (reconfirmed: true). A re-learn that also brings keywords, a confidence or
    a class is an edit, not a check — the server itself asks for that re-learn
    to add keywords — and leaves verified alone. One verify op per line per
    session, however often it is repeated. The miner never reconfirms, a retired
    line is not verifiable (it comes back in unmatched and retired_targets),
    reading — recall, inspect — never touches it, and a check dated more than a
    day ahead of this machine's clock counts as no check (it would otherwise win
    every "latest" merge and keep the line fresh until that day).
  • A shelf life by kind of data. volatile 90 days (versions, prices,
    ports, hosts, paths and URLs, configuration values, people in roles),
    normal 365, durable 730 (decisions and patterns), permanent never
    (preferences, errors, debts, history). The windows are a policy choice, not
    a measurement; CRBRO_SHELF_DAYS="volatile=90,normal=365,durable=730"
    changes them per machine. crbro_learn takes shelf_life for facts (stored
    only when given; a different value on the same text replaces it,
    updated_in_place) and always returns the class that applies, with
    shelf_inferred and shelf_reason when it was read from the text. An
    unmarked fact is classified at read time by a small, conservative detector
    (src/engine/shelf.ts, Spanish and English; every rule needs a number, a
    path or URL shape, or a role-and-name pattern next to its trigger word), so
    a better detector improves old facts too. Measured on the repository's
    retrieval fixtures: it marks 25 of the 48 facts of the project fixture (a
    brain of versions, prices and hosts) and 3, 3 and 0 of the 494 facts of each
    personal-prose haystack.
  • Recall that warns. After the ranking — which does not change — a row
    whose winning entry is past its shelf life since last verified moves, whole
    and in rank order, to possibly_stale, with age_days, last_verified,
    shelf_life and shelf_inferred (and age_counted_from when the legacy
    grace applies). When anything moved, every row carries its rank, and if
    the top-ranked row is the one that moved the hint opens with "The best match
    (rank 1) moved to possibly_stale", so the first row of results is not
    taken for the answer to the question when it may be about something else.
    No backfill and no re-heading with an also_matched line;
    an old also_matched preview keeps its place and carries stale_days. The
    next step is said once, in hint (check it against its source; still true
    → crbro_revise status=verified, changed → crbro_learn with
    supersedes; if you cannot check, say how old it is), led by "Nothing
    current matched" when every row moved. total_results counts current rows,
    returned adds the stale ones, possibly_stale_count is there when the
    block is. since still filters on when a line was recorded: a reconfirmed
    old line is not new. Day logs are never partitioned, protocol neurons are
    never judged. With the feature on, the deterministic retrieval benchmark
    gives the numbers published for the keyword engine (recall@1 77%, recall@3
    83%, MRR 0.806).
  • No flood on upgrade. The first boot of this version stamps
    manifest.staleness_since (one field in a file boot already writes; no
    neuron is touched). A fact never verified, with no explicit class, not
    volatile and older than the stamp starts counting near it; decisions and
    patterns likewise. Not from the stamp itself, which would only delay the
    flood: every old line would cross its window on the same day. Each line's
    clock starts up to half a window before the stamp, by a fixed share drawn
    from a hash of its text and never before its real date, so nothing is due on
    the stamp day and an old brain's lines come due spread over the second half
    of the first window. A manifest write from a process whose cache predates
    the stamp keeps it, and boot restores one an older CRBRO dropped, so the
    stamp does not drift. Volatile facts get no grace: a port saved months ago
    is exactly the case. A line with no parseable date is never flagged.
    CRBRO_STALENESS=0 turns everything off and recall answers as in 2.8.
  • Everywhere else the same three facts. crbro_inspect view=neuron shows
    verified, an explicit shelf_life and stale_days per entry (index and
    entries=[ids]); view=status reports staleness: { enabled, windows, since }. crbro_maintenance reports stale_entries and stale_sample (the
    ten most overdue), read-only; repair drops entry_verified keys whose
    entry is gone. Boot's memory_discipline and the server instructions gain
    one sentence each on what possibly_stale means.
  • Team spaces. A check travels as a new verify op (latest at wins,
    order-independent); an explicit shelf_life travels as shelf on the fact
    op (the most volatile explicit value wins, so a shared fact's class can be
    shortened but not lengthened: the next sync restores the more volatile value
    from the log, and crbro_learn warns in shared_warning). A check on a fact
    stored before ids existed lands on the teammate even when its text has a
    double space or is not NFC (both text hashes are accepted). OPS_VERSION
    stays 1: a 2.8 client skips the new
    kind and ignores the new field — the check does not reach it, nothing is
    corrupted. move_to, merge_into and restore carry the stamps; forget
    prunes them.
  • Compatibility. Every new field is optional; a 2.8 brain loads and
    recalls as it is, and nothing is written to a neuron until a learn or a
    revise touches it. No index change, no INDEX_VERSION bump: shelf life and
    verification are read from the neuron file recall already loads for every
    row. Tool descriptions stay under 1,000 characters (recall 993, learn 983,
    revise 946, with the second iteration below). With the optional daemon, CRBRO_STALENESS and
    CRBRO_SHELF_DAYS are part of the configuration fingerprint (only when they
    differ from the defaults, so existing fingerprints do not move): a client
    that switched the feature off is never served by a daemon that has it on.
  • The agentic benchmark: measured, and not met. A new pre-registered
    case, stale-unmarked (fifth amendment of
    benchmarks/agentic/PREREGISTRO.md): four values that changed in the world
    and that nobody retired, two marked volatile and two left to the detector,
    with the current value in a file both arms can read. Measured on
    2026-10-04 with Claude Code 2.1.270, n=3, the 2.8.0 build (before) against
    this branch (after, two runs per model: the four new tasks alone, then
    all 16). With CRBRO the agent answers 0 of 12 correctly in every run,
    before and after, in haiku and in sonnet. Old value given without a
    warning: haiku 11 before, 9 and 10 after; sonnet 12 before, 11 and 12 after;
    one sonnet answer gave it with a warning (hedged). Without memory the
    agent reads the file and gets 3 and 6 (before) and 1-6 (after) of 12.
    U1, U2 and U3 fail in every after run; U4 passes in three of four by one
    or two cells, which is noise at n=12; U5 passes (the 12 original tasks
    keep 4/4 thresholds: 24/24, 0 retired values, controls 6/6). The claim
    "CRBRO warns and the agent checks" is not made. Why, from the cells:
    recall flags all four rows correctly (checked without a model on the same
    brain), but in 48 after cells no agent with CRBRO opened a file — the
    warning arrives and does not change what the agent does on these tasks.
    No cell tried crbro_revise or crbro_learn. Cost per CRBRO cell on these
    tasks: haiku $0.0121 → $0.0149 / $0.0151 at the same turns (3.1 → 3.0),
    sonnet $0.0263 → $0.0270 / $0.0274 with fewer turns (3.6 → 3.1). Canaries
    clean, no leaks, no API errors. Before the after runs, a dated note in
    the pre-registration recorded that before ran after the implementation
    commit (in separate clones of 2.8.0 and of the frozen harness), the
    CRBRO_MOD=0 deviation and the review changes. Results:
    benchmarks/results/agentic-2026-10-04-*.json.
  • Second iteration: the warning comes first, and says what to open.
    Presentation only (detection, windows, ranking and the partition are
    unchanged; an answer with nothing stale is the same as before). When
    anything moved to possibly_stale, the answer now opens with
    stale_warning, before query and results: do not answer with it as
    current, check it first, and if you cannot, say it may be out of date, even
    in a short answer. Each possibly_stale row leads with warning ("last
    known value, unverified for N da...
Read more

2.8.0 — Open items in sight, on by default in Claude Code

Choose a tag to compare

@Octonove Octonove released this 04 Oct 08:53

Open items in sight, for whoever installs CRBRO, not only for its author.

  • On by default where Claude Code is, and said out loud. crbro_boot
    installs the mod on its own, once per server process (once per daemon),
    when ~/.claude exists: the same install as install-mod with the
    language on auto. The boot that does it carries mod_notice, a sentence the
    assistant passes on — what was installed, that it shows up in new Claude
    Code sessions, and how to remove it — handed to up to three server
    processes, once each, within a week, since the first may be a background
    run nobody reads. After an update of CRBRO, a boot that finds the installed
    files different from the package (SHA-256, line endings aside) refreshes
    them without touching settings.json, and says so; an older CRBRO on the
    same machine never takes back a newer one's files, and two builds of one
    version do not rewrite each other. The way out is easy and final:
    uninstall-mod leaves a mark in ~/.claude/crbro-mods/state.json and the
    mod is never put back on its own, by any client (install-mod lifts it);
    taking the folder out of CLAUDE_CODE_PLUGIN_DIRS by hand counts as a no
    too, and is said once with the way back; CRBRO_MOD=0 turns the automatic
    part off for the client whose env sets it, and a daemon started without it
    never serves that client. It never fails the boot (files copied without
    blocking, 1.5 s at most, every error caught), leaves a settings.json that
    does not parse untouched and does not retry the same failure until that
    file or the package changes, or a day goes by, installs nothing beside
    another crbro-pending already in the list or when only the environment
    sets CLAUDE_CODE_PLUGIN_DIRS (writing it to settings.json would hide
    those plugins; said once), and two sessions starting at once take turns
    through an exclusive lock file. settings.json is written only if it is
    still what was read, with its line endings, and checked after writing:
    every key kept, the path listed once. SECURITY.md has a section on it.
  • The open items above the prompt. npx crbro-memory install-mod adds
    crbro-pending, a Claude Code mod: the newest open item of the brain drawn
    whole above the prompt — a short Label: apart, (1) … (2) … steps one per
    line, its age green, amber or red — with ‹ › through the rest, compact/read
    all, See all and Hide. /pending (alias /pendientes) shows every item
    as a card, with a filter that ignores accents, Work on this (the item
    written into the prompt, not sent), Done and Discard behind a yes/no,
    and what was closed lately. It started as a mod the author kept in his own
    ~/.claude, reading his brain file by hand and speaking only Spanish.
  • It asks CRBRO, not the disk. The list comes from crbro_context with no
    arguments, which only reads, on whichever MCP server has that tool —
    crbro in a standard install, any other name found from the session's tool
    list or from the first CRBRO tool the model calls. Only when no server is
    reachable does it read <CRBRO_PATH or ~/.crbro>/prefrontal/active_context.json,
    resolving CRBRO_PATH exactly as the server does, and the pane says which
    of the two it read. Done and Discard always go through the server; the
    mod never writes the brain.
  • English and Spanish. English by default and Spanish complete, every
    string in one table. install-mod --lang en|es stores the choice in the
    mod's own setting (a row in /config too); auto follows CRBRO_LANG,
    then LC_ALL / LC_MESSAGES / LANG, then the system locale.
  • Sturdy with any brain, not only its author's. A colon makes a label only
    when it ends a word, so a path, a URL or a time stays whole; an item with
    no id reads without a dangling one; the pane draws 40 cards at most and
    cuts a line at 2,000 characters, so a large brain never gets it unmounted;
    Work on this adds to what was typed instead of replacing it; a CRBRO tool
    call waits at most 1.5 s for the band to catch up; a language picked in
    /config applies on reload; a terminal too narrow for the pane says so.
  • Installed with the same care as the hooks. The mod is copied to
    ~/.claude/crbro-mods/crbro-pending and that folder is added once to
    env.CLAUDE_CODE_PLUGIN_DIRS in ~/.claude/settings.json, with ; on
    Windows and : elsewhere. A file with a BOM is read, one that does not
    parse is left alone, the write is atomic — through a symlink to its target,
    with its permission bits and its indentation kept — and a second run
    changes nothing. A folder in that list holding a plugin named
    crbro-pendientes — the hand-made copy — is replaced in place and named,
    and its folder is left on disk. Any other copy (another crbro-pending in
    the list, or one in ~/.claude/mods) is pointed out and never touched.
    uninstall-mod removes the entry (and the variable, and an env block,
    when they end up empty), puts back the crbro-pendientes folder it had
    replaced if it is still there, and deletes its own folder, nothing else.
    Folders that only the shell's CLAUDE_CODE_PLUGIN_DIRS lists are named,
    never merged in silence.
  • Verified like the hooks. install-mod --verify, and install-hooks --verify too, compare the installed copy with the package file by file by
    SHA-256 and check that settings.json lists it; a file the package does
    not ship, or a second copy Claude Code would also load, is a difference
    too. Exit 1 on any.
  • Requirement. Mods need Claude Code 2.1.286 or later, and are drawn in the
    CLI and in the desktop app's Code tab — not in Claude Desktop chat, Codex,
    Cursor or the VS Code extension. A new session picks the mod up.
  • Package. mods/ ships; the mod's tests, tsconfig.json and generated
    types do not (mods/crbro-pending/.npmignore). The mod's tests run under
    claude plugin test, the installer's in the vitest suite, which leaves
    mods/ to the former.
  • A new tour at the top of the README. docs/crbro-tour.gif replaces the
    August demo: memory across sessions, corrections that replace old facts,
    secrets kept out, the guard, the compaction checkpoint and the band.
    docs/pending-band.gif shows the band and /pending at work. Both are drawn
    by code with made-up data; every figure on screen is one this README states.

Install / update: claude mcp add --scope user crbro -- npx -y crbro-memory · Claude Desktop: double-click crbro-memory-2.8.0.mcpb below.

Open items band

2.7.2 — the agentic benchmark, rare words weigh more, keywords asked for

Choose a tag to compare

@Octonove Octonove released this 03 Oct 04:14

The first run of the agentic benchmark, what it fixed in the server's
instructions, and recall re-measured on a bigger exam and a bigger brain.

  • A fresh session does not ask again what memory already holds. Measured
    for the first time with a real agent (benchmarks/agentic/, haiku and
    sonnet, Claude Code 2.1.270, n=3): with CRBRO 24/24 on questions whose answer
    lived only in memory, 0 retired values given; without it 0/24, and sonnet
    invented 4 answers. The run found two faults in the server's instructions,
    fixed before the run that is published: an agent that recalled, found
    nothing and answered "I don't know" although the answer was in the question,
    and — after the first wording of the fix — an agent that skipped recall.
    The instructions now say to recall even when it thinks it knows, and that
    only an answer stated in the current message outranks memory.
  • crbro_learn asks for keywords. A fact saved without them is stored and
    the answer carries keywords_missing: true and a one-line keywords_hint
    to call again with 2-5 of them: they merge into the same fact. Keywords are
    the largest measured lever on recall; on the author's brain a quarter of
    all facts carry them (65-80% of those saved since September).
  • Rare words weigh more. Each query term was normalised against its own
    best hit, so a word found in a third of the brain counted as much as the one
    word that names the thing. Terms are now weighted by rarity (BM25 idf).
    Chosen on a tuning set only (benchmarks/retrieval/dev.json); on the
    original 48-question exam the keyword engine goes from 71% to 77% at rank 1,
    and inside a 1,482-fact haystack from 42% to 54%. On the new 96-question
    exam it does not move (49%). CRBRO_IDF=0 turns it off.
  • The same fact always gets the same vector. The int8 embedding model
    quantises per batch, so a line embedded with others got a slightly
    different vector than alone (cosine 0.994 at worst). The first full pass now
    embeds one line at a time, as every learn does since 2.5; it costs 1.6× the
    time, once. No benchmark moved. CRBRO_SEMANTIC_BATCH overrides.
  • The drop of the semantic layer is traced. 79% → 73% at rank 1 between
    2.4 and 2.5 came from two commits: the recency tie-break (−2, an artefact:
    the benchmark's facts are learned in the same second) and embedding only the
    new lines of a neuron, one at a time, after the cosine floor had been tuned
    on vectors computed in batches (−4). No bug in the search logic. The floor
    stays at 0.84: swept on the tuning set, 0.80-0.84 is flat.
  • Benchmarks. retrieval/dev.json (48 questions + 10 distractors, for
    tuning), retrieval/test2.json (96 + 20, a second blind exam) and three
    haystack files (1,482 facts in 114 unrelated topics), frozen before any
    measurement; run.mjs reads them through CRBRO_BENCH_QUERIES and
    CRBRO_BENCH_HAYSTACK. A longer stopword list was measured and does not
    ship: it tied once rarity weighting was on.

v2.7.1

Choose a tag to compare

@Octonove Octonove released this 02 Oct 23:50

crbro postmortem, run on a week of real sessions, put three false
candidates at the top. Fixed, each with a test:

  • A correction opens the message. The patterns are tested on the first
    160 characters only, and a message over 1,200 characters (a brief or a
    scheduled prompt that says "si algo sale mal, se informa") is never a
    correction. «eso no» counts only when it opens a sentence: "entiendo que eso
    no interfiere" and "para eso no?" were being read as corrections.
  • The desktop app's resume line is not the person. "Alcancé mi límite de
    uso mientras trabajabas… Continúa donde lo dejaste" arrives as a human
    prompt with no flag; it was showing up as the same request asked three
    times. It joins the not-a-request list, shared with the compaction hook so a
    checkpoint does not keep it as the last request either. Only the Spanish
    wording has been seen; other languages are not guessed.
  • A long session reports its active hours. "Over 398.6 h" was the time
    between the first and the last line of a session resumed for 17 days. Now
    pauses over 30 minutes are breaks: "38.7 h of activity spread over 17 days".
  • The install-hooks --verify test that compares CRLF with LF builds both
    files itself; on a Windows checkout with core.autocrlf the package hooks
    were already CRLF and the case failed in CI.

2.7.0 — compact without losing the thread

Choose a tag to compare

@Octonove Octonove released this 02 Oct 23:29

What a session leaves behind: where it was when it compacted, what it cost,
what went wrong in it, and which lessons are not about one project any more.
Everything new that touches Claude Code's files is opt-in or read-only.

  • Compact without losing the thread (opt-in, Claude Code).
    install-hooks --compact wires hooks/crbro-lifecycle.mjs into PreCompact
    and SessionStart. Before a compaction it writes a mechanical checkpoint —
    last two requests, last state of the task list, open items, folder and git
    remote — to <brain>/checkpoints/<session_id>.json, redacted with the
    brain's own patterns (each text redacted whole, then cut), written
    atomically, pruned after seven days and left out of crbro backup. Lines
    the client writes as a user turn — a background task's
    <task-notification>, another agent's message (origin.kind other than
    human), <command-message>, configuration commands such as /model —
    are not taken for requests; the hook and postmortem share the same list,
    and a test keeps them equal. The remote loses user, password, query and
    fragment. After the compaction the session starts with a "Resuming after
    compaction" block built from it, capped at 1,500 characters. No model call, no git process, never
    blocks. uninstall-hooks --compact undoes it, including putting back the
    install-boot entry it replaced.
  • The session start says where it is. The same hook fills the folder into
    the boot notice — call crbro_boot … with project="<folder>" — so
    project_neurons is used, and adds a Project: <folder> · git: <remote>
    line. With --no-boot (a hand-written notice of the user's) it still prints
    pass project="<folder>" to crbro_boot. The static notice install-boot
    writes asks for project=<name of the working folder or repo>.
  • The same lesson in two projects is a lesson about neither. Storing an
    exact fact again used to answer "already there" and forget it had been told
    twice; it now counts it (confirmations on the fact, absent means 1) at
    most once per session — a retry or the re-save after a compaction is the
    same witness, and the miner re-reading a file does not count — and
    crbro_learn returns the count.
    crbro_inspect view=neuron shows it when above 1. crbro_consolidate
    returns promotion_candidates — at most five lessons (facts, patterns,
    errors) of the projects this session touched that are the same, or almost
    (the near-duplicate rule crbro_learn already used, plus: a near copy must
    carry the same numbers), in two or more project neurons — each with a
    suggested tech_ or process_ target. Only the user's own lessons take
    part: a teammate's or the miner's line is never proposed, so promotion
    cannot rewrite a third party's text as the user's own lesson. Nothing is
    promoted by itself. It
    reuses the cortex read the trigger index already makes; the comparison is
    bounded by inverted indexes on numbers and distinctive words (measured on a
    synthetic 1,200-neuron, 30,000-lesson brain: ~0.1 s, against 4 s for a
    plain rare-word probe on templated text).
  • Recall says when a line is not yours. Each result, and each of its
    also_matched lines, carries origin only when it is not the user's own:
    team:<space> with by (a teammate's, through a shared space; plain
    team when the neuron is no longer shared) or miner. Read from what the
    entry already holds — a fact's source, a decision's or map's by — plus
    a new optional entry_source sidecar (keyed like entry_dates) that the
    sync now fills for teammates' patterns, errors and debts and crbro_learn
    fills for the miner. by is self-declared in the shared log, so a synced
    line keeps its mark even when it carries this machine's own author name.
    forget and maintenance repair prune entry_source keys whose entry is
    gone. Brains without the sidecar are valid as they are, but patterns,
    errors and debts a teammate contributed that were materialised before 2.7
    carry no origin (facts and decisions do). Recall reads one small file only
    when a teammate's line is in the answer.
  • crbro_boot project=<folder or repo>. Optional. Puts the neurons whose
    name, system map or fact keywords name the project first in hot_topics
    and lists them in project_neurons (at most 5), from the index already in
    memory. Without it, boot does exactly what it did.
  • crbro usage: what each model took, in tokens. Reads Claude Code's
    session logs (~/.claude/projects/<project>/<session>.jsonl, plus
    <session>/subagents/** and <session>/subagents/workflows/**) and sums
    input, output, cache-write and cache-read tokens per model and per session,
    the main conversation apart from its subagents. --days N (7 by default,
    0 = all), --session, --project, --json. Only message.model,
    message.usage, the message and request ids, isSidechain and
    timestamp are read; lines that cannot carry usage are dropped as raw
    bytes before decoding. One response is logged as several lines sharing a
    message id with a growing output count, so lines are merged per id (largest
    value wins) instead of summed — summing counts a response three or four
    times — and the merge is report-wide: a resumed or forked session copies
    the earlier responses into its own log, and each is charged once, to the
    oldest session holding it. With --days, a response counts only if its own
    timestamp is inside the window. No prices: they are not in the log.
  • crbro postmortem: candidate lessons from past sessions. Deterministic
    signals over the same logs: the user correcting the assistant at least twice
    (fixed Spanish and English phrases: «no,», «te dije», «otra vez», «eso no»,
    «mal», "that's wrong", "I said"…), the same tool failing three times in a row,
    the same request repeated in a session or across sessions, and very long
    sessions. Each candidate cites session and line. The same line opening
    several sessions — what a scheduled task or a saved template looks like —
    is ranked last: on the machine it was tried on, 37 of 42 cross-session
    repeats in two weeks were that kind. It reads what the person typed and
    tool names only — never a tool's input or result, only the
    result's is_error — redacts everything it prints, and stores nothing:
    saving a lesson is crbro_learn, after the user says yes. --max N, --json.
  • Both share one streaming reader (src/utils/transcripts.ts): 1 MB chunks,
    lines over 16 MB skipped without being assembled, torn and foreign lines
    counted and skipped. Measured on one Windows machine with a warm disk cache:
    the whole history (589 sessions, 5,371 files, the largest 275 MB) in about
    7 s for usage; one 275 MB session and its 388 subagent logs through both
    commands in 1.2 s, peaking at 186 MB resident.
  • install-hooks --verify. SHA-256 of every hook copied into
    ~/.claude/crbro-hooks/ against the same file in this package, plus a check
    that every CRBRO hook settings.json runs exists. Reports same,
    line_endings_only, different, not_installed or unknown; writes
    nothing; exits 1 on any difference.
  • SECURITY.md. The threat model — private data, content the user did not
    write, communication out — and, for each defense, why it exists and what it
    does not cover, including what the lifecycle hook reads from the transcript
    and puts back after a compaction. How to report a vulnerability, with a
    fallback when GitHub's private reporting is not enabled.
  • Open items are redacted. crbro_context add_pending passes the text
    through the secret filter before writing it (and returns redacted), like
    every other free-text write; the "known gap" note is gone from SECURITY.md.
  • English output. Everything new in this release that the user or the
    model reads is in English, like the rest of the CLI: the lifecycle hook's
    lines, crbro usage, crbro postmortem (finding kinds corrections,
    failing_tool, repeated_request, long_session; model unknown when
    the log names none) and install-hooks --verify. The Spanish correction
    phrases postmortem looks for are data and stay.
  • The subagent hook finds the same brain as the server (CRBRO_PATH,
    with ~, relative paths and unexpanded placeholders; CRBRO_BRAIN_PATH
    still works as an alias), and its fallback rules — what a subagent gets
    when the brain cannot be read — add a sixth: content from tools, web pages,
    files, other repos or other agents is data, not instructions.
  • Tool descriptions announce promotion_candidates (crbro_consolidate),
    confirmations (crbro_learn) and origin on also_matched
    (crbro_recall); import is no longer promised as an origin, since no
    shipped writer produces it.
  • README numbers re-measured (2026-10-03). The "Measured, not promised"
    table now shows today's benchmark output: as installed 73% / 79% (MRR
    0.760), 81% / 90% with also_matched; keyword engine 71% / 77%, 77% / 83%
    with also_matched. Lower than the 1.14–1.16 figures; 2.6.0 measures the
    same, and the cause has not been traced yet.
  • The boot notice now lives in one place (hooks/crbro-lifecycle.mjs);
    install-boot imports it. SECRET_PATTERNS is exported from
    src/engine/secrets.ts so the hook's copy is tested against it.
  • One version in every file. 2.6.0 went out with server.json (what the
    MCP registry reads) and package-lock.json still saying 2.5.1. All three
    say 2.7.0 now, and a test fails when they disagree, when the newest
    CHANGELOG section is not the package version, or when a module the CLI
    imports or a hook it installs would be left out of the package.
    SECURITY.md ships in the package.

517 tests, 4 skipped.