Tygart Media

Tag: Claude AI

  • Claude in Chrome Across Multiple Chrome Profiles — The Multi-Account Workflow

    Claude in Chrome Across Multiple Chrome Profiles — The Multi-Account Workflow

    What This Covers
    Chrome profiles are separate browser identities — different logins, different extensions, different sessions. Claude in Chrome connects to one profile at a time via a manual click. Here is how to set that up for multi-account work, and where the friction still lives.

    Chrome profiles are one of Chrome’s most useful and most underused features. Each profile is an isolated browser identity: its own login state, its own saved passwords, its own open tabs, its own extensions. If you manage multiple Google accounts, multiple work environments, or need to keep different service logins separate, profiles are how you do it.

    Claude in Chrome works at the profile level. Understanding that changes how you think about setting it up.

    Each Chrome Profile Is Its Own Island

    When Claude in Chrome connects to a session, it connects to a specific Chrome profile — the one you’re running the extension in, the one where you clicked Connect. It can navigate any tab open in that profile. It cannot see or interact with tabs in other profiles, even if those profiles are open in other windows on your screen.

    This isolation is actually useful. It means you can set up dedicated Chrome profiles for different purposes:

    • One profile logged in to your primary work tools
    • One profile for a client’s services or a specific platform
    • One profile for personal accounts you don’t want mixed into work sessions

    When you want Claude to work in a specific environment, you connect it to that profile. It only sees what that profile sees.

    ⚠️ The extension must be installed on each profile separately. Installing Claude in Chrome on one profile does not install it on others — Chrome isolates extensions per profile. If you set up five profiles and want Claude to be available on all of them, you need to install and connect the extension five times. Check that it’s installed and active before starting any session.

    How switch_browser Works Across Profiles

    When Claude calls the switch_browser tool, it broadcasts a connection request to all Chrome instances that currently have the Claude in Chrome extension installed and active. Every eligible browser window shows a Connect prompt.

    You click Connect on the profile you want Claude to use. That profile becomes the active connection. The other windows are unaffected.

    A few practical notes:

    • Only one profile is connected at a time. Claude doesn’t maintain simultaneous connections to multiple profiles. If you need Claude to work in a different profile mid-session, it calls switch_browser again, and you click Connect in the new target.
    • The connection requires a manual click every time. Claude cannot silently hop between profiles. Each switch requires your action. This is intentional — it keeps you in control of which environment Claude is accessing at any given moment.
    • Pre-login matters. Once connected, Claude can only interact with services you’re already logged in to in that profile. Log in before the session starts, not during.

    A Working Multi-Profile Workflow

    In documented use, the multi-profile workflow looks like this:

    1. Open the Chrome profiles you’ll need for the session — each in its own window
    2. Log in to all the services you’ll need in each profile
    3. Confirm the Claude in Chrome extension is installed and active in each profile you’ll use
    4. Tell Claude Chat what you need done and which profile/environment to start in
    5. Claude calls switch_browser — you click Connect in the right profile
    6. Claude executes the task in that profile
    7. If you need Claude to switch profiles, it calls switch_browser again — you click in the next profile

    The manual click at each switch is the main friction point. It means truly automatic profile-hopping isn’t possible — Claude can initiate the switch, but you have to authorize it each time.

    ⚠️ Be deliberate about which profile you click Connect in. If you have multiple profiles open and multiple Connect prompts appear simultaneously, it’s easy to click the wrong one. The simplest prevention: when switch_browser fires, close or minimize the windows for profiles you don’t want Claude to access before clicking Connect. You can also open only the profile you need at that moment, run the task, then open the next one.

    The Chrome Profile Mapping Idea

    One capability that doesn’t exist yet but is worth building: a Chrome Profile Mapping skill that tells Claude which profile has which services logged in. Right now, Claude has to be told at the start of each task — “the Google account is in Profile 2, the platform admin is in Profile 4.” With a profile map, Claude would know this from context and could request the right profile without you specifying it every time.

    The idea is filed. It’s a one-time setup that would pay off across every multi-profile session afterward.

    How Many Profiles Is Practical?

    There’s no technical limit, but practical friction increases with the number of profiles you’re managing. The manual click requirement means every profile switch is a human action. Sessions that require frequent switching between more than two or three profiles become difficult to sustain without losing track of where Claude is.

    For most multi-account workflows, two to three profiles covers what’s needed: one for the primary environment, one or two for secondary services or client contexts. Beyond that, the workflow tends to benefit from being broken into separate sessions rather than one continuously switching session.

    Frequently Asked Questions

    Can Claude switch between Chrome profiles without me clicking anything?

    No. Every profile switch requires you to click Connect in the target profile. Claude can request the switch by calling switch_browser, but it cannot complete the connection without your action. This is a deliberate design decision, not a technical limitation that will be worked around.

    Do I need to install the Claude in Chrome extension on every profile?

    Yes. Chrome extensions are isolated per profile. The extension must be installed separately on each profile where you want Claude in Chrome to be available.

    What happens if I have multiple Chrome profiles open and I click Connect in the wrong one?

    Claude will connect to whichever profile you clicked in. If you realize you connected to the wrong one, disconnect, call switch_browser again, and click Connect in the correct profile. There’s no automatic way to undo actions Claude took while connected to the wrong profile, so stay attentive when multiple profiles are open.

    Can Claude be connected to two Chrome profiles at the same time?

    No. Claude in Chrome maintains one active connection at a time. To work in a different profile, you switch — which disconnects the current one.

    Is it safe to have Claude connected to a profile that’s logged in to my personal Google account?

    Use judgment. Claude in Chrome can see and interact with any tab open in the connected profile. If your personal profile has Gmail, Google Drive, or other personal services open, Claude has access to those tabs during the session. If you don’t want Claude to interact with personal accounts, use a dedicated work profile for Claude sessions and keep personal tabs in a separate profile that isn’t connected.

  • How to Use Claude in Chrome to Write Directly to a Web App

    How to Use Claude in Chrome to Write Directly to a Web App

    The Pattern
    Claude Chat writes the work order. Claude in Chrome navigates the UI and executes it. This combination lets you automate web apps that have no API — or where the API doesn’t expose what you need.

    A lot of the most useful tools on the web don’t have APIs. Or they have APIs, but specific features — a particular button, a workflow trigger, a UI-only setting — aren’t exposed through them. For years, the workaround was Zapier, custom scripts, or doing it manually.

    Claude in Chrome opens a different path: Claude navigates the UI directly, the same way you would, but you don’t have to be the one clicking.

    How the Two-Claude Pattern Works

    The workflow that works well in practice uses two Claude instances working together:

    1. Claude Chat (the claude.ai interface) handles planning, writing, API calls, and generating the specific instructions for what needs to happen in the browser
    2. Claude in Chrome (the browser extension) receives those instructions and executes them directly in the web app UI

    The typical flow: you describe the task to Claude Chat. Claude Chat writes a precise, step-by-step work order — what page to navigate to, what to click, what to fill in, what to confirm. You paste that into Claude in Chrome. Claude in Chrome executes it in the browser.

    It’s not magic. It’s division of labor: reasoning on one side, execution on the other.

    Real Situations Where This Applies

    In documented use, the Claude Chat → Chrome pattern has been used for:

    • Cloud console navigation — walking through multi-step infrastructure setup in a browser-based cloud console where the relevant actions weren’t exposed through the provider’s CLI or API
    • Domain registrar settings — updating DNS records through a registrar’s web interface. The registrar had an API, but the specific record type needed wasn’t in it.
    • Social scheduling tools — posting or scheduling content through a platform’s web UI when the API tier available didn’t include the scheduling endpoint
    • Web-based terminal environments — operating Cloud Shell or browser-based terminals without switching windows or copy-pasting
    • Browser-based AI notebook tools — creating notebooks, adding source URLs, navigating to generation features, and triggering video or audio generation through a UI

    The common thread: a logged-in browser session was required, and the action wasn’t available through an API.

    ⚠️ Pre-login before you hand off. Claude in Chrome can only interact with services where you’re already logged in in that Chrome profile. If Claude navigates to a page that requires a login it doesn’t have, it will stall or hit an error. Log in to every service you intend to use before starting the session, and make sure the session hasn’t expired. Also: close any tabs with services you don’t want Claude to interact with during this task.

    What Makes a Good Work Order

    The quality of the Chrome execution depends heavily on the quality of the instructions Claude Chat produces. A good work order is:

    • Sequential. Each step follows the last. Claude in Chrome doesn’t skip around.
    • Specific about UI elements. “Click the blue Save button in the upper right” is better than “save it.”
    • Includes what to do if something unexpected appears. Login screen, confirmation dialog, error message — Claude in Chrome handles these better if the work order anticipates them.
    • Ends with a confirmation step. “After completing, read the page and report what you see” closes the loop so you know whether the task actually finished.

    Claude Chat is good at generating this kind of structured instruction when you describe the task well. Give it the context of what tool you’re working in, what you’re trying to accomplish, and what you expect the UI to look like.

    The API-First Rule

    Using Claude in Chrome to operate a web UI is slower and less reliable than using an API. UI layouts change. Buttons get renamed. A platform update can break a workflow that worked yesterday.

    The rule that holds up in practice: API first, Chrome when the API fails or doesn’t exist.

    If a tool you use regularly exposes the action you need through an API, build the API integration and use that. Chrome UI automation is the fallback — valuable and often the only option, but a fallback nonetheless. Don’t default to Chrome just because it’s faster to set up today.

    ⚠️ Don’t leave Claude in Chrome running on high-stakes UI actions without reviewing first. If your work order includes steps like submitting a payment form, publishing content publicly, deleting records, or sending a message — review the work order carefully before Claude executes it, and stay present during execution. UI actions in Claude in Chrome are real. There is no undo button built in.

    When the Work Order Approach Doesn’t Work Well

    A few situations where the Claude Chat → Chrome hand-off runs into friction:

    • Dynamic UIs with inconsistent layouts. If the UI renders differently based on account state, screen size, or A/B tests, Chrome may not find the element the work order described.
    • Multi-factor authentication prompts. If a service triggers MFA mid-session, Chrome will stall waiting for input. You need to be present to handle it.
    • Very long multi-step tasks. The longer the chain of actions, the more likely something unexpected will interrupt it. For long tasks, build in manual check points rather than treating the whole thing as one uninterrupted run.
    • Anything involving CAPTCHA. Chrome cannot solve CAPTCHAs. Tasks that require CAPTCHA completion need manual intervention at that step.

    Frequently Asked Questions

    Does Claude in Chrome work with any website?

    It works with any website loaded in Chrome where you have the appropriate access. The extension interacts with the live DOM of whatever page is open. Some sites use security measures that prevent external scripts from interacting with certain elements, which can limit what Claude can click or read on those pages.

    Can Claude in Chrome interact with pop-up windows or modal dialogs?

    Yes, in most cases. Pop-ups and modals that are part of the page’s DOM are accessible. Browser-level dialogs (like the native file picker or browser alert boxes) have more limited interaction.

    What if the UI changes and Claude can’t find an element?

    Claude in Chrome will report that it couldn’t find the element and stop. It won’t guess or click something random. You’ll need to update the work order to reflect the current UI, or manually navigate to the right state and then reconnect.

    Is there a risk of Claude submitting forms I don’t want submitted?

    Yes, if the work order includes a form submission step. Always review work orders that include submit, confirm, send, or delete actions before execution. If you’re uncertain, break the work order into stages and review what Claude has done before authorizing the next stage.

    Can I use Claude in Chrome for a tool I use for work with sensitive data?

    Use judgment. Claude in Chrome processes what it sees in the browser tab, and the content of that interaction is processed by Anthropic’s systems under your account’s privacy settings. Review Anthropic’s privacy policy for your plan before using Claude in Chrome with tools containing confidential, regulated, or personally identifiable information.

  • Claude in Chrome vs Cowork Computer Use — What’s the Difference

    Claude in Chrome vs Cowork Computer Use — What’s the Difference

    The Short Version
    Claude in Chrome = browser only, any plan, you stay present. Cowork computer use = full desktop, scheduled, unattended, Pro or Max required. They solve different problems. The confusion comes from using the word “automation” for both.

    If you’ve tried Claude in Chrome and also explored Cowork’s computer use feature, you’ve probably noticed they feel completely different — even though both involve Claude “doing things” on a computer. That’s because they are fundamentally different tools, with different scope, different risk levels, and different use cases.

    This comparison is built from documented use of both. Not marketing copy.

    The Core Difference: Browser vs. Desktop

    Claude in Chrome operates exclusively inside the Chrome browser. It can read pages, click elements, fill forms, scroll, download files, and navigate between open tabs. That’s it. It has no awareness of your desktop, no access to your filesystem, and no ability to open applications outside the browser.

    Cowork computer use operates at the full desktop level. It can see and interact with any application on your machine — your file manager, terminal, spreadsheet software, desktop apps, system utilities. It treats your entire computer as its workspace.

    The practical difference: if you close Chrome, Claude in Chrome stops. If you close Chrome while Cowork computer use is running, Cowork keeps going in other applications.

    Scheduling and Presence

    Feature Claude in Chrome Cowork Computer Use
    Scope Browser only Full desktop
    Can run scheduled / unattended No Yes
    Requires you to be present Yes No (once configured)
    Available on free plan Yes No
    Requires Pro or Max No Yes
    Access to filesystem No Yes
    Can open desktop applications No Yes
    Connection method Manual click to connect Configured per task

    When Chrome Is the Right Tool

    Claude in Chrome is the better choice when:

    • The tool you’re working with is entirely browser-based and has no API (or an API that doesn’t expose what you need)
    • You want to work alongside Claude in real time — you’re co-piloting, not delegating
    • The task is one-off or occasional, not something you need to run on a schedule
    • You want Claude to interact with a logged-in browser session that you control
    • You’re on any Claude plan and don’t have access to Cowork computer use
    ⚠️ Stay present with Chrome. Claude in Chrome is not designed for unattended use. If Claude clicks something unexpected or a form submits mid-session, you need to be there to intervene. This isn’t a limitation you can safely work around by walking away — it’s the intended operating model.

    When Cowork Computer Use Is the Right Tool

    Cowork computer use is the better choice when:

    • The task needs to repeat on a schedule — daily, every few hours, weekly
    • The task spans multiple applications (browser plus desktop app plus filesystem)
    • You want it to run without you being present
    • The task involves file operations — reading, writing, moving, processing local files
    • You need multi-step pipelines that chain browser actions with non-browser actions
    ⚠️ Unattended computer use has a wider blast radius. When Cowork computer use runs a scheduled task, it has access to your full desktop — including applications, files, and anything else open on your machine. A misconfigured task or an unexpected UI change on a target website can cause Claude to interact with things it wasn’t supposed to. Review what’s open on your machine before scheduling unattended runs, and test new tasks manually before letting them run on a schedule.

    They Can Work Together

    One pattern that works well in practice: Claude Chat writes the instructions, Claude in Chrome executes the browser-side steps. Cowork handles the scheduled, recurring, multi-app pieces.

    Think of it as a three-tier model. Claude Chat is strategy and orchestration. Claude in Chrome is the field operator for browser-native tasks that require a logged-in session or a UI that has no API. Cowork is the autonomous layer for scheduled, repeating, multi-system work.

    A task that’s “too small for Cowork but too tedious to do manually” is usually a Claude in Chrome task. A task that runs every night at 11pm is usually a Cowork task. Most workflows eventually use all three.

    The Decision Rule

    One question resolves most cases: do you need it to run while you’re asleep?

    If yes — Cowork computer use (Pro or Max required).
    If no — Claude in Chrome, from any plan, with you present.

    Frequently Asked Questions

    Can I use Claude in Chrome instead of Cowork computer use to save money?

    For one-off browser tasks, yes — Claude in Chrome is available on all plans and covers a meaningful range of browser automation. But it can’t replace Cowork computer use for scheduled tasks, unattended runs, or anything that requires filesystem or desktop application access.

    Does Claude in Chrome work inside a Cowork session?

    They’re separate features. Claude in Chrome is a browser extension that works in claude.ai chat sessions. Cowork computer use is a separate capability within the Cowork product. They don’t directly compose with each other, though you can use both in complementary workflows.

    Is Cowork computer use riskier than Claude in Chrome?

    The surface area is larger with Cowork computer use because it has access to your full desktop, not just the browser. Whether that translates to more risk depends entirely on how you configure and test your tasks. Well-tested Cowork tasks running on a focused setup can be lower risk than an untested Claude in Chrome session with sensitive tabs open. The tool isn’t the risk — how you set it up is.

    Can Claude in Chrome run overnight or on a schedule?

    No. Claude in Chrome requires an active chat session and a manual connection per session. It is not designed for scheduled or unattended use. For overnight or scheduled automation, you need Cowork computer use.

    Which one should I start with?

    If you’re new to both, start with Claude in Chrome. It’s available on all plans, the blast radius is limited to your browser, and you stay in the loop during every session. Once you’re comfortable with how Claude navigates browser-based tools, you’ll have a much better sense of whether Cowork’s scheduled automation is worth setting up for your specific workflows.

    Related: How Claude Cowork Can Actually Train Your Staff to Think Better — a 7-part series on using Cowork as a training tool across industries.

  • What Is Claude in Chrome and How Does It Actually Work

    What Is Claude in Chrome and How Does It Actually Work

    Claude in Chrome — Quick Definition
    Claude in Chrome is a browser extension that gives Claude direct control over your active Chrome tab. It can read page content, click buttons, fill forms, scroll, and download files — all inside the browser, without touching your desktop or filesystem.

    There are now three distinct ways to work with Claude at the task level: through the chat interface, through Claude Cowork, and through Claude in Chrome. Most people know the first two. The third one is genuinely different, and genuinely useful — and most people writing about Claude haven’t actually used it yet.

    This article is built from documented operational use. Not theory.

    What Claude in Chrome Actually Is

    Claude in Chrome is a browser extension — separate from claude.ai, separate from Cowork — that connects Claude to your active Chrome tab. Once the extension is installed and connected, Claude gains a set of browser-native tools it doesn’t have in a standard chat session.

    Those tools include:

    • Reading page content — Claude can see what’s on the current tab, including text, links, form fields, and interactive elements
    • Clicking — Claude can click buttons, links, checkboxes, and UI controls
    • Filling forms — Claude can type into text fields, dropdowns, and inputs
    • Scrolling — Claude can scroll a page to load more content or navigate to a section
    • Downloading files — Claude can trigger downloads from web interfaces
    • Navigating — Claude can move between tabs that are open in the connected profile
    ⚠️ Before you experiment: When Claude has browser control, it can interact with any tab in the connected Chrome profile — including tabs where you’re logged in to banking, email, or other sensitive services. Before running any Claude in Chrome session, close or move tabs you don’t want Claude to have access to. Pre-login only to the services you intend to use in that session.

    What Claude in Chrome Is Not

    It’s worth being precise here, because there’s real confusion between Claude in Chrome and Claude Cowork’s computer use feature.

    Claude in Chrome is browser-only. It operates inside Chrome. It cannot access your filesystem, run terminal commands, open desktop applications, or do anything outside a browser window. If you need Claude to interact with files on your computer or run code locally, that’s a different tool entirely.

    Claude Cowork computer use is full-desktop. Cowork’s computer use feature gives Claude access to your entire desktop environment — applications, filesystem, terminal, everything. It’s also scheduled and can run unattended. That’s a much larger surface area.

    The comparison matters because the risk profile is different. Browser-only means the blast radius of any mistake is limited to what’s accessible through Chrome. Full computer use is a fundamentally different level of access. More on this comparison in the full breakdown article.

    How the Connection Works

    Claude in Chrome uses a tool called switch_browser. When Claude calls this tool, it broadcasts a connection request to all Chrome instances that have the extension installed. A small prompt appears in the browser — you click Connect — and Claude is now operating in that Chrome profile.

    A few things to understand about how this works in practice:

    • One profile at a time. Claude connects to one Chrome profile per session. If you have multiple Chrome profiles open, the connection goes to whichever one you click Connect in.
    • The extension must be installed on each profile separately. Chrome profiles are isolated environments. Installing the extension in one profile doesn’t propagate it to others.
    • The connection requires a manual click. This is intentional friction — Claude can’t silently connect to a Chrome profile without your action. You will always know when Claude is taking browser control.
    • Once connected, Claude can navigate between open tabs freely within that profile.
    ⚠️ Don’t walk away during a session. Claude in Chrome is designed for working with a human present. If Claude navigates to a tab where you’re logged in to a web app and something goes wrong — a form submits, an action fires — you need to be there to catch it. This is different from Cowork scheduled tasks, which are designed to run unattended. Treat Claude in Chrome sessions like you’re co-piloting, not delegating.

    What It’s Useful For

    Claude in Chrome’s sweet spot is situations where there’s no API. A lot of useful web tools — dashboards, admin panels, third-party platforms — don’t offer an API, or their API is locked behind an enterprise plan, or the specific action you need isn’t exposed via API even if the tool has one.

    In documented use, Claude in Chrome has been used to:

    • Navigate cloud console interfaces that require clicking through menus
    • Interact with domain registrar admin panels to update DNS settings
    • Operate social media scheduling tools through their web UI when the API doesn’t expose the specific feature needed
    • Use web-based terminal environments where copy/paste would be the alternative
    • Run automated notebook workflows in browser-based AI tools — creating notebooks, adding sources, triggering generation, downloading output

    The pattern is consistent: API first, Chrome when the API doesn’t exist or is blocked. Chrome is the fallback, not the default. But it’s a very capable fallback.

    Available on All Claude Plans

    One thing that surprises people: Claude in Chrome is available to all Claude subscribers, not just Pro or Max. This is different from Cowork computer use, which requires Pro or Max.

    If you’re on a free plan, you can still install the extension and use browser control in your chat sessions. The session limits of your plan still apply, but the capability itself isn’t gated.

    The Right Mental Model

    The cleanest way to think about Claude in Chrome: it’s Claude with a mouse and keyboard, but only inside the browser, and only when you hand it control.

    That framing clarifies both the power and the limits. It’s not autonomous. It doesn’t run in the background. It doesn’t have memory of previous browser sessions. Every connection is a deliberate, per-session handoff. You stay in the loop.

    When you need Claude to do something in a browser-based tool and you’re willing to be present while it runs — Claude in Chrome is the right tool. When you need scheduled, unattended, multi-application automation — that’s Cowork territory.

    Continue reading:
    Claude in Chrome vs Cowork Computer Use — What’s the Difference
    How to Use Claude in Chrome to Write Directly to a Web App
    Claude in Chrome Across Multiple Chrome Profiles — The Multi-Account Workflow

    Frequently Asked Questions

    Do I need a paid Claude plan to use Claude in Chrome?

    No. Claude in Chrome is available on all Claude plans, including free. You’ll still be subject to your plan’s message limits, but the browser control capability itself is not restricted to paid tiers.

    Can Claude in Chrome access my files or run programs on my computer?

    No. Claude in Chrome operates only inside the Chrome browser. It cannot access your filesystem, open desktop applications, or run terminal commands. If you need Claude to interact with files or run code locally, you’re looking for a different tool.

    Is it safe to use Claude in Chrome while logged in to sensitive accounts?

    Use caution. When Claude in Chrome is connected to a Chrome profile, it can see and interact with all open tabs in that profile — including any tabs where you’re logged in to banking, email, or other sensitive services. Best practice is to pre-close tabs you don’t want Claude to have access to before starting a session, and to stay present during the session.

    Can Claude connect to Chrome automatically without me doing anything?

    No. Every connection requires a manual click. When Claude calls the switch_browser tool, a Connect prompt appears in the browser — you have to click it. Claude cannot silently establish a browser connection without your action.

    What’s the difference between Claude in Chrome and Claude Cowork computer use?

    Claude in Chrome is browser-only, works in any chat session, and is available on all plans. Cowork computer use gives Claude access to your entire desktop — applications, filesystem, terminal — and can run scheduled, unattended tasks. It requires a Pro or Max subscription. The choice depends on what you’re trying to automate and whether you need to be present.

    What happens if I close a Chrome tab while Claude in Chrome is using it?

    Claude will lose access to that tab. If the tab was part of an active task — for example, a browser-based notebook generating output — the task will fail or stall. You’ll need to reopen the tab, reconnect the extension, and restart the relevant step. It’s one of the reasons Claude in Chrome is designed for sessions where you stay present.

  • Claude Cowork Changelog: What Changed in Q1 2026

    Claude Cowork Changelog: What Changed in Q1 2026

    Claude AI · Tygart Media · Updated April 2026
    Q1 2026 summary: Cowork went from research preview to generally available. Computer use launched for Pro/Max users. Scheduled and recurring tasks shipped. The sessiondata.img disk-full bug (GitHub #30751) remained open all quarter — the workaround is manual. Plugin marketplace launched in April.

    Claude Cowork shipped more meaningful features in Q1 2026 than in any prior quarter. This is the complete log of what changed, what shipped, and what stayed broken — documented for teams managing Cowork deployments who need to know what actually changed and when.

    January 2026: Foundation Stability

    January was primarily infrastructure hardening. The Cowork runner environment received reliability improvements addressing the most common mid-task failures — streams aborting on slow API responses, sub-agent MCP tool inheritance failures, and session cleanup bugs that left stale working directories. No major feature launches, but the stability improvements reduced the frequency of mid-run failures that had characterized late 2025 Cowork usage.

    Claude Code received the iOS app in October 2025 and the web version — both of which fed into Cowork’s remote dispatch capabilities in Q1. By January, the ability to assign Cowork tasks from a phone was stable enough for regular use.

    February 2026: Model Upgrades Change Everything

    February 5: Claude Opus 4.6 launched. February 17: Claude Sonnet 4.6 launched. Both significantly improved Cowork task quality — particularly for long-horizon agentic sessions where the original 4.0 models would lose coherence mid-task. Sonnet 4.6’s dramatically improved computer use capability (scoring 72.7% on OSWorld) made computer-use Cowork tasks reliable for the first time. Tasks that previously required constant human intervention to stay on track became genuinely autonomous.

    The 1M token context window entered beta on both models in February, enabling Cowork tasks to hold significantly more context across long sessions — particularly valuable for content pipelines processing large document sets or cross-database synthesis tasks in Notion.

    March 2026: Computer Use Reaches Cowork

    March brought the integration of computer use into Cowork for Pro and Max plan users. Claude gained the ability to open files, navigate browsers, click through interfaces, and operate software within Cowork sessions — no additional setup required for Pro/Max subscribers. This was the most significant capability expansion of the quarter: Cowork tasks could now interact with software that doesn’t have an API, including legacy desktop applications and web interfaces without structured data access.

    Dispatch — Cowork’s task queue feature — was extended to support computer use actions, allowing scheduled tasks to include browser automation and desktop interaction steps alongside the existing MCP tool calls and bash operations.

    The Cowork VM disk-full bug (GitHub issue #30751) was acknowledged by Anthropic during March but not resolved. Power users with many skills installed continued to hit the useradd: cannot create directory error every 40-50 sessions. The documented workaround — moving sessiondata.img to reset the VM — remained the only fix. See the full fix guide.

    April 2026: General Availability

    Cowork reached general availability on macOS and Windows via Claude Desktop in April, removing the “research preview” label it had carried since launch. The GA release added enterprise features that had been absent from the preview: usage analytics, OpenTelemetry support for monitoring Cowork activity, and role-based access controls for Enterprise plans allowing admins to define which capabilities each team group can access.

    A plugin marketplace launched for Team and Enterprise plans with admin controls. Admins can now approve, restrict, or block specific plugins org-wide. The Customize section in Claude Desktop was reorganized to group skills, plugins, and connectors in one place.

    Scheduled and recurring task creation was formalized in the UI — previously requiring config file editing, now accessible from within the app. This was the feature most requested by Cowork power users throughout Q1.

    What Remained Broken Through Q1

    The sessiondata.img disk-full bug was the most significant ongoing issue. It affected every power user with a substantial skill library and required periodic manual intervention. No automatic session cleanup shipped in Q1. The manual workaround is documented at Claude Cowork useradd Failed Error Fix.

    Machine-sleep task skipping also remained unresolved — scheduled tasks that fire when a machine is asleep are silently skipped with no retry. Teams running reliable scheduled automation continued to need an always-on machine or a cloud-side solution.

    Q2 2026 Outlook

    The disk-full bug fix and automatic session cleanup are the most anticipated Q2 items. Agent teams (available on Max plans) are expected to expand with better orchestration tooling. Claude 5, expected Q2-Q3, will bring model quality improvements that should further improve long-horizon Cowork task reliability.

    When did Claude Cowork become generally available?

    Claude Cowork reached general availability on macOS and Windows in April 2026. It had been in research preview since its initial launch in late 2025.

    What was the biggest Cowork improvement in Q1 2026?

    The February launch of Claude Sonnet 4.6 and Opus 4.6 most improved Cowork task quality — especially computer use tasks, which became reliably autonomous with Sonnet 4.6’s improved OSWorld scores. March brought computer use to Cowork for Pro/Max users directly.

    Was the Cowork disk-full bug fixed in Q1 2026?

    No. GitHub issue #30751 (sessiondata.img filling up) remained open through Q1 2026. The manual workaround — moving sessiondata.img to reset the VM — is the only fix as of April 2026.

    Related: How Claude Cowork Can Actually Train Your Staff to Think Better — a 7-part series on using Cowork as a training tool across industries.


  • WordPress REST API for Publishers: How to Connect Claude to WordPress Without Plugins

    WordPress REST API for Publishers: How to Connect Claude to WordPress Without Plugins

    Claude AI · Tygart Media
    What this enables: Publishing articles to WordPress programmatically from Claude, Python scripts, GCP Cloud Run jobs, or any HTTP client — without plugins, without Elementor, without touching the WP admin. The same pipeline that powers 27+ managed sites publishing thousands of articles per month.

    WordPress has a fully functional REST API built in. Most people never use it because they don’t know it’s there. For publishers, content operations teams, and anyone running Claude-powered content workflows, the REST API is the infrastructure that eliminates manual publishing and enables automation at scale. Here’s how it works and how to wire Claude to it.

    What the WordPress REST API Can Do

    The REST API exposes every major WordPress function over HTTP: create posts, update posts, get posts, manage categories and tags, upload media, manage users. Every action you can take in the WordPress admin can be done via API call. No plugin required — it’s built into WordPress core since version 4.7.

    Authentication: Application Passwords

    The simplest authentication method for Claude-to-WordPress connections is WordPress Application Passwords — a built-in feature (WordPress 5.6+) that generates a dedicated password for API access without exposing your main login credentials.

    To generate one: WP Admin → Users → Your Profile → Application Passwords → enter a name → click Add New. Copy the generated password immediately — it’s only shown once. The format it gives you has spaces; remove them before using in API calls.

    Authenticate using HTTP Basic Auth:

    Authorization: Basic base64(username:app_password)

    Publishing a Post via API

    A complete post publish call:

    POST https://yoursite.com/wp-json/wp/v2/posts
    Authorization: Basic [base64 credentials]
    Content-Type: application/json

    {
      "title": "Your Post Title",
      "content": "<p>Full HTML content here</p>",
      "excerpt": "Your SEO meta description (140-160 chars)",
      "status": "publish",
      "categories": [5, 12],
      "tags": [34, 67, 89],
      "slug": "your-post-slug"
    }

    The response returns the new post ID and URL. Log these — you need the post ID for any subsequent updates.

    Wiring Claude Into the Pipeline

    The standard Claude-to-WordPress pipeline: Claude generates the article content (with SEO optimization, schema markup, and FAQ sections baked in), a Python or Node.js script assembles the API payload, the payload POSTs to the WordPress REST endpoint, and the response confirms publication. For Cowork tasks, this runs on a schedule without human intervention.

    The critical rule: Notion first, WordPress second. Every article goes to a Notion page before publishing to WordPress. Notion is the storage and version control layer; WordPress is the distribution layer. If you ever need to republish, update, or audit, you have a source of truth that isn’t locked inside the WordPress database.

    Handling WAF Blocks

    Many managed WordPress hosts (WP Engine, SiteGround) run Web Application Firewalls that block API calls from cloud IP addresses. Symptoms: 403 Forbidden errors on POST requests, even with correct credentials. Two solutions: route API calls through a Cloud Run proxy service that presents a different IP profile, or whitelist your specific GCP IP range in the hosting provider’s WAF settings. For SiteGround specifically, direct whitelisting is the most reliable path — the proxy approach has mixed results due to SiteGround’s aggressive WAF configuration.

    Schema and SEO Metadata

    The WordPress REST API supports all Yoast SEO and Rank Math meta fields as post meta. To set SEO title, meta description, and schema markup programmatically, include the relevant meta fields in your POST payload. For Yoast: _yoast_wpseo_title and _yoast_wpseo_metadesc. For Rank Math: rank_math_title and rank_math_description. Inject JSON-LD schema directly into the post content as a <script type="application/ld+json"> block — it renders correctly on the front end and passes Google’s rich results validator.

    How do I publish to WordPress without logging in?

    Use the WordPress REST API with Application Password authentication. Generate an application password in WP Admin → Users → Your Profile, then POST to /wp-json/wp/v2/posts with Basic Auth credentials. No plugin required — the REST API is built into WordPress core.

    Can Claude publish directly to WordPress?

    Yes — through the WordPress REST API. Claude generates content, a script assembles the API payload, and the POST call publishes it. This is how automated content pipelines work at scale. Always write to Notion first; WordPress is the distribution layer.

    Why is my WordPress REST API returning 403?

    Most likely a WAF (Web Application Firewall) blocking the request — common on WP Engine and SiteGround. Either route API calls through a proxy service with a whitelisted IP or whitelist your specific IP range in the hosting provider’s firewall settings.

  • Claude on GCP: Billing, IAM, and Quota Setup for Teams

    Claude on GCP: Billing, IAM, and Quota Setup for Teams

    Claude AI · Tygart Media
    The three things teams get wrong: Using a shared GCP project for Claude and other workloads (makes cost attribution impossible), not requesting quota increases before launch (causes 429 errors at the worst time), and using overly broad IAM roles (security risk and audit problem). All three are fixable in an afternoon.

    Running Claude through Vertex AI on GCP is straightforward to set up for a solo developer. For a team deploying Claude in production, three infrastructure decisions matter significantly: project structure for billing, IAM configuration for access control, and quota management to avoid rate-limit failures. Here’s the setup that scales cleanly.

    Project Structure: One Project for Claude

    Create a dedicated GCP project for Claude workloads — separate from your main application project, your data pipeline project, and your development sandbox. This separation is the single most important decision for operational clarity. With a dedicated project you get: Claude API costs isolated on their own billing line, IAM permissions that only affect Claude access (not your entire infrastructure), quota limits and alerts scoped to Claude usage, and audit logs that only contain Claude-related activity.

    Naming convention: company-claude-prod for production, company-claude-dev for development. Keep them separate — dev workloads shouldn’t share quotas with production.

    IAM Configuration: Minimum Necessary Permissions

    The role that grants Claude API access through Vertex AI is roles/aiplatform.user. That’s the only role needed for model invocation and token counting. Don’t assign broader roles like roles/aiplatform.admin or roles/editor to service accounts that only need to call Claude.

    For team deployments, create one service account per application or environment — not one shared service account for everything. Example structure:

    Service Account Role Used By
    claude-prod-api@project.iam.gserviceaccount.com aiplatform.user Production app
    claude-dev-api@project.iam.gserviceaccount.com aiplatform.user Development
    claude-cowork@project.iam.gserviceaccount.com aiplatform.user Claude Code / Cowork

    If a service account is compromised, you rotate one key without affecting other applications. If a developer leaves, you disable their specific account without touching production credentials.

    Quota Management: Request Increases Before You Need Them

    Vertex AI Claude quotas are set conservatively by default. The default quota for most regions is enough for development and testing, but production workloads — especially automated pipelines running multiple requests per minute — will hit limits. The 429 error (Resource exhausted) at peak load is one of the most common production failure modes.

    Request quota increases before launch, not during an incident. Go to Cloud Console → IAM & Admin → Quotas, filter by “anthropic,” and request increases for the Claude models you’re deploying. Approval is typically same-day for standard business accounts. For the global endpoint, a good starting quota for a production team is 60 requests per minute for Sonnet 4.6 and 20 requests per minute for Opus 4.6.

    Budget Alerts: Know Before It’s a Problem

    Set a budget alert on your Claude GCP project before anything runs in production. Go to Billing → Budgets & Alerts, create a budget for the project, and set email alerts at 50%, 80%, and 100% of your expected monthly spend. Add a Pub/Sub notification if you want to automatically throttle or pause workloads when budget thresholds are hit.

    A Claude content pipeline running at unexpected volume can burn through budget quickly — especially with Opus 4.6 at $25/million output tokens. Budget alerts are the safety net that turns a potential billing surprise into a manageable alert.

    Cloud Logging: Keep the Audit Trail

    Vertex AI API calls are logged to Cloud Logging by default. For regulated industries, explicitly configure log retention to match your compliance requirements — the default 30-day retention may not be sufficient. For SOC 2 or HIPAA environments, export logs to Cloud Storage for long-term archival. The log entries include model called, project, timestamp, and token counts — enough for a complete audit trail without exposing prompt content.

    How do I set up billing for Claude on GCP?

    Create a dedicated GCP project for Claude workloads, set a budget alert before anything runs in production, and monitor spend at Billing → Budgets. Keeping Claude in its own project makes cost attribution clean and prevents unexpected spend from affecting other project budgets.

    What IAM role does Claude need on Vertex AI?

    The roles/aiplatform.user role is sufficient for model invocation and token counting. Use one service account per application or environment. Never assign broader roles like editor or aiplatform.admin to service accounts that only need to call Claude.

    How do I fix Claude 429 quota errors on Vertex AI?

    Go to Cloud Console → IAM & Admin → Quotas, filter by “anthropic,” and request a quota increase for the specific Claude model hitting limits. Request increases before production launch, not during an incident. Approvals are typically same-day for standard business accounts.

  • Claude Cowork MCP Setup: Connecting Notion, Gmail, and Google Drive

    Claude Cowork MCP Setup: Connecting Notion, Gmail, and Google Drive

    Claude AI · Tygart Media
    What this connects: Notion, Gmail, Google Calendar, Google Drive — the four MCP servers most useful for Cowork tasks. Each connects through claude_desktop_config.json and authenticates once. After setup, Cowork tasks can read and write to these services automatically.

    Claude Cowork’s value multiplies significantly when it’s connected to the services where your work actually lives. A Cowork task with no MCP connections can only work with files on your local machine. A task connected to Notion, Gmail, and Google Calendar can read your priorities, check your schedule, triage your inbox, and write outputs back to your workspace — automatically. Here’s how to wire the connections.

    Where MCP Configuration Lives

    All MCP servers are configured in a single file: claude_desktop_config.json. On Windows, this is at %APPDATA%\Claude\claude_desktop_config.json. On macOS, it’s at ~/Library/Application Support/Claude/claude_desktop_config.json. Open it in any text editor. If it doesn’t exist yet, create it. Claude Desktop reads this file at launch — any changes require a restart.

    Connecting Notion

    Notion MCP gives Cowork tasks read and write access to your Notion workspace — fetch pages, create pages, query databases, and update records.

    Add to your claude_desktop_config.json:

    "mcpServers": {
      "notion": {
        "command": "npx",
        "args": ["-y", "@notionhq/notion-mcp-server"],
        "env": {"OPENAPI_MCP_HEADERS": "{"Authorization": "Bearer YOUR_NOTION_TOKEN", "Notion-Version": "2022-06-28"}"}
      }
    }

    Get your Notion API token from notion.so/my-integrations. Create an internal integration, copy the token, and add it to the config. Then share each Notion database or page you want Claude to access with that integration — Notion doesn’t give blanket workspace access, you grant it page by page.

    Connecting Gmail

    Gmail MCP lets Cowork tasks search threads, read emails, and create drafts. Setup requires a Google Cloud project with the Gmail API enabled and OAuth credentials configured.

    "gmail": {
      "command": "npx",
      "args": ["-y", "@googleapis/gmail-mcp"],
      "env": {"GMAIL_CREDENTIALS_PATH": "/path/to/credentials.json"}
    }

    First-run requires completing OAuth in a browser window. After that, the token refreshes automatically. Gmail MCP is read-heavy in most Cowork workflows — used primarily for triage and summary, not bulk sending.

    Connecting Google Calendar

    Calendar MCP provides today’s events, upcoming meetings, and schedule context for briefing and planning tasks.

    "google-calendar": {
      "command": "npx",
      "args": ["-y", "@googleapis/calendar-mcp"],
      "env": {"GOOGLE_CREDENTIALS_PATH": "/path/to/credentials.json"}
    }

    If you’ve already set up Gmail MCP with Google OAuth credentials, Calendar MCP can reuse the same credentials file.

    Verifying Your Connections

    After updating the config and restarting Claude Desktop, open a new chat and ask: “What MCP servers do you have access to?” Claude will list the active connections. If a connection doesn’t appear, check the config file for JSON syntax errors — a single missing comma or bracket breaks the entire config. Use a JSON validator before restarting.

    For Cowork specifically: start a task session and ask Claude to fetch a specific Notion page or list today’s calendar events. A successful response confirms the MCP connection is working for scheduled tasks, not just interactive chat.

    Common Issues

    MCP server not showing up: JSON syntax error in config, or the npx package failed to install. Run the npx command manually in a terminal to check for errors.

    Notion pages returning empty: The integration hasn’t been granted access to that specific page. Go to the page in Notion, click the three-dot menu, and share it with your integration.

    Gmail authentication loop: The OAuth token expired or the credentials file path is wrong. Delete the token file and re-authenticate.

    How do I connect Notion to Claude Cowork?

    Add the Notion MCP server to claude_desktop_config.json with your Notion API token, restart Claude Desktop, and share the specific pages or databases you want Claude to access with your Notion integration.

    Can Claude Cowork read my Gmail?

    Yes with Gmail MCP configured. It requires a Google Cloud project with Gmail API enabled and OAuth credentials. Once set up, Cowork tasks can search, read, and draft emails in Gmail.

    Related: How Claude Cowork Can Actually Train Your Staff to Think Better — a 7-part series on using Cowork as a training tool across industries.

  • How to Build a Daily Briefing With Claude Cowork

    How to Build a Daily Briefing With Claude Cowork

    Claude AI · Tygart Media
    What this builds: A Cowork task that runs each morning, pulls context from Notion, checks your calendar and email, and delivers a structured daily briefing — without you opening anything. Estimated setup time: 90 minutes. Daily time saved: 20-30 minutes of morning context-gathering.

    One of the most practical Cowork automation setups is a daily briefing task — a scheduled agent run that assembles your morning context before you start work. Here’s exactly how to build it.

    What the Briefing Covers

    A well-designed daily briefing task pulls from 3-5 sources and returns a single structured summary. Typical sections: today’s calendar events (from Google Calendar MCP), open priority tasks (from Notion MCP), any overnight emails that need a response (from Gmail MCP), one or two metrics worth knowing (from whatever dashboard you track), and a suggested priority order for the day. The whole thing arrives as a Notion page or appears in a Cowork run log by the time you open your laptop.

    Step 1: Set Up Your MCP Connections

    The briefing task needs read access to the services it pulls from. In Claude Desktop settings, confirm you have active MCP connections for the services you want to include. At minimum: Notion (for tasks and project status) and Google Calendar (for today’s schedule). Gmail is optional but adds significant value if you get time-sensitive emails. Configure these in claude_desktop_config.json before building the task.

    Step 2: Write the Task Prompt

    The prompt is the core of the task. It needs to be specific about what to pull, how to structure the output, and where to write it. A working prompt structure:

    Daily Briefing Prompt Template:

    You are producing my daily morning briefing. Run these steps in order:

    1. Check my Google Calendar for today’s events. List all events with time, title, and any location or meeting link.
    2. Open my Notion [Priority Tasks database] and list any tasks marked P0 or P1 that are not yet complete.
    3. Check Gmail for any unread emails received in the last 12 hours that appear to need a response. List sender, subject, and one-sentence summary.
    4. Write the compiled briefing to a new Notion page titled “Daily Briefing — [today’s date]” under [your briefing parent page].

    Format the briefing with clear sections: Calendar, Priority Tasks, Email Review, Suggested First Action. Keep it scannable — bullet points, not paragraphs.

    Step 3: Create and Schedule the Task

    In Claude Desktop, open Cowork and create a new task. Paste your prompt. Set the schedule to daily at a time before you start work — 6:00 AM or 7:00 AM typically. Make sure Claude Desktop is configured to launch at startup on your machine so it’s running when the task fires. If your machine is off or sleeping when the task fires, it will be skipped — there’s no catch-up mechanism.

    Step 4: Test It Manually First

    Before relying on the scheduled run, trigger the task manually once. Verify it’s pulling from the right Notion database, writing to the correct parent page, and that the calendar and email integrations are connecting. Most first-run failures are MCP authentication issues — the MCP server needs to be authenticated with each service before the task can use it.

    Iteration: Making It Better Over Time

    The first briefing will be useful but imperfect. After a week of runs, refine the prompt based on what’s missing or what’s noise. Common refinements: add a “what’s overdue” check from Notion, filter email to only flag certain senders or subjects, add a weather check for field-based work, or include a one-line summary of the prior day’s Cowork run logs. Each iteration takes 5 minutes to update the prompt; the task runs better every week.

    Can Claude Cowork send me a daily briefing automatically?

    Yes — you build a Cowork task with the briefing prompt, connect it to your MCP sources (Notion, Google Calendar, Gmail), and schedule it to run each morning. The briefing appears in Notion before you start work. Claude Desktop must be running and your machine must be awake at the scheduled time.

    What MCP connections does a daily briefing task need?

    Minimum: Notion (for tasks) and Google Calendar (for schedule). Optional but valuable: Gmail (for overnight emails). All must be configured in claude_desktop_config.json and authenticated before the task can use them.

    Related: How Claude Cowork Can Actually Train Your Staff to Think Better — a 7-part series on using Cowork as a training tool across industries.

  • Claude for Consultants: Proposals, Research, and Client Deliverables

    Claude for Consultants: Proposals, Research, and Client Deliverables

    Claude AI · Tygart Media
    Where consultants get the most leverage: Proposals and SOWs, research synthesis from client documents, deliverable first drafts, presentation structure, and meeting prep. Claude doesn’t replace client relationships or domain expertise — it removes the writing and structural overhead so you can focus on what only you can do.

    Consulting is a business where writing output is the product — proposals, reports, presentations, frameworks. Claude is unusually well-suited to consulting work because it’s strong at exactly the tasks that consume a consultant’s non-billable time: structuring arguments, synthesizing research, drafting deliverables, and translating complex analysis into clear language.

    Proposals and Statements of Work

    The highest-leverage Claude use case for most consultants. Create a Project with your methodology, standard deliverables, pricing structures, and 2-3 past proposals as style examples. Every new opportunity starts with: client name, their problem, what you’re proposing to do, timeline, and fee range. Claude produces a complete proposal draft — executive summary, problem statement, proposed approach, deliverables, timeline, investment. You edit for client-specific nuance and relationship context. A half-day proposal becomes a 45-minute task. Win more by spending less time losing.

    Research Synthesis and Due Diligence

    Paste industry reports, client documents, earnings transcripts, or competitive intel. Ask Claude to synthesize the key insights relevant to your specific engagement question. What used to take a day of reading and note-taking to structure into a coherent picture takes an hour. The synthesis still needs your expert interpretation — but the raw assembly happens at machine speed.

    Deliverable First Drafts

    Give Claude your analysis, your key findings, and your recommended structure. Ask for a first draft of the section or full report. Claude produces a complete draft with appropriate headers, transition logic, and executive language. You edit heavily on the first engagement; lightly on the fifth, because Claude has learned your structure from the Project context. Deliverable production time drops 40-60% for most consulting engagements.

    Presentation Structuring

    Describe your story — what you found, what it means, what you recommend. Ask Claude to structure it as a McKinsey-style or Barbara Minto pyramid argument, as a narrative flow, or as an issue-based structure. Claude returns a complete slide outline with recommended content per slide and the logic of each transition. Your designer then builds it. The thinking-through-structure step that used to take an afternoon takes 20 minutes.

    Meeting Prep and Client Briefings

    Paste a client’s recent press releases, earnings call transcripts, LinkedIn activity, or news coverage. Ask Claude to brief you on their current strategic priorities, recent challenges, and likely concerns going into your meeting. The 2-hour pre-meeting research sprint becomes a 20-minute briefing review. You walk in better prepared than if you’d done the research manually.

    Setting Up for Your Practice

    The investment that pays back most for consultants: spend two hours building a Claude Project that contains your firm’s methodology, writing style, standard deliverable structures, and 3-5 examples of past work (appropriately sanitized). Every engagement after that benefits from that context. Your outputs become more consistent, your voice comes through, and new associates or contractors onboard faster because the style context is documented and enforced by Claude.

    Can Claude write consulting proposals?

    Yes — this is one of its highest-value consulting use cases. With your methodology and style loaded as Project context, Claude drafts complete proposals from a brief. What takes half a day takes 45 minutes. You edit for client-specific nuance.

    Will Claude make my consulting deliverables sound generic?

    Not with proper context. Generic prompts produce generic output. A Claude Project loaded with your methodology, writing examples, and client context produces outputs that sound like you. The setup investment is one-time; the payback is on every deliverable after.

    What Claude plan should consultants use?

    Claude Pro at $20/month for solo consultants. Claude Team for small firms where multiple people share Projects, templates, and client context. The shared Projects feature is particularly valuable for consultancies — consistent voice and methodology across all team members.

    Related: How Claude Cowork Can Level Up Your Content and SEO Agency Operations