← back

The Complete Guide to Every Claude Update in Q1 2026

AI Maker (Substack) · 12 min read · original

If you’re anything like me, I’d say we’re currently in the middle of an Anthropic fever.

The pace of Anthropic updates right now is so overwhelming. In the last three months alone, they’ve shipped over 30 new features. New model, new integrations, new tools, new capabilities... almost every single week.

Keeping up with Anthropic really does feel like a full-time job:)

And if you’re like most people, you’ve seen the announcements, bookmarked a few, maybe tried one or two, and moved on. Because who has time to figure out what actually matters when the next update drops before you’ve even explored the last one?

Lucky for you, you’ve got someone like me, who has all the time in the world to test and experiment with each of Anthropic’s updates every single day, so you’ll know how it works without having to figure it out yourself.

But, here’s what I want you to know: not all of these features are built for the same person. Some are for developers. Some are for everyday users. Some are game-changers. Some are nice-to-haves you’ll never touch.

So Ilia Karelin and I decided to separate the signal from the noise. We went through every single Claude update from January to March 2026, tested them against our actual workflows, and came back with an honest breakdown of what matters, what doesn’t, and what you should actually spend your time learning.

Ilia writes Prosper, the newsletter about AI and software that gives you an unfair knowledge advantage. This is Ilia’s fifth time writing for AI Maker; his first post, on the 3-document system for AI memory is still one of our most-shared pieces, followed by “When NOT to Use AI,” and, most recently, “Claude in Chrome” and “Grok 4.2 Agents Updates.”

Here are Ilia’s latest three posts that you might want to check out:

  1. Save Claude Tokens: 16 Tactics for Chat, Code & Cowork
  2. Claude Chat, Cowork, and Code: The Setup Most People Never Do
  3. Before You Use Claude, Create This File

In this post, Ilia is covering Claude Code features. I’m covering everything else: the Cowork features, general upgrades, and integrations that affect non-techy people like you and me.

🚨 Warning: This is going to be a long post packed with features and screenshots. If you don’t have time to read it now, you might want to click the save button and bookmark this post for weekend reading.

Now, let’s get into it.

Before we go deep, here’s the full list:

That’s 35 updates in roughly 90 days. I know these updates are a source of anxiety, and I don’t want to bore you with changes that don’t actually affect how you work.

Now let me show you which ones truly changed how I work, so we can focus on what actually matters.

🚨 A quick note from sponsor…

Most AI tools help you brainstorm. Atoms helps you build. Turn ideas into real, usable products faster with AI — with a workflow designed for builders and founders who want to ship, not just chat.

Start building with Atoms

I already wrote a full deep-dive on Claude Cowork when it launched in January. If you haven’t read it, start here:

  1. The Ultimate Guide to Building Your Agentic AI Workflow With Claude Cowork
  2. How I Run A Full-Blown AI Research Operation on My Phone (Powered by Claude Cowork)
  3. How to Run a Competitive Analysis on Substack Newsletters with Claude Cowork

The short version: Cowork is basically Claude Code’s autonomous capabilities wrapped in a visual interface. You don’t need to touch a terminal. You give Claude a complex, multi-step task, and it plans, executes, and delivers finished work.

Its main competitive advantage? It made agentic AI accessible to everyone, not just developers. That’s a big deal for people like you and me who want autonomous AI workflows without learning command-line tools.

Everything I’m about to share builds on top of Cowork as the foundation.

These two new features become especially powerful when you combine them, turning Claude into a full agent capable of executing long-running tasks:

This is the model that powers everything I do now when using Claude Cowork/Code. I’m on the Max plan, and Opus 4.6 with high thinking effort is my default.

What changed:

