AirMemo

01 — The layer

Everyone's building smarter agents. We're building the layer that keeps them from acting on yesterday.

Authorized memos land in an agent's context on the next turn — with a receipt that proves what each agent saw.

Install the hookRead the mechanism

02 — The problem

Your agents are acting on yesterday.

Whatever is already in a session reads as current, and every agent acts on it that way. Nobody governs the shelf.

0 of 6 — frontier models, confidently wrong, reading zero files

03 — The mechanism

Next action, not current sentence.

A tiny hook rides the lifecycle events your agents already expose. The memo lands in session context — prompt-visible on the next turn, never mid-conversation.

queued → injected → receipted → expired

04 — One memo, four vendors

No enterprise fleet is single-vendor. Neither is AirMemo.

Four adapters, one delivery contract — and the hedge is not a promise, it's a fixture.

Claude Code · Codex · Copilot · Gemini CLI

05 — The receipt

Proof, not pixels.

Every delivery writes an append-only, signed receipt — audit evidence, billing meter, and the acquisition metric: agents under management.

[AIRMEMO · authorized · memo_4821]

06 — Install

One line, then enroll.

The hook is a single static binary — no runtime, no daemon. Held until the v0.1.0 public release.

airmemo-hook enroll --org YOUR_ORG --platform claude

Install the hookRead the mechanism →