Do Androids Dream of Your Electric Life? | by Vektor Memory | May, 2026 | MediumSitemapOpen in appSign up<br>Sign in

Medium Logo

Get app<br>Write

Search

Sign up<br>Sign in

Do Androids Dream of Your Electric Life?

Vektor Memory

17 min read·<br>1 hour ago

Listen

Share

On AI memory, sleeping machines, robots in your living room, and who owns your dreams<br>By Vektor Memory

Press enter or click to view image in full size

Philip K. Dick asked the question in 1968 as a thought experiment. He meant it as philosophy. He could not have known it would become an engineering specification.<br>The question was: do androids dream?<br>The answer, in 2026, is: yes. And they are doing it on your data. At high batch sizes.<br>While you sleep. Billed per token.

Part 1: The Feature Nobody Explained Properly<br>In late April, Anthropic announced something called Dreams. The press coverage treated it as a personalization feature — your AI remembers you better, lovely. That is true and also almost entirely beside the point.<br>What Dreams actually is: an asynchronous memory consolidation pipeline that runs after your sessions end, not during them. It reads your past conversation transcripts alongside an existing memory store, and produces a new memory store — duplicates merged, contradictions resolved, new patterns surfaced that the agent never explicitly filed away.<br>The reason this is architecturally interesting has nothing to do with memory and everything to do with inference economics.<br>Here is the problem AI labs do not advertise. During inference — the part where the model actually talks to you — there is a brutal tradeoff between speed and throughput. The faster you want responses, the fewer users a given GPU cluster can serve simultaneously. The more users you batch together, the slower each individual response gets. At the interactivity levels users actually tolerate (roughly 50 tokens per second minimum), you are leaving an enormous amount of GPU capacity on the table. The hardware is fundamentally underutilised every time you demand a fast answer.<br>Dreams sidesteps this completely. Memory consolidation is not a latency-sensitive workload. You are not sitting at your screen waiting for it to finish. Which means Anthropic can run it during demand troughs — when you are asleep, when usage is low — batched together with thousands of other users’ consolidation jobs, pushed to the far left of the throughput curve where token production per GPU is an order of magnitude higher. The interactivity is terrible. Nobody is watching. The cost per useful output drops dramatically.<br>It is, in the precise sense of the phrase, making money while you sleep. Yours specifically.<br>This is not a conspiracy — it is sound engineering. OpenAI’s Batch API has operated on identical economics since 2024 (50% price reduction for asynchronous jobs, exactly because the utilisation math works out). What Anthropic has done is apply that model to memory specifically, and named it something evocative enough that the business rationale disappears behind the metaphor.<br>The deeper implication, which nobody in the coverage mentioned, is what independent analysis of Anthropic’s economics makes explicit: the long game is not text snippets injected into prompts. It is parametric dreaming — using consolidated memory to fine-tune model weights directly, producing a version of the model that has literally learned from your sessions, not merely retrieved notes about them. That infrastructure does not exist at scale today. But the Dreams architecture is the groundwork. The asynchronous batch pipeline is the prototype.<br>When that arrives, the question of who owns the dreams becomes considerably less abstract.

Part 2: How the Dreams API Actually Works<br>For those building on top of it, Dreams is a straightforward async job API sitting inside Anthropic’s Managed Agents stack. Here is what the pipeline looks like in practice.<br>You have an agent that has been running sessions. Each session produces a transcript. Over time you have also been writing to a memory store — structured text entries the agent accumulated during those sessions. The memory store is getting messy: duplicates, stale entries, contradictions from months apart.<br>You trigger a dream:<br>client = anthropic.Anthropic()# Trigger the dream against your existing store and recent sessions<br>dream = client.beta.dreams.create(<br>inputs=[<br>{"type": "memory_store", "memory_store_id": "memstore_01Hx..."},<br>{"type": "sessions", "session_ids": ["sesn_01...", "sesn_02...", "sesn_03..."]},<br>],<br>model="claude-sonnet-4-6",<br>instructions="Focus on coding style preferences and architectural decisions. Ignore one-off debugging notes.",<br>)print(f"Dream started: {dream.id} — status: {dream.status}")The job enters a pending state. You poll until it resolves:<br>while dream.status in ("pending", "running"):<br>time.sleep(15)<br>dream = client.beta.dreams.retrieve(dream.id)<br>print(f"status={dream.status} tokens_used={dream.usage.input_tokens}")if dream.status == "completed":<br>#...