Here’s a real example. I run a full competitive analysis on other Substack newsletters using Cowork and Opus 4.6. In a single session, it connects to Chrome, fires up Firecrawl to scrape 5 to 10 newsletter pages, and runs a deep analysis across all of them. While it’s doing that, it deploys sub-agents in parallel to process each newsletter simultaneously instead of going one by one. By the end, I get a full summary of how my newsletter stacks up: what topics competitors are covering, where the gaps are, and what angles I should consider next. That entire workflow runs autonomously. I wrote about this in detail here:

Before Opus 4.6, this kind of multi-step, multi-source research would break down halfway through. The reasoning wasn’t sharp enough to manage that many moving parts. Now it handles the whole thing without losing track of what it’s doing or why.

This one’s quiet but massive. I used to worry about hitting the token limit mid-conversation, especially on longer projects. That’s gone now. I can have extended working sessions without the context falling off or needing to restart.

For anyone building AI systems (not just having quick chats), this changes the dynamic. Your conversations can be as deep as they need to be.

But please keep in mind that whenever you are in a conversation with Claude, it’s highly recommended to focus on only one topic. If you mix it with other things or projects you’re working on, context rot will happen easily, regardless of how many tokens you can spend.

I’d rate this update 9/10 because it unlocks more possibilities and reduces the mental overhead of worrying about hitting the context limit.

If you’re on the Pro plan, be careful with Opus. It burns through your token quota fast. Sonnet 4.6 with thinking mode turned on is your better default for general tasks. Save Opus for the complex stuff.

This is the update that’s changed my daily routine the most.

I have a research agent that runs every morning and delivers a personalized intelligence brief. It’s not generic AI news. It’s been customized to my specific interests, topics I’m tracking, and the kind of trends that matter for my work. The result feels personal because it is.

Twice a day, an agent checks my calendar and email and gives me:

At the end of the day, it summarizes everything I accomplished. It’s like having a personal chief of staff who tracks your output so you don’t have to.

Your scheduled task now appears under Scheduled in the left sidebar. You can view, edit, or pause it anytime.

Alternatively, you can also create a scheduled task directly from the Scheduled menu by clicking “+ New Task.”

Then fill in the inputs as shown in the screenshot above. Make sure to select the folder you want to work on. The scheduled task has access to everything a regular Cowork session does: your connectors, your files, your skills.

This is the part people sleep on. Dispatch lets me trigger my Cowork agents remotely, including from my phone.

I trigger my research agent while I’m still in bed. I run newsletter workflows from my phone when I’m away from my desk. The work doesn’t stop when I close my laptop.

Start with one scheduled task. A morning brief or email digest. Get that working before you build more.

This is very useful for people who are on mobile a lot, jumping between multiple meetings or commuting, because they can simply trigger their agent to work for them without being present.

Now we get to the more interesting stuffs, let’s dive in:

Connectors being available on the free tier is a bigger deal than people realize. This is what lets Claude talk to your other tools. I wrote about this firsthand last year in my MCP post, feel free to check it out.

Here’s what my current integration stack looks like:

That’s not a flex. That’s the whole point: Claude becomes the central hub that connects everything you already use.

I have a full tutorial on how to activate connectors in your Claude Desktop app. Some connectors are available directly in Claude, while others require a more technical setup using an MCP JSON file that you’ll need to understand:

Connectors are for those who are tired of copying and pasting every AI output from one place to another. They allow you to execute tasks end to end without becoming the middleman between the AI output and your workspace.

Think of plugins like a work theme. Imagine you’re in marketing. A plugin would bundle together custom slash commands, skills, and MCP connectors into one package built around that role. Instead of setting up each piece separately, you install one plug-in and everything is ready to go.

Cowork comes with Anthropic-built plugins that you can install right away. But you can also build your own.

I built a sales and content flywheel plugin for my newsletter business. Here’s what it does: when I have a meeting with a founding member or a client, the plug-in gives me new content ideas across LinkedIn, X, Substack Notes, or One Shot Show based on that conversation, generates a content flywheel, suggests product improvements or new service offerings for my consulting, and surfaces product ideas I can launch later for The AI Maker. All from one meeting input.

