What changed?

Assistants stopped starting from zero. Memory features carry context between sessions — preferences, projects, how you like things written — so the tool that needed re-briefing every morning increasingly doesn't.

That's a real improvement. It's also a change in what a chat is. A conversation that ends is ephemeral. A conversation that persists is a record — and records have properties conversations don't: they accumulate, they're retrievable, and they can be wrong in ways that stick.

Why is that worth thinking about now?

Because the cost of a bad memory entry compounds quietly, and the cheapest moment to sort it out is while the history is short.

Three things change once memory persists:

Mistakes become durable. Tell it something wrong in March and it may still believe it in September — and you won't see the belief, only its downstream effects. Advice subtly shaped by a fact you corrected verbally once, in a chat you've forgotten.

Convenience pulls you toward oversharing. The tool is more useful when it knows more, which is a genuine incentive to tell it more. Fine for working preferences. Different for client details, financials, or anything you'd need to be able to delete on request.

Your context becomes an asset with no backup. Six months of accumulated working context is valuable, sits somewhere you don't control, and — as anyone who has lost a machine knows — is exactly the sort of thing you don't think about until it's gone.

What should a one-person business actually do?

Three things. None takes long, and doing them early is worth far more than doing them well later.

Decide what memory is for, and write it down. Working preferences: yes — tone, formats, recurring structures, the shape of your business. Client identifiers, financial details, anything under a confidentiality obligation: no. That line belongs in your decision log so that in six months you know what you decided and why.

Read what it already remembers. Most people have never opened the memory settings. Open them and read the list as though someone else wrote it. You'll usually find one or two things you'd rather it didn't hold, and occasionally something factually wrong that has been quietly shaping answers for weeks.

Keep the important context in a file you own. The single most useful document — the one-pager describing your business, your customers and how you work — should live in your own folder and be pasted in, not merely remembered. This is the one-pager argument with a new reason attached: portability. A context you own moves between tools; a context the tool owns doesn't.

What's checkable here, and what isn't

Checkable: from 2 August 2026, EU AI Act transparency obligations apply — including telling people when they're dealing with an AI system, with machine-readable marking of AI-generated content following for existing systems from 2 December 2026 and a simplified route for smaller businesses. If a memory-enabled assistant handles anything customer-facing on your behalf, that's now a live consideration and not a future one. (Not legal advice — check your own position.)

Also checkable, and worth doing rather than assuming: your specific tool's data-retention and deletion terms. They vary between products and between tiers of the same product, and they change. Read the current page — don't rely on what was true when you signed up, and don't rely on this post.

Not checkable: whether persistent memory makes you more productive. That's your number, measured on your work, over a fortnight — minutes back per pound, same as any tool.

The one thing to do this week

Open the memory settings and read the list. Ten minutes, and it's the only way to find out what your assistant thinks it knows about you.

For the checks we run before letting anything remember on our behalf, the free 5-min read is here: The 10-Hour Audit.

Related Decodes

• Agents Got File Access in July — the reach question, of which memory is the quieter half.
• The Settings Page Nobody Opens — where to start.
• Automate the Task, Not the Promise — the week's hub.

TL;DR: Persistent memory turns a chat from something ephemeral into a record — which means mistakes become durable, convenience pulls you toward oversharing, and your accumulated context sits somewhere you don't control. Decide what memory is for and log that decision, read what it already remembers, and keep the important context in a file you own so it stays portable. Check your specific tool's current retention and deletion terms rather than assuming.