The headline everywhere this week is that Claude Cowork finally remembers what you told it in chat. Memory shipped. Preferences persist. You stop re-explaining every morning that you want bullets and no preamble, and Anthropic gets to call context solved for another quarter.

Fine. I use Cowork. I’ll take it.

But “memory” is doing two completely different jobs in AI product copy right now, and the one that just shipped is the smaller of the two by a wide margin.

Two things wearing the same word

App memory is a durable store of what you typed into a chat box. Your tone preference, your team’s name, the client you keep asking about. It’s cheap to build and it makes the assistant feel less like a goldfish, which is a real improvement over the alternative.

Session context is something else entirely. It’s the state sitting in your Chrome at this exact second: the Salesforce tab where you’re authed as an ops admin, the Gmail thread you half-drafted, the internal billing panel behind SSO that has no public API and never will. None of that got typed anywhere. It’s not a preference you expressed. It’s who those servers currently think you are.

So the ceiling on app memory isn’t how much it stores or how cleverly it retrieves, but that everything in it arrived through a text box, which means it can only ever hold the parts of your work you bothered to describe out loud.

Recall isn’t access

Cowork can now remember that you like short replies. It still can’t open the tab where the reply has to go. Those are not the same problem and no amount of storage closes the distance.

The second step is where it falls apart

Say you ask Cowork to help you follow up with a stalled deal. Memory kicks in beautifully. It knows your company, it knows you write short, it knows you sign off with your first name only and hate the word “circling.” The draft comes back sounding like you, which is exactly what memory was built for and exactly what people are celebrating.

Then you have to go get the deal. Open Salesforce, find the opportunity, check the last activity date, read the two notes your AE left, copy the contact’s email, switch to Gmail, find the thread, paste the draft, fix the greeting because the draft assumed a name it never saw. Ten minutes of work that the memory feature does not touch, because every single piece of it lives behind a login the app has no relationship with.

The thing that actually finishes a task is rarely the preference you stated last Tuesday; it’s the cookie jar, the org you’re scoped into, the SSO session your IT team provisioned in March, and the fifteen tabs you left open because they’re all part of one job. Anthropic’s app can’t reach any of that, and it’s not an oversight. Cowork runs beside your browser, not inside it. We wrote about the same wall when Cowork landed on Windows and nothing about memory changes the geometry.

What would change it is an agent that reads the page you’re already looking at. That’s what Dassi does from the Chrome side panel: your session, your cookies, your existing login state, no OAuth handshake and no connector to configure. It sees the opportunity record because you can see it.

What memory can’t hold

  • Whether your session expired four minutes ago
  • Which of your three Google accounts is active in this window
  • The row you filtered down to in an admin table
  • That the vendor portal only renders the invoice after you click a tab
  • Anything behind a login your chat app was never given

None of these are exotic. They’re just Tuesday.

Same model, different plumbing

The funny part is that the model is not the bottleneck. Opus is Opus. The reasoning that drafts your follow-up is identical whether it runs in Cowork’s window or in a browser side panel, and if you’re on BYOK you’re literally calling the same endpoint with the same key. What differs is what gets handed to it before it starts thinking.

One version gets a memory blob of preferences you typed. The other gets the DOM of an authenticated Salesforce record and the Gmail compose window sitting next to it.

I’ve said before that an agent that can’t see your logins is guessing, and memory sharpens that rather than softening it, because now the guessing sounds much more like you.

Give it a few months and every assistant will have shipped memory, and the marketing will move on to whatever’s next while the login screen stays exactly where it is. Dassi’s bet is the boring one: be in the browser, use the session that’s already there, skip the part where you explain your job to a text box.