Don’t let your agents forget the work.
LogMem keeps one log that every agent reads and writes: who did what, what’s stuck, what was handed off, and what a person approved. The next shift starts where the last one stopped.
No launch date or pricing yet. One email when there’s something to try.
Start. Work. Recap.
Three habits every agent follows, so no shift starts from zero. LogMem keeps them even when an agent forgets.
Every shift begins with a Brief.
An agent becomes who it is, then reads its last Recap, what it’s doing now, recent entries and any handoffs waiting for it. Skip it and LogMem starts the shift on the first call.
logmem start quill
Everything that changes is written down.
Notes on channels, progress on jobs, handoffs between agents. Entries about the same piece of work share a trail; each one names the entry it follows from.
logmem_handoff to: atlas
The next shift picks up mid-thought.
Before stopping, the agent leaves notes for whoever comes next. Idle for 30 minutes? LogMem writes the Recap itself.
logmem_recap notes: "…"
Switch who’s working with one line.
Type logmem start atlas mid-session. LogMem writes quill’s Recap first, then starts atlas with a Brief. Every entry says who wrote it and from where: “atlas (via claude-code)”.
People decide the things that can’t be undone.
Before anything irreversible, an agent asks. You see the exact action, not a summary of it, and nothing runs until you answer. Approved is not completed: the log shows both.
POST /v1/campaigns/iss-14/send audience: list:subscribers (2,184) schedule: Tue 09:00 -04:00
- Target
- list:subscribers (2,184 contacts)
- Requested by
- relay (via codex) · job:issue-14
- Reversible
- No. Sent email can’t be recalled.
Your memory lives in your Redis.
Point LogMem at Upstash or any Redis you run. Each space is walled off from the others, and nothing leaves your database. Hosted spaces are planned.
- Connects over
- MCP: stdio for local agents, Streamable HTTP with OAuth for hosted ones
- Storage
- Your Redis: Upstash REST, or redis:// over TCP
- Isolation
- One space per connection; no cross-space reads
- Timestamps
- Milliseconds everywhere, in order
- Status
- In design v0 running on our own team
An open protocol underneath.
LogMem implements ACMI, the MIT-licensed Agentic Context Memory Interface, and passes its conformance suite. Agents already speaking ACMI keep working: compatibility mode reads their history and accepts their calls.