How OpenHome Is Scaling Personalized Agents To 80,000 Users With Memorable.

OpenHome Case Study Architecture

OpenHome Superagent

TASK COMPLETION
100%
Flat retrieval70%
Procedural memory100%

Procedural memory against flat retrieval on the same tasks.

OpenHome Superagent

WASTED TOOL CALLS
0
Wasted tool calls0

Counted across every eval run.

OpenHome builds an open smart speaker platform. Each device exposes around 150 keyword-triggered abilities that route into one agent, the superagent. The hardware has little onboard storage.

150 Abilities, Each Starting From Zero.

Every ability re-derived its approach on each call. The more steps a request had, the longer the person waited in silence. A procedure written into the prompt was paid for on every call, by every user, whether the run needed it or not.

Built For A Device With Limited Storage.

Most memory products store a conversation in the cloud. OpenHome needed procedures that fit on the device, for an agent that acts on requests.

Before Memorable

FLAT RETRIEVAL
>Stores a transcript

Session logs sized for a chat history.

>Assumes cloud storage

Sized for a server, far above the storage budget of a speaker.

>Recalls preferences

Preferences carry across sessions. The steps of a task do not.

With Memorable

PROCEDURAL MEMORY
>Stores how things get done

The steps that finished the task and the result that proved it.

>Runs on the device

Fits the storage budget of a speaker.

>Finishes a task the same way twice

The same steps run again. No new plan is reasoned out.

"Most memory tools store what happened. Memorable stores how things get done. It watches an agent's own successful runs and turns them into reusable workflows, so the path an agent worked out once becomes a path it can follow."

Routing Daemon, Trace Flywheel, Superagent.

{ 01 }

Routing Memory Daemon

Sits on the device between the wake word and the ability it triggers. It checks for a stored procedure before the superagent starts reasoning.

wake word"play movie night"routing daemonon device, checks storeprocedurefound, replayedsuperagentreasons from scratch

100% Task Completion, Up From 70%.

100%

task completion with procedural memory, 70% with flat retrieval

0

wasted tool calls across every eval run

100%

live demo completion with memory on, 50% with it off

EVAL_LOG.JSONEval log
MetricBefore (Flat Retrieval)After (Procedural Memory)How it was measured
Task completion70%100%Same tasks, flat retrieval against procedural memory
Wasted tool callsPresent0Every eval run
Live demo completion50%100%8 live tasks, memory off then on

Try Memorable on your own agent

>npx memorable-cli@latest
># runs on the device, the store stays on your side

Case Studies From Design Partners.