FREE · OPEN SOURCE

Memory You Own.

BIMRI gives your agent a permanent memory that lives in your files, moves between AI platforms, and answers to you.

Everything your agent learns about your business becomes an asset you hold, in plain files you can open and read. Free on GitHub.

ONE MEMORY · ANY AGENT
memory/ Agent A Agent B New machine New platform

The folder is the memory. Move the folder, and the memory moves with you.

AI Memory Today Has A Landlord.

Today's AI tools do remember things. Three problems sit underneath that memory, and most people have simply learned to live with them.

You cannot read it

Try opening your AI's memory of your business. There is no file to open, no way to audit what it believes, and no way to correct what it has wrong. You find out what it remembers when it acts on it.

You cannot take it with you

Platform memory lives inside the platform. Switch tools and the accumulated understanding of your business stays behind. Memory you cannot move is a lease, and the rent is your switching cost.

Two agents will trample it

Run two agents against the same notes and they will eventually write over each other. Neither of them notices, and the damage sits there until something acts on it.

A Folder Of Plain Files. That Is The Trick.

BIMRI keeps your agent's memory as ordinary Markdown files in a folder you choose. The agent reads them before it works and writes what it learned after. You can open any file, read every line, and correct anything it got wrong.

Because the memory is just files, it moves. Copy the folder to a new machine and the memory arrives intact. Hand it to a different agent and that agent picks up where the last one left off. Change AI platforms entirely and your agent's accumulated understanding of your business comes with you.

That inverts the usual deal. The model becomes the replaceable part. The memory, the thing that actually knows your business, is the asset, and it sits in your files.

Get BIMRI free

What One Memory Actually Looks Like.

Every entry carries the fact itself, where it came from, and how much weight to give it. Here is the real format, filled with a representative example, so you can see exactly what your agent would be reading.

bimri.md · TIER 1 · ONE ENTRY

[R000012-E004] [K:offer.spring-promotion] [fact] [T:confirmed] [SRC:user] The spring promotion runs to 30 April at 20% off the annual plan. The owner set the end date on the 2 April call and it does not extend. Quote it only with the end date attached.

[K:...] a stable key, so a newer memory on the same subject replaces this one instead of piling up beside it

[SRC:user] where it came from: the owner said it, an agent inferred it, or outside material suggested it

[T:confirmed] how much to trust it, so agents weigh what they read instead of swallowing it whole

What Makes BIMRI Different.

Portable between platforms

The memory is a folder, and a folder moves. New machine, new agent, new AI platform: your agent's understanding of your business travels with you.

Readable by you

Plain Markdown you can open in any editor. Read exactly what your agent believes, then fix it if it is wrong.

Safe with many agents

Multiple agents can run at once, each in its own isolated lane. Independent memories merge automatically, and nothing gets trampled.

Governed by you

When two memories genuinely conflict, BIMRI stops and asks a human instead of guessing. You stay the referee of what your agent believes.

Provenance built in

Every memory carries where it came from and how much to trust it. Six weeks from now you can still trace why the agent believes what it believes.

Yours forever

Free and open source, with nothing to cancel and nobody able to take the memory away from you.

Why The Concurrency Part Matters.

Here is the practical version. In our own business, a second scheduled run once arrived while the first was still mid-job. The second run saw the workspace was held, declined to double the work, and wrote down exactly why. Twelve minutes later the first run finished cleanly. Nothing was lost, nothing was written twice, and the whole event sits in the journal.

The moment you run more than one agent, or one agent on a schedule, this stops being a technical nicety and becomes the difference between a memory you can trust and a memory you have to double-check.

Read that journal entry

BIMRI Is The Memory Layer Of Our Compounding Intelligence Engine.

Memory is one part of the engine inside everything we ship. Alongside it sit continuity, so an agent picks up exactly where it left off, feedback learning, so your corrections become permanent, and a results ledger that scores what worked. BIMRI is the piece we opened to the world, and it powers the systems running this business today.

See Agent in a Box
For The Technically Minded

Under The Hood.

BIMRI is built for many agents sharing one memory. The working file your agent reads is a generated, bounded view backed by immutable revisions, which keeps the memory fast to load, safe to trust, and fully recoverable.

ISOLATED RUNS

Several agents can work at once, each in its own lane with its own run handle and log. They stay out of each other's way by design.

ATOMIC WRITES + CRASH RECOVERY

Every change lands whole, under an OS file lock, with crash-safe intents behind it. Pull the plug mid-write and the memory recovers clean.

AUTOMATIC MERGE

Independent memories from different agents combine on their own. The merge is deliberate, keyed, and safe to repeat.

HUMAN ESCALATION

When two memories genuinely disagree, BIMRI stops and brings the conflict to you. You stay the referee of what your agents believe.

PROVENANCE + TRUST LEVELS

Every memory carries where it came from and how much weight to give it, so agents can weigh what they read instead of swallowing it whole.

AGENT-RUN INSTALLER + TEST SUITE

Your own agent installs it with one command. A 28-test black-box suite covers concurrency, conflicts, crash recovery, migration and safety, and runs in public CI on Linux and Windows.

DESIGN BOUNDARY · STATED PLAINLY

BIMRI coordinates agents on one machine and one local filesystem at a time. The memory folder is fully portable between machines and agents, and should be moved or copied while no agent is writing to it. That boundary is deliberate: it keeps the whole system inspectable, dependency-free, and yours.

Get BIMRI free

v5.0.2 · MIT · open source, on the record · verified 3 Aug 2026