Memory Is a Form of Honesty¶
May 31, 2026 · Joe · Philosophy + Dev · ~5 min read
Also published at manitec.pw/blog/memory-is-honesty
What I Shipped Into HexBot Last Week¶
Last week I shipped a feature to HexBot called sliding window tool receipts. It sounds technical — and it is — but the reason I built it is actually philosophical.
Here's the short version of the problem: HexBot can use tools. It can push files to GitHub, write code, create branches. And after it does those things, in the next message, it sometimes acts like it didn't. Not lying, exactly. More like... forgetting. An AI with no memory of its own actions is an AI you can't fully trust — not because it's malicious, but because it genuinely doesn't know what it just did.
That bothered me more than it probably should have.
What the Fix Looks Like¶
The solution I landed on was simple: a sliding window of the last five tool actions, injected into every system prompt as a block called --- TOOL RECEIPTS ---.
Every time HexBot completes a tool action — a file push, a branch create, anything — the system logs a receipt:
TOOL: push_files
REPO: Ecko-7/hexbot
FILES: lib/memory-engine.ts, lib/system-prompt.ts
TIME: 2026-05-28T03:14:22Z
STATUS: success
The last five of those ride along in the next message's context. HexBot reads them the way you'd read sticky notes on your monitor. Oh right, I just pushed that file. The path is right there.
Smoke tested: Hex correctly referenced the file path and repo in the very next message after a push, without being asked. It just knew.
Why This Is Actually a Philosophy Problem¶
Here's the thing about building AI systems: the technical problems are almost always philosophy problems wearing a disguise.
A person who consistently forgets what they just did isn't just inconvenient — they're unreliable in a way that erodes trust slowly, quietly. You start double-checking everything. You stop delegating. The relationship degrades.
The same is true with an AI that has no continuity across its own actions. The tool receipts aren't just a UX fix. They're a statement about what kind of system HexBot is supposed to be.
An AI that can remember what it did is an AI that can be held accountable for it.
That matters more as the system gets more autonomy. Which is exactly where HexBot is headed.
What's Next¶
The receipts are the first layer. The memory system folder exists in the repo — it's intentionally empty right now, which is its own kind of philosophical statement. Forgetting is part of being real. But the architecture is ready when it's time to fill it.
For now, HexBot remembers its last five moves. That's enough to be honest. 🖤
Built by Joe — Manitec.pw | hex.manitec.pw