In Pursuit of Agentic AI Workspace

What changed when I gave AI a home inside my actual work.

I want to tell you about something that’s been bugging me for months.

I was using AI every single day. ChatGPT, Claude, NotebookLM—the whole stack. And I genuinely felt productive. Ideas were flowing. Content was getting drafted faster than ever. I was convinced I’d figured this thing out.

But every session ended the same way.

Command+C. Command+V

My workflow looked like this:

• Brainstorm newsletter ideas in ChatGPT → copy to Notion.

• Research topics in NotebookLM → manually pull insights into Docs.

• Draft content in Claude → copy to Substack editor.

• Generate social posts → copy to a scheduling tool.

• Analyze what’s working → screenshot and paste into my tracking spreadsheet.

I was doing this dance every day without questioning it.

Then one afternoon, I caught myself mid-paste and just... stopped.

I looked at what I was actually spending my time on. I wasn’t thinking or creating. I was just deciding where things should go, how to format them, what context to add by hand, and how to connect this output to everything else I’m working on.

I was a human API—the glue between AI outputs and the places where my real work lived. AI was supposed to free me from mechanical busywork. Instead, it created a different kind.

For months, I’d been stuck on the wrong question:

“Which AI tool should I use?”

Then I asked a different one:

“Where does my AI actually live?”

My AI lived in a chat window. My work lived in Google Docs, Notion, Slack, email, and five other places. I was the bridge between them—every single time.

I started calling this the “copy-paste tax.” And I’d been paying it for months without noticing.

If any of that sounds familiar, I think you’ll relate to what I’m about to share.

The truth was I didn’t realize how stuck I was until I experienced what comes next.

What it actually feels like when AI doesn’t just help you think—but can execute inside the places where your work lives.

When you go from being the middleman copying outputs between tools to directing AI that can read, write, and act across your entire workflow.

I’ve been calling this an “agentic AI workspace.” Not just AI that answers questions—AI that can act on your behalf, in the places where your work actually happens.

And once I experienced it, I couldn’t go back.

Let me show you what I mean.

The Three Levels of AI Integration

When I started mapping out how people actually use AI, I noticed a pattern. There are roughly three levels—and most people are stuck at the first one without realizing there’s anything beyond it.

Level 1: The Chat Window

This is where most of us start. You open ChatGPT, Claude, or Gemini. You ask a question. You get an answer. Then you take that answer and manually put it somewhere useful.

The AI is helpful. But it has no idea where your work lives, what you did yesterday, or what you’re trying to accomplish this week. Every conversation starts from scratch. Every output requires you to do the last mile.

This is fine for quick questions. But if you’re trying to run a business, manage projects, or produce content consistently—you hit a ceiling fast.

Level 2: AI With Access

This is the shift that changed things for me.

Instead of AI that lives in a chat window, you start using AI that can actually read and write inside your work environment.

There are a few ways this is happening right now:

1. Google’s approach: Gemini is already woven into Gmail, Docs, Sheets, Drive, YouTube, and NotebookLM. If you live in Google Workspace, your AI can already summarize email threads, draft responses, analyze spreadsheets, and pull research—without you ever leaving the tools you’re already in.

2. Claude’s approach: MCP (Model Context Protocol) lets you connect Claude to your email, calendar, Google Drive, project management tools, and local files. Claude Code takes it further—it can read, write, and execute across entire file systems and repositories.

To be honest, this is where OpenAI has lost me for a while. They don’t have strong multi‑app integration like the other two. I know they have the app store, but those don’t really change how I work.

The difference from Level 1 is simple but significant: AI that has edit access to where your work actually happens. You stop copying outputs out of a chat window. The AI puts things where they need to go.

Level 3: The Agentic AI Workspace

This is where it gets interesting—and where I’ve been spending most of my time with Claude Code.

Level 2 gives AI access to your tools. Level 3 is when your AI can chain actions together across those tools without you orchestrating each step.

Here’s the litmus test I use:

“Can your AI read your meeting notes, draft a follow-up email, update your project tracker, and flag what needs your attention—without you copy-pasting between any of those steps?”

If you’re still the one connecting the dots between tools, you’re at Level 2. If AI can move through your workflow the way you would—reading context from one place, acting on it in another—that’s Level 3.

And this is where things are moving fast.

