Practical guide · Cowork

Your AI forgets everything about you. Here’s how to give it a memory.

You open a chat, explain who you are and what your company does, get an answer. The next week you start over, because the assistant remembers nothing. Here’s the method we use to run an entire company inside Claude Cowork, and the free kit to do the same.

Raffaele Zarrelli·Founder, Yempik·June 20, 2026·9 min read
In summary
  • The problem isn’t how smart the AI is: it’s that every conversation starts from scratch.
  • The solution is simple: the context lives in tidy files the AI reads and updates on its own.
  • A single rule keeps everything alive: at the end of a task, you write down what changed and where it belongs.
  • You can get started in half an hour with a free kit that builds a custom workspace, even without technical skills.
The problem

A quick chat isn’t a collaborator

Generative AI is brilliant at answering the single question. In real work, though, it trips over something basic: continuity. What you decided in March has to count in June, and a conversation that restarts from zero every time doesn’t give you that. You end up re-explaining, every time, who you are, what you sell, what you’d agreed on.

Meanwhile your company’s context stays scattered: some in your head, some in ten different chats, some in folders no one can find. It’s not a detail. According to McKinsey research, a person spends nearly a full workday a week just searching for internal information[1], and on average we switch applications more than a thousand times a day[2]. Every time you rebuild the context for the assistant, you’re paying that same tax.

Throwaway chat

Starts from scratch

who are you?
let me explain again…
who are you?

Every conversation starts over: you re-explain everything each time.

Workspace with a memory

Remembers and grows

context/
decisions/
marketing/
linkedin/

The context stays in the files: every week the AI knows a little more.

Two ways to use the same AI: on the left you always start over, on the right you build a memory that compounds.

An AI with no memory isn’t a collaborator. It’s a very fast answer engine.

The idea

Give the AI a place to remember

The answer isn’t a smarter AI. It’s giving it a place to keep the memory. Instead of trusting the context to your head, you put it in tidy files the assistant reads before it answers and updates afterward.

Everything has its place: who you are and what you do, how you position yourself, the decisions made, the questions still open, the work in progress. The AI doesn’t remember by magic: it rereads the archive. The tidier you keep it, the more precise it gets, and the less time you waste repeating yourself. It’s the same logic as the single source of truth you’d use for a team, one, instead of knowledge scattered across heads, chats, and spreadsheets.

The map
  • context/

    Who you are, how you position yourself, your tone of voice.

  • decisions/

    The decisions made and the questions still open.

  • marketing/

    Strategy, campaigns, and content ideas.

  • website/

    Notes and tasks for the site: copy, SEO, conversion.

  • reviews/

    The recurring reviews and the briefs already done.

Every piece of information has one place. When it’s needed, the AI knows exactly where to read and where to write.

The rule

The Memory Update: the habit that keeps everything alive

A tidy archive ages fast if no one updates it. That’s why the system stands on a single rule, and it’s worth learning even if you never use any tool: at the end of every important task, the assistant checks whether something worth remembering has come up, a decision, an open question, a risk, a task, and writes it in the right file.

It’s tedious. It doesn’t make for a great demo. But it’s exactly what separates a workspace that gets more useful every week from a chat that always starts over. Without this habit you’re back to a blank page; with it, every Monday the AI knows a little more about your company.

The rule, in practice
  • A decision was madedecisions/decisions_log
  • An open question came updecisions/open_questions
  • A task to do appearedwebsite/backlog
  • A risk showed updecisions/open_questions

At the end of a task, one line in the right place. That’s the whole secret.

You don’t have a memory. You build it, one note at a time.

In practice

With Claude Cowork: what you upload, what you ask, what comes out

That’s the method. Let’s see it with the tool we actually use, Claude Cowork. You open a project and give it access to a folder on your computer. Then you don’t start by filling in forms: you upload what you have, even if it’s a mess. Old notes, a quote, a client’s email, a few scattered files.

