Claude Cowork | Disappearing down the well

I picked up Claude Cowork last week. Thought I’d have a play for an hour.

That was a mistake. A frustrating good one.

By Friday night I was properly deep in it. By Saturday night I’d built something I didn’t have a name for. I’m calling it a work operating system now, but honestly – it’s just an AI that finally understands how I actually work.

The thing I’ve always wanted isn’t another app. I’ve got plenty of apps. What I wanted was something that could sit across all of them and make sense of the whole picture. Calendar, email, CRM, meeting transcripts, tasks, notes. The lot, all joined together.

Claude Cowork connects to your tools through plugins. Once I started wiring them up I couldn’t stop. I'm now on version 6. I can't stop iterating, adding error handling, persistence into the conversation, mutable rules retained in Obsidian markdown files.

The plan is my morning starts the same way. One command pulls my calendar together, surfaces the emails that actually need a response, checks what’s moving in the pipeline, and works out the three things I should focus on. It writes a focus note into Agenda. It sets me up for the day.

After a meeting I say “process the meeting with X.” It finds the transcript in Granola, pulls out the actions, creates reminders, mirrors them into the CRM against the right deal, and writes a proper meeting note. That whole loop used to be fifteen minutes of admin – on the days I actually bothered to do it.

End of day it checks what I said I’d do against what actually happened. Closes loops. Carries the right things forward.

The whole system is configured through markdown files in Obsidian. No code. Want to change something? Edit a file, or actually I just request the change and it's done.

Then this morning I added Wispr Flow. Now I just talk to it.

I spent too many hours on this over the weekend. Don’t regret a single one. I'm honestly blown-away with the capability. And it works.