How to use Claude Cowork to turn a week of meetings into one review

Weeve author portrait

Dylan de Heer

How to use Claude Cowork to turn a week of meetings into one review

Of everything you can bolt onto Weeve, this is the setup we recommend first, because it requires no technical skill whatsoever. If you can choose a folder in a dialog box and type a paragraph, you're qualified.

The result: every Friday afternoon, a document appears in a folder on your Mac. It tells the story of your week in one paragraph, lists every decision you made and which meeting it came from, gathers all action items into a table with owners, and flags "dropped threads": questions that came up and never got answered. You'll read it in three minutes and know exactly where the week landed.

The two halves

Weeve records your meetings and writes the notes, entirely on your Mac. Every meeting becomes a small file containing the title, date, who spoke, and the summary. No bots join your calls; nothing goes to a server.

Claude Cowork is Anthropic's assistant inside the Claude desktop app (it launched in early 2026). Unlike a chatbot, it works directly with a folder you give it: it reads the files inside, plans multi-step work, and saves finished documents back. It also runs tasks on a schedule. Anthropic pitched it as Claude Code for everyone whose work isn't code, which translates to: the powerful stuff, without the terminal.

Weeve fills a folder with meetings. Cowork works on folders. That's the whole integration.

Step 1: Move your Weeve library somewhere sensible

Cowork asks you to pick the folder it may work in, so let's make that folder easy to pick. In Weeve, open Settings → Data & Storage and click Change folder. Create a folder called Weeve in your home folder and select it. Weeve moves everything and carries on saving new meetings there.

Your meetings now sit at Weeve → Users → (a folder with a long name, that's your account) → Recordings, one file per meeting.

Step 2: Create a Project and lay down house rules

In the Claude desktop app, create a new Project and point it at your Weeve folder. Projects carry standing instructions that apply to everything you ask inside them. Paste this into the instructions:

The Recordings folder contains one file per meeting. The "summary" field holds the meeting notes; "speakers" lists who was there by name. Only use files where "summaryStatus" is "ready", because anything else is still being processed. Treat the meeting files as read-only: never edit or delete them. Save everything you create into a "Reports" subfolder.

Two of those rules do real work. The "ready" rule exists because Weeve saves a meeting's file the moment recording starts and updates it as the transcript and summary finish, so Cowork must wait for the ready flag rather than reading half-finished meetings. The read-only rule keeps your meeting archive pristine; Cowork asks before deleting things anyway, but it costs nothing to say it twice.

Step 3: Ask for the review

Type this as a task:

Read all my meetings from the last 7 days. Create "Reports/Week of [date].md" containing: one paragraph telling the story of the week; every decision made, each noting which meeting it came from; all action items in a table with owner; and a "Dropped threads" section for questions that were raised but never resolved. Keep it under two pages.

Cowork shows you its plan, reads the files, and writes the document. The first run is your fitting session. Maybe you want decisions grouped by client, or the action items sorted by owner. Just say so and run it again.

Step 4: Put it on a schedule

Happy with the shape? Type /schedule and set it for Fridays at 16:00. Done. The weekly review now writes itself. One practical note: because this task reads a folder on your Mac, it runs on your Mac, which means Claude Desktop needs to be open at the scheduled time. If it isn't, the task simply runs the next time you open the app. Friday at 16:00, when you're at your desk closing out the week anyway, is a good slot for exactly that reason.

What else one sentence buys you

Once the Project exists, useful requests cost a sentence each:

"Read my last two weeks of meetings with Achmea and draft a progress update I could email them, in plain language with no internal shorthand." First drafts of client updates, assembled from what was actually said.

"I'm seeing Vincent tomorrow. Find every meeting he's been in, and tell me what's still open and what we discussed last time." This works because Weeve records who said what, and it works best when you take five seconds after each meeting to rename "Speaker 1" to a real name in the app. This workflow will make that a habit fast.

"Keep a running file called Reports/Decisions.md: add each new decision with its date and source meeting, and never rewrite old entries." One file that answers "when did we agree to that?" forever.

Read this before you schedule anything

Weeve's core promise is that your meetings are processed entirely on your Mac. This setup keeps Weeve's half of that promise intact and introduces a choice on the other half. Claude, the AI reading your files, is a cloud service: the content of the meetings it reads is sent to Anthropic to be processed. For many people and most meetings that's a fair trade for what you get back. Make it a decision rather than an accident: if certain clients or topics shouldn't leave your Mac, keep those recordings in a project you exclude, or simply don't point Cowork at them. For a fully on-device alternative, see our OpenClaw guide.

Why you might want one of the others instead

This is the only one of the five that never asks you to open a Terminal, and the only one whose output is a piece of thinking rather than a pile of filed artefacts. A weekly review reads your meetings and tells you what happened; the others move files around.

Pick differently if what you actually want is the moving of files. OpenClaw files each meeting as it lands, with no Terminal either. Claude Code does the same thing within seconds instead of minutes, and does require the Terminal. Codex skips scheduling altogether and lets you interrogate past meetings whenever the question comes up.

That's the entire setup: one folder change in Weeve, one Project in Claude, one paragraph of rules, one scheduled sentence. Friday afternoons just got a lot more honest. If weekly is too slow for how you work, the same idea runs every night in our Hermes digest guide.

Once the weekly review becomes a habit, the interesting question is what to do with everything it produces. We wrote up how we built an AI company brain at Weeve, which starts from exactly this review and turns it into an editorial process.

None of this works without a week of meetings on disk to review. Weeve's free Starter plan records and summarises 10 a month on a Mac, all of it on the device. Apple Silicon and macOS 14 or later required. If you are not on a Mac, the browser transcriber handles one recording at a time in the tab, which is enough to see whether the output is worth building a habit around.