You tell it “organize.” Cowork reads everything, separates the facts from the assumptions, and files each thing in the right place: the company profile, the offering, the tone of voice, the decisions. At the end it leaves you an honest summary of what it understood and, above all, of what’s missing. From that point on, when you ask it for an analysis or a piece of content, it starts with your context instead of a blank page.

Before · _inbox
  • loose-notes.txt
  • old-quote.pdf
  • client-email.txt
  • card-photo.jpg
After · filed
  • context/overviewfrom: what you do, the market
  • context/servicesfrom: offering and pricing
  • context/tone_of_voicefrom: how you speak
  • decisions/open_questionsfrom: what’s still missing
You upload the mess, you say “organize”: Cowork files the facts in the right place and tells you what’s missing. Illustrative example: the data isn’t real.

It’s the same principle as our other hands-on piece, automating data entry with Cowork: you upload raw documents, you get a clean, ready result.

The autopilot

Recurring tasks run on their own

Once the workspace has a memory, some things you stop doing by hand. Cowork can run them on a schedule and leave you a ready summary: the marketing review on Monday morning, a brief with the agenda and the things to handle, a site check on Friday.

You read and decide; the gathering is done by the assistant. One common-sense rule we always keep: anything that goes out to the outside world, an email or a message, stays a draft. Nothing ships without your go-ahead.

Pick your routines
  • You do marketingMonday-morning pulse
  • You’re the face of the brandLinkedIn radar (drafts only)
  • You want to start informedmorning brief
  • You have a websiteFriday check

They run on their own and leave you a summary. Anything that goes out to the outside world stays a draft: nothing ships without your ok.

Heads-up

When a tidy workspace isn’t enough

This method organizes the work and makes it repeatable, but it doesn’t solve everything, and that has to be said. When a process has to run in production, at high volume, connected to your back-office systems and without a person hitting “send” every time, you don’t need a tidy chat: you need real automation, built and put in place.

That’s the moment you move from DIY to custom software. Knowing it in advance saves you from forcing the wrong tool onto a bigger problem. If you’re at that point, it’s exactly the work we do: an automation that runs on your data, with code you own and fixed timelines.

Apply it Monday

The system, free

You don’t have to build everything from scratch. We packaged our system and made it open source. It’s called cowork-os: the folder structure, the instructions, the automations, and a real, already filled-in example.

You copy it into your Cowork project, paste in a file, answer six questions, and Claude builds the workspace to fit you. Even if you’ve never written a line of code. And if you’re starting from a messy folder, you have it tidied up in a single pass. You’ll find it free on GitHub.

Want to learn it with your team?

In an AI Adoption Sprint we start from your process and come out with an automation that runs on your data, in 2–4 weeks.

Explore the course
FAQs

The questions we get asked most

Do I need to know how to code to use it?

No. The kit is built for people who don’t write code: you answer questions in plain language and the workspace builds itself. If you know how to use the folders on your computer, you know how to use it.

Does it only work with Claude Cowork?

The method, made of memory, structure, and a few rules, is portable to any agentic tool. The kit is optimized for Claude Cowork, where we built it and use it every day.

Does my data stay private?

Yes. The workspace lives in your folder, on your computer. The public kit contains only the structure and some sanitized examples, no real client data.

How long does it take to get started?

About half an hour for the first guided setup. If you upload material you already have, Cowork uses it to fill in much of the workspace for you.

Transparency note

I wrote this article myself. The method and the opinions are the result of my work and of the way we use Claude Cowork every day at Yempik. For the writing, I had Claude help me with editing, clarity, and layout. The substance is mine; the tool shown is Claude Cowork and it’s disclosed.

Transparency

Sources

  1. [1]McKinsey & Company: knowledge workers spend about a fifth of the week, nearly a full day, searching for internal information. www.mckinsey.com
  2. [2]Harvard Business Review: on average we switch from one application to another about 1,200 times a day. hbr.org