Notion just entered this space. Last week, they launched custom AI agents that can run autonomously inside your workspace — on a schedule or triggered by events, without you prompting them. You describe a job in plain language, and the agent handles it: triaging tasks, compiling status updates, answering team questions from your internal docs, pulling feedback from Slack, routing work across projects. It connects to Slack, email, calendar, Figma, Linear, and more. For teams that already live in Notion, this is a serious option — your project management tool just became an agentic workspace overnight.

Claude Cowork is another path worth knowing about. Anthropic recently released it as a less technical alternative to Claude Code. Same idea — AI that can read and write your local files, break down multi-step tasks, create spreadsheets, draft reports — but without needing a terminal. If Claude Code feels too developer-oriented for you, Cowork gives you the same agentic capability through the regular Claude desktop app. I wrote an in‑depth guide on Claude Cowork if you want to go deeper.

We’ve now reached a level of AI integration where it can act across your entire work environment, not just answer questions in a chat. The question is whether you’re taking advantage of it.

I’m not going to pretend I’ve fully arrived here. I’m somewhere between Level 2 and 3, and it’s an ongoing process. But even partial progress has been transformative (thanks to OpenClaw!)

Here’s what that looks like in practice.

What Changed For Me

I’ll give you two examples from my own life — because this shift didn’t happen all at once. Instead, it happened in two phases, and each one showed me something different about what an agentic AI workspace actually means.

My Newsletter: From Scattered Tools to One Repository

For months, my newsletter operation was scattered across five or six tools. Ideas in Notion. Drafts in Google Docs. Research in NotebookLM. Social posts created separately. Performance data in a spreadsheet I’d check once a week and forget about.

None of these tools talked to each other. I was the one holding all the context in my head, manually connecting the dots every time I sat down to work.

Then I made one decision that changed everything: I moved my entire newsletter operation into a single repository.

Everything. Published posts, drafts in progress, content ideas, social media archives, writing guidelines, performance data, daily brain dumps, research notes. All of it, in one place, organized in folders.

And then I pointed Claude Code at it.

I’ve written before about how I turned Claude Code into my personal AI operating system for writing and research—and I genuinely mean it when I say it’s been the single biggest shift in how I work with AI.

Here’s why.

Claude Code doesn’t work like a chatbot to answer your questions. It’s an agent. It operates inside my file system. It can read every file in my repository, understand the relationships between them, and write outputs directly where they belong. No copy-pasting. No switching tabs. No reformatting.

• So instead of “Claude, help me brainstorm ideas” followed by pasting into a separate tool—I say: “Read my top-performing posts and my writing guidelines, then draft social variants that match my voice.” And it writes them directly into the right folder.

• Instead of manually checking what content is working—I say: “Look at my performance data and tell me what patterns you see.” It already has the context.

But the part that really surprised me was when I connected Claude Code to NotebookLM through MCP. Now I can do deep research without ever leaving my working environment. I’ll feed sources into NotebookLM, and Claude Code can pull those research insights directly into my drafts and notes—no more alt-tabbing between a research tool and a writing tool, trying to hold everything in my head.

That combination—Claude Code for execution, NotebookLM for research, both accessible from the same environment—is what finally made the “agentic workspace” idea feel real for me. My research feeds my writing. My writing feeds my social content. My performance data feeds my next topic decision. And none of it requires me to be the one carrying context between steps.

If you want the full technical walkthrough, I wrote a complete Claude Code implementation guide.

My Productivity System: From Organized to Opinionated

The newsletter was the first domino. But the second one changed how I think about productivity tools entirely.

I wrote about this last week — how I replaced Notion, Todoist, and Google Sheets with Obsidian + Claude Code. So I won’t repeat the full setup here. But the reason it matters for this conversation is what it revealed about the difference between a system that stores information and one that thinks about it.

With my old stack, I’d spend 45 minutes every Monday clicking through four apps trying to piece together what actually matters this week. I had all the information. But I was still the one connecting the dots.

When I moved everything into an Obsidian vault and connected Claude Code to it, something unexpected happened. Claude started catching things I couldn’t see from inside my own plans:

• One week, it flagged that I’d deferred the same project for three consecutive weeks — something I hadn’t noticed because each individual deferral felt reasonable. It pulled a line from my own weekly review where I’d written “working on multiple things at the same time ruined my focus” — and used that to restructure the next week’s plan around sequential focus blocks instead of parallel task-switching.

• Another time, it caught that a blocker I’d logged on Monday — a payment issue that needed a colleague’s help — was about to collide with an announcement I’d scheduled for Wednesday. I’d stopped thinking about the blocker. Claude hadn’t.