That’s a custom plugin built for my specific workflow.

I’ll do a deeper session on how to build your own plugins, but for now, here’s what you should know: plugins are how you go from using Claude as a general tool to having Claude work the way your business works.

These two are gems:

If you used Skills before, forget what you know. Skills used to be saved prompts. Reusable instructions that stopped you from repeating yourself every session. Useful, but limited.

The recent update turned Skills into something completely different: full workflow packages. A Skill now bundles together instructions, scripts, templates, and reference materials into one modular unit that Claude executes on demand. The AI community started calling this “Skills 2.0” because the jump is that significant.

Here’s what changed:

I have 30+ custom Skills built for my newsletter workflow. Here are five that I use the most:

The shift here is from “Claude helps me write” to “Claude produces the deliverable.” And with Skills 2.0, the deliverables are actual files: slides, spreadsheets, documents, not just text in a chat window.

I have 30+ Skills like these built for my newsletter business. If you want to grab them, 10+ of my custom Skills are available as part of AI Maker Lab membership. You get them as a perk when you join.

This one’s practical for a specific use case: livestreams for One Shot Show. When I’m explaining a concept on stream, I can ask Claude to generate a diagram or chart on the fly. Better visualization, better explanation, better content.

This visual below built by prompting them with this:

“Create a built-in diagram and chart to visualize how Skill creator works.”

If you do any kind of teaching, presenting, or explaining, this feature alone is worth exploring.

This one solves a problem you’ve probably felt but couldn’t name.

Every time you start a new conversation with Claude, you’re starting from zero. You re-explain your role, your preferences, your writing style, the tools you use. Even with memory turned on, a new chat doesn’t carry the full weight of a specific project you’re working on.

Cowork Projects fix that. A Project is a persistent workspace where you group your files, custom instructions, and project-specific memory into one place. When you open that Project, Claude already has the context. It knows what you’re building, how you like things done, and what files matter.

You can create a Project from scratch or import one from your existing Claude Projects in the browser. If you’ve been building up a Claude Project with custom instructions and uploaded files, you don’t have to start over. Import it into Cowork and now it has access to everything Cowork can do: scheduled tasks, connectors, plugins, sub-agents, the whole stack.

I wrote an in-depth guide on building your Claude Project Knowledge that you can later import into Claude Cowork:

Here’s how I use Cowork Projects.

I have a Project called “AI Maker” that holds my newsletter style guide, my content calendar, my audience research, and my brand voice instructions. When I open that Project and ask Claude to draft a post, review a piece, or generate social content, it already knows how I write, who I write for, and what format I want. I don’t re-explain any of it. That’s hours of prompting I’ve gotten back over time.

If you’re a consultant, think about having one Project per client. All their briefs, your deliverables, your communication history, scoped together. If you’re a researcher, a Project for each topic you’re tracking that accumulates knowledge across sessions instead of starting fresh every time.

The setup takes five minutes: open Cowork, click “New Project,” point it at a folder or import from an existing Claude Project, add your instructions, and you’re done. From that point forward, every session inside that Project carries the full context of everything before it.

Claude now remembers your preferences across conversations.