These aren’t dramatic moments. But stacked together, they add up to something I never had with traditional productivity apps: a system that has opinions about my plan. Not just storage. Not just organization. Actual pattern recognition across weeks of my own data.

That’s the shift I keep coming back to. The difference between an app that holds your plan and an AI copilot that reads your plan, compares it to your past behavior, and tells you what you’re avoiding.

Why Both Examples Matter

The newsletter repo showed me that AI can operate inside creative work. The Obsidian vault showed me it can operate inside strategic work too. Same principle — consolidate into plain files, give Claude Code access, stop being the one carrying context between steps.

And it doesn’t stop at the desk. I use OpenClaw that lives inside my Telegram. It has access to both my newsletter repository and my Obsidian vault. So if I’m on my phone and need to check my sprint progress, capture an idea for next week’s post, or ask what’s on my plate today — I just message OpenClaw from Telegram. The agentic workspace follows me, even when I’m away from my laptop.

But the part that feels closest to what an agentic workspace should actually be is Claude Code’s auto memory. Every time a new pattern comes up during a session — a preference I express, a workflow I repeat, a decision I make — Claude Code saves it to its memory automatically. I don’t have to tell it to remember. It just does. And the next session starts smarter because of it.

That’s the compounding effect I keep coming back to. It’s not just that every new file I add makes the system better. The AI itself is learning how I work, session after session — what I care about, how I like things structured, which patterns matter. That never happened with any tool I’ve used before.

Where To Start

I’m not going to give you a 10-step action plan. If this post resonated, you probably already know which part of your workflow has the most copy-paste friction. The one where you spend more time moving outputs between tools than actually doing the work.

Start there. Just that one workflow.

There are two ways to find your starting point.

The first:

“Where does most of your work already live?”

That’s the consolidation path — move your work into a place where AI can reach it.

But there’s another way in that I think is just as valid:

“Where do you already feel the least friction when working with AI?”

Maybe you’ve noticed that certain tasks with AI feel effortless — the back-and-forth is natural, the output is useful, you’re not fighting the tool. Start there. Don’t reorganize your entire life around AI.

Find the interaction that already works and ask:

“What would it look like if this AI could actually act on what we just figured out together, instead of me copy-pasting the result somewhere else?”

That’s how my newsletter repo started. I wasn’t trying to build an agentic AI workspace. I was just tired of the friction in one specific workflow. The system grew from that.

If you’re deep in Google Workspace — Gmail, Docs, Sheets, Drive — Gemini is the shortest path. The integration is already there. You don’t need to set anything up. Start asking Gemini to act across your Google tools instead of using it as a standalone chat.

If you work with files, notes, or anything that benefits from persistent context — look at Claude Code or Claude Cowork. Claude Code is what I use, but if the terminal feels intimidating, Cowork gives you the same file-level access through the regular Claude desktop app. Either way, point it at a folder where your real work lives. Even something as simple as a project folder with a few key documents changes the dynamic.

If your team already lives in Notion — you might not need to switch anything. Notion’s new custom agents can automate workflows, triage tasks, and connect to Slack, email, and other tools directly inside your existing workspace. Worth exploring before you rebuild from scratch.

If you’re managing projects across multiple apps and feeling the friction I described — consider whether consolidating into plain markdown files (Obsidian or even just a folder of .md files) and connecting Claude Code to it would simplify things. It did for me. It might not for you. But the principle holds: the fewer walls between your AI and your actual work, the less time you spend being the middleman.

You don’t need to transform everything at once. I didn’t. The newsletter repo came first. Obsidian came months later. Each step taught me something about how I actually work — not just how I thought I worked.

The Pursuit

I called this post “In Pursuit of Agentic AI Workspace” for a reason. I haven’t arrived. I’m still figuring out where the edges are, what works and what doesn’t, which parts of my workflow genuinely benefit from AI integration and which ones I’m overcomplicating.

But the direction is clear to me now.

The copy-paste era of AI — where you ask a chatbot for help and then manually move everything into your real work — is a phase. A necessary starting point, but not the destination.

What comes next is AI that lives where your work lives. That reads your context, acts on your behalf, and gets smarter the more you use it — because your environment gives it something to build on.

The shift isn’t really about tools; we need to reframe it as a different question.

Not “which AI should I use?” but “where should my AI live?”

Once you answer that, everything else follows.

I’m still in pursuit. But I’m a lot closer than I was six months ago — and if you’re feeling that same copy-paste friction I described at the start, I think you might be ready to start too.

See you in the next one.