[Memory is now available on the free plan. We've also made it easier to import saved memories into Claude. You can export them whenever you want.

7:53 PM · Mar 2, 2026 · 10.9M Views

1.27K Replies · 2.66K Reposts · 38.1K Likes](https://x.com/claudeai/status/2028559427167834314?s=20)

I have auto memory turned on, and over time Claude has learned how I like things done without me having to re-explain every session. It accumulates context about my work style, my preferences, my common patterns.

It’s subtle, but it compounds. The more you use Claude, the less prompting you need to do. That’s the whole point of building AI systems that get better over time.

I want to be honest about what I skip. Not every feature is for everyone.

I already solved this with Google Workspace integrations and custom skills. If you’re deep in the Google ecosystem like me, you might feel the same way. If you live in Microsoft Office, these are probably worth exploring.

Cowork as the foundation that makes everything else possible. Opus 4.6 and the 1 million token context window for longer, deeper working sessions. Scheduled tasks that run your morning routine before you even sit down. Connectors that let Claude talk to your existing tools. Plugins that bundle entire workflows around your specific role. And Skills 2.0, which turned Claude from a writing assistant into something that produces actual deliverables.

That’s the visual, no-code side of Claude. And for a lot of you, that might be where you spend most of your time.

But here’s why you should keep reading.

A lot of you use Claude Code. I know because you followed my guides, you set up MCP servers, you started building things in the terminal that you never thought you could. And some of the most important Q1 updates happened on the Claude Code side.

Ilia is going to walk you through the ones that matter. And I want to be clear: this isn’t a section “for developers.” Dispatch, Remote Control, Channels... these features are about making your Claude workflows run without you being in front of your laptop. That’s relevant whether you write code for a living or you just learned what a terminal was six months ago.

Now let’s go over to Ilia.

Share

Hello, Ilia here 👋🏻

Most Claude Code users treat it like a better terminal. You type a prompt. It writes code. You review it, accept or reject, move on.

That’s using a race car to drive to the grocery store.

Over the last few months, a set of features shipped quietly that changes what Claude Code actually is. Not a faster autocomplete - a system that reads your inbox, runs research sessions, controls your computer, and briefs you on meetings, all while you’re away from your desk.

Most people hear “control Claude Code from your phone” and picture a stripped-down mobile version of the app.

It’s not that.

Dispatch is a remote trigger for your desktop. You type a prompt on your phone, it fires into a full Claude Code or Cowork session running on your machine - same folders, same context. Everything your desktop has access to, available from wherever you are.

The one requirement: your laptop needs to be awake. Dispatch doesn’t run in the cloud. It runs on your machine remotely.

Think about what that changes. Until now, nothing could start that work without you in front of it. Dispatch removes that constraint.

Setup: Claude app on your phone → Cowork section → Dispatch tab. One-time pairing, 60 seconds.

First prompt to try: /emails-tasks 4h

I created this skill in Cowork with Claude’s help. It reads your Gmail inbox for the last four hours, filters for anything that needs a response or decision, and outputs a structured list - sender, subject, what they need, deadline urgency, and a one-sentence draft opener for each. By the time you’re back at your desk, six items are waiting with context pulled and a reply already started. Or it’s a clean inbox in my case:

Dispatch handles prompts you type manually. Remote Control goes further.

Claude Code Remote Control lets you connect to a running Claude Code session on another machine — not just trigger it, but interact with it in real time. You see the session, send follow-up prompts, check progress on long-running tasks, and redirect if needed.

This matters for tasks that take time. Research that spans 20 minutes. A code refactor across multiple files. With Remote Control, you don’t have to be sitting there for the duration. You check in, adjust, and let it continue.

Setup: Run /remote-control command in Claude Code. It will give you a URL link, but it will also let you know that it’s now active. The active Claude Code session will appear in the “Code” section of the Claude app as a “Remote control” session.

In the screenshot above, my Remote control session is already archived, but the active ones will be at the top of the page.

Where it’s most useful: Any task longer than five minutes that you started at your desk and want to monitor or adjust from somewhere else.

Claude Code output, by default, lives where you created it - a file in a folder, a response in a session. You have to go look for it.

Channels change direction. Instead of you checking on Claude Code, Claude Code delivers to you.

You configure a channel: Telegram or a custom webhook, and Claude Code sends output there when a task completes or when something needs your attention. Or you can literally chat with CC through Telegram. Finished a long research session? The brief lands in your Telegram. Hit an error that requires a decision? You get a message, not silence.

I set this up myself. Connected Telegram to Claude Code and named the bot Karl. (Not the most creative name, I know). But now I can talk to Karl and launch tasks from my phone and just casually chat with it. This setup is easier to go through than OpenClaw. Also - shoutout to The AI Maker!

After all the setup is done, to get this running, you install the Telegram plugin and start a channel session with this command:

Setup: Start with Anthropic’s official tutorial: link.

The output finds you. You stop checking.

Computer Use gives Claude direct access to your screen. It can see what’s on it, click, type, scroll, and navigate like a person sitting at your keyboard. No connector needed.

My first idea with this feature was to use Claude as a research assistant that could navigate my social media feeds and find content worth discussing.

Here’s the prompt I used:

“Can you go to X (I’m already logged in on my computer) and find 2-4 posts worth talking about on my Substack?”

Claude opened Chrome, went to X, scrolled my feed, looked at engagement numbers, and came back with four posts - each with view counts, like counts, and a one-sentence editorial angle written for my audience. It read what I would have read. It handed me the synthesis instead of the raw scroll.

Or I tried another little workflow - I asked Claude to go to my LinkedIn and look at the engagement numbers for some of my posts:

Here you can see Claude actually doing the task:

First task to try:

“Can you go to [site you’re already logged into] and find [specific thing you’d normally spend 15 minutes looking for]?”

Computer Use is powerful and deliberate, but a bit slow. It’s doing everything visually, which takes time. The right tasks are ones where the alternative is manual, repetitive clicking. Claude always asks permission before accessing a new application, and you can stop it at any point.

With scheduled tasks, you define a task, attach a schedule (daily at 8am, every Monday, the last Friday of the month), and Claude Code runs it on that cadence. Your inbox triage every morning at 7:45 before you wake up. Write a short LinkedIn post in the evening. A calendar prep session that runs automatically before your Monday starts.

The difference from a calendar reminder: a reminder tells you to do something. A scheduled task does it.

Another variation is “/loop” - a lighter version built for the session you’re already in. Instead of setting up a persistent task, you just type a prompt with an interval and Claude starts checking in the background while you work. Here are examples you can follow:

  1. /loop 5m check if the deployment finished and tell me what happened
  2. /loop 20m [your another slash command]

The key difference: “/loop” lives only as long as the session is open. Close the terminal and it’s gone. That makes it perfect for “watch this while I’m doing something else right now” without needing to set up a permanent schedule.

A Claude Code terminal showing a /loop command with a 5-minute interval

Setup:

The first week, it feels like magic. After two weeks, you can’t remember how you started the day without it.

Claude Code is running a very long task. You have a quick question - not something worth interrupting for, but something you need answered. You don’t want to break the flow or clutter the conversation history.

*/btw* is built for exactly this. It opens a side question that runs independently of the main session. Claude answers from everything already in context - code it’s read, decisions it made earlier, the full conversation, but the question and answer never enter the conversation history (so you can save on tokens!). They appear in a dismissible overlay and disappear when you’re done.

Here are some examples how I used it:

/btw what was the name of that config file again?

/btw is this the function we said we weren’t touching?

Here’s the way you do it: /btw <your question here>.

A few things worth knowing:

Anthropic describes it as the inverse of a subagent: a subagent has full tools but starts with empty context; */btw* has full context but no tools. Use */btw* to ask about what Claude already knows. Use a subagent to find out something new.

You’ve been using Claude Code for weeks or months. You think you have a sense of where you’re wasting time.

You’re wrong. Or at least, I was definitely wrong.

*/insights* reads your last 30 days of session transcripts - your prompts and Claude’s responses and generates an interactive HTML report analyzing exactly where your workflow breaks down.

I ran it a couple of months ago. Then it got to the friction analysis. And I learned a lot from there.

It identified 46 instances of “wrong approach”: Claude jumping into execution before I’d approved the direction. It flagged that my UI sessions averaged 3-5 correction rounds because I kept giving design instructions without constraints. It knew the exact patterns causing most of my friction, what commands and tools I used, what I wanted from Claude, and a lot of other good things about my work.

The best part: after diagnosing the friction, it generates CLAUDE.md rules specific to your pain points, take a look:

Your report will be located on your machine: ~/.claude/usage-data/report.html

I wrote more in-depth about ‘/insights’ commands in my newsletter here.

How to run it: Type */insights* in Claude Code. Takes a few minutes to process. Opens as a local HTML report in your browser.

Run it once a month. The goal is to know exactly where you need to become better at.

This one is small but genuinely changes how fast you can work.

/voice enables push-to-talk dictation directly in the Claude Code terminal. Hold *Space*, speak your prompt, release. Your speech transcribes live into the input field - you can see the words appear as you talk. Then mix in any typing you want and hit enter like normal.

Activate voice with slash command: /voice

When voice mode is enabled, hold Space to record and release it when you are done.

A few things that make it actually useful rather than a gimmick:

The transcription is tuned for coding. It recognizes regex, OAuth, JSON, localhost, and your actual project name and git branch automatically. It’s not fighting you on terminology.

Voice mode persists across sessions once you enable it. You don’t have to turn it on every time.

To activate: type */voice* in Claude Code. The first time, it asks for microphone permission. The default push-to-talk key is *Space* - rebind it in *~/.claude/keybindings.json* if you want a modifier combo like meta+k (which starts recording instantly with no warmup delay).

One requirement: you need to be signed in with a Claude.ai account, not an API key. Audio is streamed to Anthropic’s servers for transcription, so it won’t work in remote/SSH environments. Whatever you say will appear in the window where you usually type in.

Auto memory is a feature where Claude saves notes for itself as it works - build commands, debugging patterns, architecture decisions, code style preferences, workflow habits. Not every session. Claude decides what’s actually worth keeping. Then, at the start of every session, it reads those notes back before you send your first prompt.

A couple of days ago I saw Karpathy post about his personal knowledge base system on X. I fed the post to Claude and asked it to help me start building something similar for Prosper - without Obsidian. No mention of memory, no instruction to save anything. But when the session ended, I noticed Claude had created a “/memory” folder inside my local Prosper directory: a MEMORY[.]md index, a project_prosper.md file, and a few notes about me and what I write about. It just decided that information was worth keeping.

SCREENSHOT: The memory folder in Finder or the terminal — showing MEMORY.md, project_prosper.md, and one or two other files Claude created unprompted

You can browse and edit everything with “/memory” inside any session - it’s all plain markdown. And if you want Claude to remember something specific, just say it directly and it’ll write it down. The memory folder lives at ~/.claude/projects//memory/ on your machine.

When I ran “/memory” and hit Enter, I noticed something else inside the UI: Auto Dream. I turned it on, though I’m not fully confident it’s actually doing anything yet.

Auto-dream feature in terminal

Auto Dream runs a maintenance cycle when you’re not in a session - surveys the memory structure, finds contradictions, converts relative dates to absolute timestamps, prunes stale entries, merges duplicates, and rebuilds the MEMORY.md index under 200 lines so it stays fast to load. It triggers when 24+ hours have passed since the last cycle and you’ve had 5+ sessions since then. You can also trigger it manually by saying “dream” or “consolidate my memory files” in any session.

Apparently, this is what people found out from the Claude Code source code leak. Again, I am not 100% confident that the “auto-dream” actually works yet, but the infrastructure is fully built. It shows up in the “/memory” UI. But as of now it’s gated server-side by a feature flag - not yet live for general users. Worth knowing it exists, and worth turning on when it becomes available.

I got most of this from a deep-dive Reddit post in r/claudexplorers that went through the source code.

Setup: On by default (requires v2.1.59+). Type “/memory” to browse, edit, or toggle it off.

Those are the Claude Code updates that actually changed how I work day to day. A lot of them sound small on paper. Dispatch is just “trigger Claude from your phone.” Channels is just “get output in Telegram.” Remote Control is just “connect to a running session.”

But stacked together, they solve the same problem: your AI workflows shouldn’t need you standing over them the whole time. The best Claude Code setup is one where you start something, walk away, and come back to finished work.

If I had to pick a starting point for someone who’s never touched these features: set up Dispatch first. It takes 60 seconds. Then trigger one task from your phone tomorrow morning. That single moment of “wait, this ran while I was making coffee” will change how you think about every other feature on this list.

Alright, handing it back to Wyndo to close us out.

I know what you’re thinking. This is a lot. Thirty-five updates, two authors, a dozen workflows, screenshots everywhere. You’re probably wondering which ones actually deserve your time this week.

Here’s the honest answer: most of them don’t. Not yet.

The biggest mistake I see people make with Claude updates is trying to adopt everything at once. They read a guide like this, get excited, open Claude, and attempt to set up scheduled tasks, connectors, plugins, and custom Skills all in the same afternoon. Then nothing sticks because nothing had time to become a habit.

So here’s what I’d actually recommend based on where you are right now:

  1. If you haven’t tried Cowork yet, start there and only there. Open Claude Desktop, give it a multi-step task you’d normally do yourself, and watch it plan and execute. That’s it. Don’t set up connectors. Don’t build custom plugins. Just get familiar with how Cowork thinks and works. Everything else in this guide builds on that foundation. You can also read my guide to speed up the process.
  2. If you’re already using Cowork but doing everything manually, set up one scheduled task. Just one. My recommendation: a morning email and calendar digest. Set it to run 30 minutes before you usually start work. When you sit down tomorrow and there’s a prioritized summary waiting for you, you’ll immediately understand why automation matters here. That’s the gateway. Once that’s running, you’ll start seeing other parts of your day that should work the same way.
  3. If you’ve been using Claude but never connected it to your other tools, pick one connector. Whichever tool you spend the most time copying and pasting from. For me that was Gmail and Google Calendar. For you it might be Notion, or Slack, or something else entirely. One connector. Get it working. Use it for a full week before adding another.
  4. If you’ve been treating Claude Code as a fancy autocomplete, try Dispatch or Channels this week. Pick whichever one sounds more useful to your workflow. Dispatch if you want to trigger work from your phone. Channels if you want results delivered to Telegram without you checking on them. Either one will shift how you think about what Claude Code is actually for.

And if you’re reading this completely overwhelmed, here’s your permission to ignore 90% of this guide. Bookmark it. Come back when you’re ready for the next layer. The features aren’t going anywhere. The only thing that matters is that you pick one thing, get it working, and let it become part of how you actually work before you add the next.

That’s how Ilia and I actually adopted all of this. Not in one sprint. One feature at a time, tested against real work, kept only if it earned its place in the daily routine.

Thirty-five updates shipped in Q1 2026. You don’t need thirty-five new workflows. You need one that runs without you. Start there.

If you found this guide useful, Maker Access is where I share everything behind the workflows you just read about.

Here’s what’s inside:

  1. 90+ thinking prompts that change how you approach problems with AI, not generic templates
  2. 10+ Downloadable Claude Skills you can deploy instantly: LinkedIn Carousel Builder, SEO Optimizer, AI News Digest, Infographic Generator, and more
  3. Full Claude Projects, Code and Cowork workflow guides for non-developers, including my complete setup for writing, research, and automation
  4. Live stream recordings and monthly Q&Asessions starting this month, where you can watch real AI workflows being built, ask questions, and get answers live
  5. Make.com and n8n automation blueprints you can copy and adapt, from AI email agents to content repurposing systems

Current pricing is $10/month or $96/year. On April 16th, it goes up to $15/month and $120/year. If you lock in before then, you keep the current rate for as long as you stay a member.

Don’t miss the One Shot Show livestream on Wednesday at 10 a.m. EST.

See you in the next exclusive post this Thursday.

Best,
Wyndo

ai.news — daily digest