Claude AI - Tygart Media

Tygart Media

Category: Claude AI

Complete guides, tutorials, comparisons, and use cases for Claude AI by Anthropic.

  • Snowflake’s $200M Claude Partnership and India’s Glasswing Gap: Two Enterprise Stories That Matter

    Snowflake’s $200M Claude Partnership and India’s Glasswing Gap: Two Enterprise Stories That Matter

    Last refreshed: May 15, 2026

    Two partnership and policy stories from the Anthropic desk that haven’t been covered here yet, both with meaningful implications for how Claude reaches enterprise users and how governments are thinking about AI security risk.

    Part 1: Snowflake’s $200M Partnership — 12,600 Enterprise Customers as Distribution

    In December 2025, Anthropic and Snowflake announced a multi-year, $200M partnership making Claude models available to Snowflake’s 12,600+ enterprise customers across all three major clouds. The partnership makes Claude the AI layer inside Snowflake’s data platform for a client base concentrated in financial services, healthcare, and life sciences — the three regulated verticals where Anthropic has been most deliberately building.

    The specific products:

    • Snowflake Intelligence — powered by Claude Sonnet 4.6, providing conversational data analysis directly within the Snowflake environment
    • Snowflake Cortex AI Functions — supporting Claude Opus 4.5 and newer models for structured AI functions across the Snowflake data warehouse

    Source: anthropic.com/news/snowflake-anthropic-expanded-partnership

    The number that matters most here isn’t $200M — it’s 12,600. That’s the customer count Snowflake brings as a distribution channel. These are enterprise organizations that have already made a procurement decision to standardize on Snowflake for data infrastructure. Embedding Claude inside that infrastructure means Claude becomes the AI system those organizations reach for when they need to query, analyze, or reason about their own data — without requiring a separate AI platform procurement decision.

    This is the distribution model that makes enterprise AI market share move: not direct sales to 12,600 enterprises, but a single partnership that makes Claude the default AI layer inside infrastructure those enterprises already use. Snowflake customers in financial services can run Claude-powered compliance analysis on their own Snowflake data. Healthcare organizations can run Claude-powered analysis on patient data that stays within their existing Snowflake security perimeter.

    The regulated-industry focus is deliberate. Financial services, healthcare, and life sciences are the verticals where data governance requirements are strictest — and where the ability to run AI on your own data, within your own security perimeter, without moving that data to an external AI service, is the deciding factor in procurement. Snowflake’s existing data residency and compliance infrastructure makes that possible in a way that a direct Anthropic API call often doesn’t.

    Part 2: India’s RBI Warning + The Glasswing Gap

    In late April 2026, India’s Finance Ministry and Reserve Bank of India convened meetings on cybersecurity preparedness specifically referencing Claude Mythos risk. Finance Minister Nirmala Sitharaman met with bank executives at North Block to advise pre-emptive hardening. The RBI began consulting with global regulators. CERT-In, major telcos, and fintechs ran parallel risk assessments.

    Source: Business Standard, April 27, 2026 — business-standard.com

    The structural issue underneath the news: Project Glasswing — Anthropic’s defensive cybersecurity consortium that provides early access to Mythos for defensive purposes — named the following founding partners: AWS, Apple, Cisco, CrowdStrike, Google, JPMorgan Chase, Microsoft, and Nvidia. Zero Indian firms. India is Anthropic’s second-largest market globally. Its government is actively warning its financial sector about Mythos risk. And no Indian organization is in the defender consortium that gets early access to the model and the defensive research that goes with it.

    This is not a small gap. The Mozilla Firefox result (271 vulnerabilities in a month, including 20-year-old bugs) demonstrated what Mythos can do in a real production codebase. If that capability is available to offensive actors — or if non-partner organizations don’t have the same early visibility into what Mythos can find — organizations outside the Glasswing partner network are in a different risk position than those inside it.

    The Tension This Creates

    Anthropic’s distribution into India is accelerating. Cognizant deployed Claude across 350,000 employees. Razorpay built its Agent Studio on the Claude Agent SDK and wired UPI rails through Claude as an authorized payment agent with NPCI. Air India, CRED, and Swiggy are named enterprise customers. India is Anthropic’s second-largest market.

    Meanwhile: India’s government is warning its financial sector about the offensive potential of Claude Mythos, no Indian firm is in the Glasswing defender consortium, and INR-denominated pricing (with 18% GST) makes the effective Pro subscription cost approximately ₹2,240/month for Indian users — a meaningful friction point for the market Anthropic is describing as its #2 global market.

    The distribution is running faster than the partnership infrastructure is opening. Either Project Glasswing expands to include Indian financial institutions and cybersecurity organizations, or India builds its own parallel defensive capacity, or the gap becomes a structural political fact in Anthropic’s India relationship.

    India’s government isn’t opposed to Claude. It’s actively adopting it across both public and private sector. The RBI/Finance Ministry meetings were framed as hardening preparation, not restriction. But the asymmetry — India as top-2 market, zero Indian firms in the defender consortium — is conspicuous enough that it will eventually require a response.

    Frequently Asked Questions

    What does the Snowflake-Anthropic partnership include?

    A multi-year, $200M agreement announced December 2025, making Claude models available to Snowflake’s 12,600+ enterprise customers. Snowflake Intelligence launched powered by Claude Sonnet 4.6 for conversational data analysis (model at time of partnership announcement; verify current model with Snowflake). Snowflake Cortex AI Functions supports Opus 4.5 and newer models. The focus is regulated industries: financial services, healthcare, and life sciences.

    What is Project Glasswing?

    Project Glasswing is Anthropic’s invitation-only defensive cybersecurity program that provides early access to Claude Mythos Preview for organizations working to defend critical infrastructure. Named founding partners include AWS, Apple, Cisco, CrowdStrike, Google, JPMorgan Chase, Microsoft, and Nvidia. Access is invitation-only with no self-serve sign-up. No Indian organizations are currently named as Glasswing partners.

    Why is India’s government warning about Claude Mythos if India is Anthropic’s second-largest market?

    The Indian government’s meetings (RBI, Finance Ministry, CERT-In) were framed as defensive preparation, not restriction. The concern is that Mythos-tier capability could be used offensively against Indian financial infrastructure — a legitimate risk that applies regardless of Anthropic’s commercial relationship with India. The tension is that organizations inside Project Glasswing get early access to defensive research while India’s financial sector, with no Glasswing presence, does not.

  • Cowork Routines and Windows Computer Use: What’s New and How We’re Using Both

    Cowork Routines and Windows Computer Use: What’s New and How We’re Using Both

    Last refreshed: May 15, 2026

    Two Cowork capabilities that haven’t been written about here yet, despite being live since late April: Cowork Routines (always-on scheduled tasks that run when your laptop is closed) and Windows computer use (Claude operating your Windows desktop directly from within Cowork). Both shipped in the April 28–30 window alongside the Claude GA release. Both materially change what Cowork is.

    Cowork Routines: The Laptop Can Be Closed

    The original Cowork model required your laptop to be open and the Cowork desktop app to be running. Useful — but bounded by your hardware being available and powered on. Cowork Routines changes that.

    Routines are cloud-hosted scheduled tasks that execute on Anthropic’s infrastructure regardless of your local hardware state. They run on a schedule you define. They execute when your laptop is off, sleeping, or in your bag on a plane. The task runs, the output lands where you configured it to land, and when you open the laptop you find the work done.

    The practical scope of what runs well as a Routine:

    • Daily briefings: Pull sources, synthesize, write to Notion or email — delivered before you open your laptop each morning
    • Monitoring tasks: Check a source on a schedule, flag anomalies, log findings
    • Content pipeline steps: Recurring publication tasks, social scheduling prep, site audit runs
    • Report generation: Weekly status documents assembled from live data sources
    • Notification triggers: Watch a condition, fire an action when it’s met

    We run our own Claude Newspaper Desk — a daily briefing that checks Anthropic’s news, release notes, GitHub releases, and external coverage, then writes a structured briefing to Notion before we start the day. That’s a Routine. The briefing that generated this article was produced by a Routine running on a schedule, not by someone manually triggering a task.

    The architectural decision that makes Routines significant: the task reads its instructions from a Notion desk spec page at runtime, not from a baked-in prompt. Change the Notion spec, change what the Routine does — without touching the scheduled task itself. The shim file that triggers the Routine is thin by design; the intelligence lives in Notion.

    Windows Computer Use: Claude Operates Your Desktop

    Computer use in Claude — the ability for Claude to navigate desktop interfaces, click through UI, fill forms, and verify results — was previously available primarily in research preview and on macOS. The April 2026 Cowork release brought computer use to Windows as a generally available capability within the Cowork desktop app.

    What this means in practice: Claude can open a native Windows application, navigate its interface, perform a sequence of actions, and hand the result back — without you needing to automate it through code or build an API integration. If there’s a tool that only has a Windows UI and no API, Claude can use the Windows UI directly.

    The current state of computer use is honest about its scope. It’s good at:

    • Navigating well-structured desktop applications with clear UI hierarchies
    • Form completion across multiple-step workflows
    • Data extraction from desktop tools that don’t export well
    • Verification steps that require visual confirmation

    It’s slower than direct API integrations when those exist. For tools with APIs, use the API. Computer use is the path when no API exists or when the integration cost exceeds the value of doing it properly.

    The combination of Routines + Windows computer use means a scheduled task can now include a step that operates a Windows desktop application — unattended, while your laptop is running in the background. That’s a meaningfully different capability than what Cowork shipped with originally.

    How We’re Using Both

    Our Cowork architecture as of May 2026:

    • Cowork as execution layer — always-on laptop running scheduled tasks
    • Notion as control plane — desk specs, task queues, logs, and credential storage
    • GCP Cloud Run as action layer — WordPress publishing, API calls, content pipeline steps
    • Claude Code Routines as cloud fallback — tasks that need to run independent of local hardware

    Routines handle the tasks where continuous availability matters more than local context: briefings, monitoring, scheduled publishing. Cowork handles the tasks where rich local context matters: multi-step sessions with file access, browser navigation, and tools that live on the local machine.

    The practical division: if the task needs to run at 3am when the laptop is sleeping, it’s a Routine. If the task needs to interact with local files, a browser session, or a Windows app, it’s Cowork.

    The Non-Developer Angle

    Neither of these capabilities requires you to be a developer to use. Routines are configured through the Cowork interface with natural language task descriptions and a schedule. Computer use activates through the same conversational interface you’re already using.

    The architecture underneath is sophisticated. The interface isn’t. You describe what you want done and when, and the system figures out the implementation. This is the progression that makes these capabilities meaningful for operations teams, executive assistants, knowledge workers, and small business owners — not just engineers building agent pipelines.

    Singapore’s Foreign Minister Balakrishnan built his own version of this on a Raspberry Pi. The point isn’t to build your own — it’s that the underlying architecture (persistent memory, scheduled tasks, multi-channel input) is now accessible at multiple layers of sophistication, from DIY open source to fully managed product.

    Frequently Asked Questions

    What are Cowork Routines?

    Cowork Routines are cloud-hosted scheduled tasks that run on Anthropic’s infrastructure regardless of whether your local Cowork laptop is on or available. They execute on a schedule you define — daily, weekly, or at specific times — and can perform any task Cowork handles: briefings, monitoring, content pipeline steps, report generation, and notification triggers. Each Routine reads its instructions from a Notion desk spec at runtime.

    Does Windows computer use require coding to set up?

    No. Computer use in Cowork activates through the standard conversational interface. You describe what you want Claude to do in the application, and Claude navigates the Windows desktop UI directly. No scripting, automation code, or API integration is required — though API integrations are faster when they exist. Computer use is the path for tools with no accessible API.

    What’s the difference between Cowork and Cowork Routines?

    Cowork runs on your local machine and requires the desktop app to be open and active. Routines run on cloud infrastructure and execute regardless of local hardware state. The practical division: tasks that need to run unattended on a schedule go to Routines; tasks that need local context, file access, or desktop UI interaction go to Cowork. Both read task instructions from Notion desk spec pages at runtime.

    Is Cowork available on both Mac and Windows?

    Yes. Cowork and computer use are available on both macOS and Windows as of the April 2026 general availability release. The Windows release also established PowerShell as the default shell (previously Git Bash was required), reducing a friction point for enterprise Windows shops.

  • Harvard FAS Replaces ChatGPT Edu With Claude: What the Switch Signals

    Harvard FAS Replaces ChatGPT Edu With Claude: What the Switch Signals

    Last refreshed: May 15, 2026

    Harvard’s Faculty of Arts and Sciences will provide Claude access to all affiliates — students, faculty, staff, and researchers — and will discontinue ChatGPT Edu after June 2026. Continuing ChatGPT Edu access will require “administrative and budgetary approval.” Harvard FAS also holds a Google Gemini institutional agreement. The story was reported by The Harvard Crimson on April 28, 2026.

    This is the cleanest institutional AI platform switch yet on record. Harvard FAS covers roughly 20,000 affiliates. The administrative approval language around ChatGPT Edu continuation is the detail that tells you this isn’t additive — it’s a replacement.

    What Actually Happened

    Harvard FAS is not abandoning all AI tools. It’s rotating its primary institutional AI platform from ChatGPT Edu to Claude. The Gemini institutional agreement stays. What’s changing is which AI system gets the default institutional license, the frictionless path, the one that “just works” for every affiliate without requiring a separate approval process.

    That framing matters. When an institution of Harvard FAS’s size structures access so that one platform requires administrative approval to continue while another is provided automatically to all affiliates, the default is the decision. The approval requirement for ChatGPT Edu isn’t a ban — it’s a friction tax that most users won’t bother to pay.

    Why Institutions Switch AI Platforms

    The Harvard Crimson’s reporting framed the switch as “platform rotation based on capability” — not a permanent commitment to any single AI provider. That framing is worth taking seriously. Academic institutions making technology decisions at this scale move deliberately, and the stated rationale (capability) suggests the evaluation was substantive.

    The specific capabilities that tend to drive academic platform decisions:

    • Long-form document handling: Claude’s 1M token context window (on Opus 4.7 and Sonnet 4.6) is directly useful for academic work — reading full papers, dissertations, and research datasets in a single session
    • Research synthesis: Multi-document reasoning across large corpora without chunking
    • Writing quality: Academic writing and editing assistance where tone and precision matter
    • Institutional trust signals: Claude’s Constitutional AI approach and Anthropic’s safety positioning have become differentiators in institutional procurement conversations

    We don’t have Harvard FAS’s internal evaluation criteria. What we know is that after running a ChatGPT Edu institutional agreement, they evaluated their options and chose to route default access to Claude.

    What This Signals for Enterprise Platform Switching

    Harvard FAS is a useful case study because academic institutions make AI procurement decisions in a way that resembles enterprise decisions more than consumer decisions: budget approval processes, IT security review, institutional liability considerations, and the need for a platform that works across a wildly diverse user base — from first-year undergraduates to Nobel laureates.

    The platform switching question — “can our organization move from one AI platform to another?” — has been theoretical for most of the last two years. Harvard FAS running this switch makes it concrete. The institutional machinery for moving 20,000 users from one AI platform to another exists and has been executed.

    For enterprise teams evaluating whether to consolidate on Claude or maintain a multi-platform approach: the Harvard FAS switch is evidence that the transition is operationally feasible at institutional scale, and that institutions with high capability and safety requirements are making this choice.

    The Competitive Context

    Claude now holds institutional agreements at major universities. ChatGPT Edu launched as OpenAI’s play for this exact market. The Harvard FAS switch doesn’t mean OpenAI is losing the education market — it means the competition for institutional default status is real and Claude is winning some of those decisions on capability grounds.

    Anthropic’s enterprise market share, cited in its April 2026 Partner Network announcement, had grown from 24% to 40% since the Claude 4 generation launched. Harvard FAS is one data point in that trend.

    Our Take

    We track institutional AI adoption because it signals where the capability and trust thresholds are in the market. When an institution like Harvard FAS — which has the internal expertise to evaluate these platforms seriously — runs a full procurement process and routes its default institutional license to Claude, that’s a substantive signal about where the models stand.

    The “administrative approval required to continue ChatGPT Edu” language is the tell. That’s not a ban. It’s the institutional equivalent of making one option the path of least resistance and the other a deliberate choice. For 20,000 people with actual work to do, the default wins.

    Frequently Asked Questions

    Did Harvard ban ChatGPT?

    No. Harvard FAS is discontinuing its ChatGPT Edu institutional agreement after June 2026. Continuing access will require administrative and budgetary approval — meaning it’s available but no longer the frictionless default. Harvard FAS is also maintaining its Google Gemini institutional agreement. Claude is becoming the new institutional default, not an exclusive platform.

    How many people does the Harvard FAS Claude agreement cover?

    Harvard FAS covers all affiliates — students, faculty, staff, and researchers within the Faculty of Arts and Sciences. Exact affiliate count varies, but FAS is one of Harvard’s largest schools, covering undergraduate education and most of Harvard’s graduate programs in arts, sciences, and humanities.

    Why did Harvard FAS switch from ChatGPT to Claude?

    The Harvard Crimson reported the switch was framed as “platform rotation based on capability” — not a permanent commitment to any single provider. Anthropic hasn’t published the specific evaluation criteria Harvard FAS used. What’s on record is that after running a ChatGPT Edu institutional agreement, FAS evaluated its options and chose to route default access to Claude.

    Does Harvard’s decision affect other universities?

    Institutional decisions at the Harvard level typically influence procurement conversations at peer institutions — not through imitation but because evaluation committees at other universities use visible peer decisions as data points in their own capability and risk assessments. The Harvard FAS switch makes Claude a more credible institutional option for other universities running similar evaluations.

  • Singapore’s Foreign Minister Built His Own Claude AI Second Brain — And Published the Blueprint

    Singapore’s Foreign Minister Built His Own Claude AI Second Brain — And Published the Blueprint

    Last refreshed: May 15, 2026

    On April 21, 2026, Singapore’s Foreign Minister Dr Vivian Balakrishnan published the architecture of his personal AI assistant on GitHub. He called it NanoClaw — “a second brain for a diplomat.” It runs on a Raspberry Pi 5. It costs roughly $80 in hardware and $5–20 a month in API fees. It connects to his WhatsApp, Gmail, and voice notes. It drafts speeches, runs scheduled briefings, and — unlike every standard chatbot — gets smarter over time because it maintains a structured knowledge graph that persists across sessions.

    His summary: “It answers every question, researches topics, provides daily updates, drafts speeches and condenses information. It has become invaluable — I don’t dare switch it off.”

    A sitting cabinet minister of a G20-adjacent nation just open-sourced his personal AI second brain on GitHub. That’s worth slowing down to look at.

    What NanoClaw Actually Is

    NanoClaw is built on four open-source components running on a Raspberry Pi 5:

    • NanoClaw (agent framework, built by developer Gavriel Cohen, 28k+ GitHub stars) — orchestrates Claude agents in isolated Docker containers. Each chat group gets its own sandboxed container.
    • Mnemon — the knowledge graph layer. Extracts discrete facts, insights, and style preferences from raw documents and conversations into a structured, retrievable graph database. Each entry is a self-contained statement, not a raw text chunk.
    • OneCLI — credential proxy.
    • Karpathy’s LLM Wiki pattern — the memory architecture that lets the system synthesize knowledge rather than just retrieve it.

    WhatsApp integration runs through Baileys, an open-source implementation of the WhatsApp Web protocol — no commercial API required. Voice notes are transcribed locally via Whisper.

    The full architecture is published at: gist.github.com/VivianBalakrishnan/a7d4eec3833baee4971a0ee54b08f322

    The Architecture Detail That Matters Most

    Standard chatbots are stateless. Each session starts from zero. The standard workaround is RAG — retrieval-augmented generation, which pulls chunks of raw text from a document store when they seem relevant. Balakrishnan’s system does something different. Mnemon’s Extract function pulls discrete facts and insights from raw documents into a graph database. Each entry is a self-contained, retrievable statement — not a text chunk.

    This is the same distinction that Anthropic’s Dreaming feature (announced May 6 for Managed Agents) is built on: the difference between storing raw experience and synthesizing it into structured knowledge. A system that synthesizes what it learns compounds in usefulness over time. One that just accumulates raw text doesn’t.

    Balakrishnan acknowledged this in a reply on his GitHub gist: “Local models will not give you the big context needed for digesting the memory graph, but will be good enough for querying it. You may want to use a bigger model that works well with a 128K token context at the very least.” He chose Claude specifically for the reasoning capability on the memory graph.

    He Built It With Claude Code, Not Traditional Coding

    This detail matters. Balakrishnan confirmed on X that he never used an IDE. Claude Code made all edits. His description of his own process: “No ‘vibe coding’. All I did was ‘tool assembly’ to create a utility that worked in my domain.”

    Tool assembly. That’s an important distinction. He didn’t write code — he assembled existing open-source tools using Claude as the implementation layer. A trained ophthalmologist and career diplomat, with no traditional software development background, built and deployed a production AI system running on commodity hardware by composing tools through Claude Code.

    His framing at the 17th Asia-Pacific Programme for Senior National Security Officers, the day he published NanoClaw: “AI agents have crossed a threshold I did not expect so soon. Not just impressive demos — but practical tools for daily use.” The audience was senior national security officials from across the Asia-Pacific region.

    Why This Is the Cowork Story in Miniature

    We run our own version of this — Claude operating scheduled tasks, content pipelines, and research workflows on our behalf through Cowork. The architecture Balakrishnan published is recognizably the same value proposition: persistent memory, multi-channel input, scheduled tasks, a system that improves over time.

    His total cost: ~$80 hardware, $5–20/month API. That’s a DIY Cowork running on a credit-card-sized computer on a diplomat’s desk in Singapore. The point isn’t that the price is better or worse than any specific product — it’s that the primitives are now accessible enough that a non-developer can assemble them into a working production system.

    His own thesis on why he published it: “Sharing the blueprint boosts the edge — the specific composition will be obsolete in months, but the builder’s ability to compose the right pieces is the durable advantage.” That’s as clean a statement of the AI-literacy case as we’ve seen from anyone, let alone a sitting foreign minister.

    The Broader Signal

    Singapore continues to be the most Claude-dense environment we track. The same week Balakrishnan published NanoClaw, a Claude Code meetup at Grab HQ drew 1,291 registrants. GIC (Singapore’s sovereign wealth fund) is a co-investor in Anthropic’s infrastructure JV. The country has institutional capital, developer community density, and now a sitting cabinet minister publishing working Claude architecture on GitHub. That triangle is unusual.

    Balakrishnan’s quote from the CNBC Converge Live fireside the day after publishing NanoClaw: “The diplomat who learns to work with AI will have a meaningful edge. I think that edge is now.” He wasn’t talking about chatbots. He was talking about a system running on his desk, integrated into his actual workflows, that he personally built and that he personally depends on.

    That’s a different kind of AI adoption signal than a press release about an enterprise partnership.

    Frequently Asked Questions

    What is NanoClaw?

    NanoClaw is an open-source Claude-powered personal AI assistant framework built by developer Gavriel Cohen. Singapore’s Foreign Minister Dr Vivian Balakrishnan published his own NanoClaw implementation on April 21, 2026 — a self-hosted assistant running on a Raspberry Pi 5 that connects to WhatsApp, Gmail, and voice notes, runs scheduled tasks, and maintains a persistent knowledge graph that grows smarter over time.

    How much does NanoClaw cost to run?

    Balakrishnan’s setup uses approximately $80 in hardware (Raspberry Pi 5) and roughly $5–20 per month in Anthropic API fees depending on usage volume. The software components (NanoClaw, Mnemon, OneCLI, Whisper, Baileys) are all open source. The full architecture is published at gist.github.com/VivianBalakrishnan/a7d4eec3833baee4971a0ee54b08f322.

    Did Vivian Balakrishnan write the code himself?

    He described his process as “tool assembly” rather than traditional coding — composing existing open-source components using Claude Code to handle implementation. He confirmed on X that he never used an IDE and that Claude Code made all edits. He has no traditional software development background; he’s a trained ophthalmologist and career diplomat.

    How is NanoClaw’s memory different from standard chatbot memory?

    Standard chatbots are stateless — each session starts from zero. NanoClaw uses Mnemon, a knowledge graph that extracts discrete facts and insights from conversations and documents into structured, retrievable entries. The system synthesizes knowledge rather than just storing raw text, meaning it compounds in usefulness over time rather than simply accumulating history.

  • Claude Dreaming Explained: Why AI Agents That Learn Between Sessions Change the Game

    Claude Dreaming Explained: Why AI Agents That Learn Between Sessions Change the Game

    Last refreshed: May 15, 2026

    At the Code with Claude conference on May 6, Anthropic announced a Managed Agents feature called Dreaming. The press covered it briefly — VentureBeat, 9to5Mac — but mostly as a developer story. The Harvey result (a legal AI company reporting roughly a 6× task completion rate increase) was cited but not unpacked. This is the non-developer version of that story, written for people who run workflows, manage operations, or use Claude professionally without writing code.

    What Dreaming Actually Does

    Here’s the mechanism in plain terms. Normally, when an AI agent finishes a session, it’s done. Whatever it learned — the patterns it noticed, the decisions it made, the context that turned out to matter — stays in that session and disappears when the session closes. The next session starts fresh.

    Dreaming changes that. After a session ends, the agent reviews what happened: it reads its own memory store alongside the session transcripts and produces a new, improved version of its memory. Duplicates are merged. Stale information is replaced. New patterns that emerged from the session get incorporated. The next session doesn’t start from scratch — it starts from a richer, more accurate knowledge base.

    The Anthropic documentation describes it this way: a dream reads an existing memory store alongside past session transcripts, then produces a new reorganized memory store with insights no single session could see alone. Docs: platform.claude.com/docs/en/managed-agents/dreams.

    This is a developer-layer feature — it requires implementation, not just subscribing to a plan. But understanding what it does helps you ask the right questions about the tools you’re evaluating and the agents you’re eventually going to run.

    Why Harvey’s 6× Result Is the Right Hook

    Harvey is a legal AI company. Their workflows are exactly the kind of work where this matters: complex research tasks that span multiple sessions, with context that compounds over time. A lawyer doesn’t approach a new matter without the knowledge they’ve accumulated from previous matters. Historically, AI agents did. Each new session was a blank slate.

    Harvey reported roughly a 6× task completion rate increase after implementing Dreaming. That’s not a benchmark number from a controlled test — it’s a production system showing measurable improvement from session-to-session memory refinement. The mechanism is the same as how human expertise compounds: not by accumulating raw experience, but by periodically synthesizing and reorganizing what’s been learned.

    Whether 6× holds across every use case is unknown. The direction of the effect is the signal. Agents that improve between sessions outperform agents that don’t. That gap widens over time.

    The Cowork Parallel

    We run our own Cowork setup — Claude operating scheduled tasks, content pipelines, and site management workflows on our behalf. The Dreaming announcement is relevant to us not because we’re going to implement it today (it’s developer preview, invitation-only access), but because it’s the roadmap signal for where agentic AI is heading.

    The systems we’re building now — Cowork routines, scheduled tasks, skill libraries — are the foundation that Dreaming-style memory will eventually sit on top of. Agents that accumulate context across sessions. Workflows that get better at your job the more you run them. That’s the direction. The Harvey result is the first public production evidence that the direction is real.

    What This Looks Like for Non-Developer Workflows

    Dreaming isn’t in consumer Claude products yet — it’s a developer preview. But the pattern it represents is worth thinking about now for anyone who uses AI in recurring work:

    • Legal and compliance work: Each matter builds on prior matter context. An agent that synthesizes what it learned from 50 prior research sessions before starting the 51st is doing something closer to what an experienced associate does.
    • Operations and project management: Recurring status meetings, weekly reports, vendor communication — these have patterns. An agent that notices “the Friday report always needs these three data sources” and incorporates that into its working memory doesn’t need to be told again.
    • Content and editorial work: Our own content pipeline is a clear example. Style preferences, site-specific constraints, recurring topic clusters — knowledge that currently lives in skill files and desk specs. Dreaming is the mechanism that would let an agent accumulate and refine that knowledge from session experience rather than requiring it to be manually specified.
    • Customer-facing workflows: Agents that handle recurring customer interactions and improve their response quality based on what worked in prior sessions — without a human having to manually update a prompt each time something changes.

    Current Access Status

    To be direct about where this stands today:

    • Dreaming: Developer preview only. Invitation-based access. Not available in claude.ai or any subscription tier.
    • Multiagent Orchestration: Public beta. Available via the Claude API.
    • Outcomes: Public beta. Available via the Claude API.

    If you’re not a developer implementing your own Claude agents, Dreaming isn’t something you can use yet. It will become relevant when it moves to GA and when products built on top of it surface in tools you already use. The Harvey result is the preview of what those products will eventually be able to do.

    Our Take

    The briefing note we wrote when this story broke said: “Dreaming is the story the press mostly missed.” The Harvey 6× result landed in VentureBeat but was treated as a developer-tier data point. We think it’s more broadly significant than that.

    What makes expertise valuable isn’t the accumulation of raw information — it’s the synthesis. A junior lawyer with access to the same case law as a senior partner isn’t equally useful, because the senior partner has synthesized 20 years of patterns into a working model that guides their reasoning. Dreaming is Anthropic’s attempt to give agents a version of that synthesis capability. It’s early, it’s developer preview, and the 6× figure is from one company’s specific workflow. But the direction is clear, and it’s the right direction.

    For anyone building with Claude or evaluating where agentic AI is heading: this is the development worth tracking most closely from the May 6 announcement. Not the SpaceX rate limits (immediately useful), not the Managed Agents public beta (available now), but Dreaming — because it’s the piece that changes the fundamental model of how AI agents improve over time.

    Frequently Asked Questions

    What is Claude Dreaming?

    Dreaming is a Claude Managed Agents feature (developer preview as of May 2026) that lets AI agents review and reorganize their own memory between sessions. After a session ends, the agent reads its memory store alongside session transcripts and produces an improved memory store — merging duplicates, replacing stale information, and surfacing patterns from the session. The next session starts with a richer knowledge base than the previous one ended with.

    What did Harvey report about Dreaming?

    Harvey, a legal AI company, reported roughly a 6× task completion rate increase after implementing Dreaming in their Managed Agents workflow. Harvey’s use case involves complex legal research spanning multiple sessions — exactly the kind of work where session-to-session memory improvement has the highest value.

    Can I use Dreaming in claude.ai?

    No. As of May 2026, Dreaming is a developer preview available only to selected developers implementing their own Claude agents via the Anthropic API. It is not available in the claude.ai interface or through any subscription tier.

    How is Dreaming different from Claude’s memory feature in claude.ai?

    Claude’s memory feature in claude.ai extracts key facts from conversations and injects them into future sessions as a summary. Dreaming is a more sophisticated agent-layer system where the agent itself reviews and reorganizes its full memory store and session history, producing a restructured knowledge base — not just a collection of extracted facts. They serve different purposes at different layers of the stack.

    When will Dreaming be available to non-developers?

    Anthropic hasn’t announced a GA timeline for Dreaming. It will likely surface in consumer and professional products after the developer preview phase completes and the implementation patterns are well understood. Harvey’s result suggests the mechanism works in production; the path to broader availability depends on how Anthropic packages it for non-developer deployment.

  • Code with Claude London (May 19) and Tokyo (June 10): What to Know and Watch For

    Code with Claude London (May 19) and Tokyo (June 10): What to Know and Watch For

    Last refreshed: May 15, 2026

    Anthropic’s Code with Claude conference went global this spring. After the San Francisco event on May 6, London is next on May 19 — followed by Tokyo on June 10. Both are free to attend in person (applications closed; selected by lottery in April) or via livestream from anywhere in the world. If you’re a developer building on Claude and didn’t get an in-person seat, the livestream is worth blocking time for. Here’s what we know about both events and why the Tokyo date in particular is worth paying attention to.

    Quick Reference

    What Code with Claude Is

    Code with Claude is Anthropic’s annual developer conference — a full day of hands-on technical workshops, live capability demos, and 1:1 office hours with the engineers who build Claude. It’s structured specifically for developers and founders who are building with the API, not for people who want marketing keynotes. The SF event on May 6 featured three parallel tracks: Research (direct access to Anthropic researchers on current and future model capabilities), Claude Platform (production agent deployment on Anthropic infrastructure), and Claude Code (running Claude Code at scale — long-horizon tasks, multi-repo work, parallel agents).

    Confirmed speakers across the series: Ami Vora (CPO at Anthropic), Boris Cherny (Head of Claude Code), and Angela Jiang (Product Lead for the Claude API and SDKs). Partner presentations from GitHub, Vercel, and Datadog were part of the SF agenda and are likely to carry into London and Tokyo.

    The Extended day format — May 20 for London, June 11 for Tokyo — is a separate event focused on independent developers and early-stage founders: builder deep-dives, laptops-open workshops from Anthropic’s Applied AI team.

    What Came Out of San Francisco (May 6)

    London and Tokyo attendees will be walking in with context from what Anthropic announced in SF. The major developments from May 6:

    • Managed Agents public beta: Multiagent Orchestration and Outcomes moved to public beta. Multiple SF sessions were dedicated to Managed Agents, including “Get to Production 10x Faster with Claude Managed Agents” and a hands-on “Build a Production-Ready Agent” workshop.
    • Dreaming (developer preview): Agents that review and reorganize their own session history between runs. Harvey (legal AI) reported roughly a 6× task completion rate increase after implementing it.
    • SpaceX compute expansion: Doubled rate limits for Pro, Max, Team, and Enterprise; 1,500% input token increase and 900% output token increase for Tier 1 API customers; peak-hours throttling eliminated for Pro and Max.
    • Claude Code v2.1.133: Subagent skill discovery fix (was silently broken), worktree base ref control, effort-level hooks.

    London and Tokyo events will likely build on these — demonstrating Managed Agents and Claude Code in production contexts with the partner companies that attended SF.

    London — May 19, 2026

    London is Anthropic’s first Code with Claude event in Europe. The practical significance: for developers building in European markets, this is the first opportunity to engage directly with Anthropic’s engineering team rather than attending via livestream from across the Atlantic.

    For teams working in regulated European industries — financial services, healthcare, legal — the Claude Platform and Research tracks are the most relevant. Anthropic’s Finance Agents suite (Moody’s integration, financial analysis and compliance tooling) and Claude Security Beta are recent launches that will likely feature in the sessions, given the financial services concentration in London.

    The London timezone (BST, UTC+1) makes the livestream accessible for much of Europe, Africa, and Middle East without the early-morning constraint that the SF event imposed. Register at claude.com/code-with-claude/london.

    What to Watch For at London

    • Enterprise deployment patterns — London’s enterprise tech community is distinct from SF’s startup-heavy audience
    • EU AI Act compliance framing — Anthropic’s approach to regulated market deployment
    • MCP ecosystem sessions — the Model Context Protocol is increasingly central to how Claude connects to enterprise data sources
    • Any Claude Code enterprise adoption data — the JetBrains 2026 developer survey showed significant Claude Code growth year-over-year; London sessions may provide more context

    Tokyo — June 10, 2026

    The Tokyo date is the strategically interesting one. Anthropic chose Japan as its first Asia-Pacific Code with Claude location at a moment when it has already made several Japan-specific moves: the NEC enterprise partnership (April 2026) and active engagement with Japan’s developer community. This is Anthropic positioning before competitors have fully embedded in the Japanese enterprise AI market.

    Japan’s enterprise AI adoption pattern is different from the US. Large enterprises dominate, procurement cycles are longer, and partnerships with established technology companies (like NEC) carry more weight than direct developer adoption alone. Tokyo’s Code with Claude is as much about signaling enterprise commitment as it is about developer community building.

    The Tokyo event is also relevant to Southeast Asia broadly — developers across the Asia-Pacific region can attend via livestream at a timezone that doesn’t require a middle-of-the-night session.

    What to Watch For at Tokyo

    • NEC partnership details — the most concrete Japan enterprise deployment announced so far
    • Asia-Pacific pricing or access updates — Anthropic’s pricing in USD creates friction in markets like India and Japan where USD conversion plus local taxes creates meaningful access barriers
    • Localization and multilingual Claude capability demos — Claude’s multilingual support is strong on paper; Tokyo is where it gets demonstrated to an audience that can evaluate it critically
    • Any announcement of a dedicated Japan or APAC infrastructure presence

    How to Attend Remotely

    Both events are fully livestreamed at no cost. The livestream covers all three conference tracks. Recordings are published to Anthropic’s YouTube channel (the “Code w/ Claude Developer Conference” playlist) within 7–10 days of each event. If you’re watching recorded sessions rather than live, the Claude Code track tends to have the highest density of immediately applicable technical content.

    For the London event: sessions run BST (UTC+1). For Tokyo: JST (UTC+9). Anthropic hasn’t published detailed schedules for London or Tokyo publicly yet — check claude.com/code-with-claude for updates as each event approaches.

    Our Take

    We watched the SF event closely and tracked what came out of it. The Managed Agents announcements were the most developer-relevant; the SpaceX rate limit news was the most immediately practical for anyone hitting API ceilings. Both London and Tokyo will be building on that foundation with an audience that has had two more weeks to actually use what Anthropic shipped in SF.

    The office hours format is underrated. Getting 30 minutes with Boris Cherny’s team on a specific Claude Code workflow problem is worth more than three conference talks. If you’re attending in person or have specific implementation questions, that’s the format to prioritize.

    For us, Tokyo is the event to watch for signals about where Anthropic’s international enterprise push is actually headed. The NEC partnership gave them a credible anchor. Code with Claude Tokyo is where they build on it.

    Frequently Asked Questions

    Is Code with Claude London free to attend?

    Yes. Both in-person attendance and virtual livestream are free. In-person applications closed in April with selection by lottery. Livestream registration remains open at claude.com/code-with-claude/london.

    Will Code with Claude Tokyo sessions be recorded?

    Yes. All sessions from all three cities are published to Anthropic’s YouTube channel within approximately 7–10 days of each event. The “Code w/ Claude Developer Conference” playlist on Anthropic’s YouTube channel is the official home for recordings.

    What tracks are available at London and Tokyo?

    Based on the SF event structure, three parallel tracks: Research (model capabilities and direction), Claude Platform (production agent deployment), and Claude Code (scaling Claude Code in real engineering workflows). Specific session details for London and Tokyo haven’t been fully published; check claude.com/code-with-claude for the agenda as each event approaches.

    What is the Extended day format?

    The Extended day (May 20 for London, June 11 for Tokyo) is a separate event focused specifically on independent developers and early-stage founders — builder stories, hands-on workshops from Anthropic’s Applied AI team, and a more informal format than the main conference day.

    Is Code with Claude relevant if I’m not using Claude Code specifically?

    Yes. The Claude Platform track covers Managed Agents, MCP integrations, and production deployment patterns that apply to any team using the Claude API — not just Claude Code users. The Research track covers model capabilities and roadmap direction relevant to anyone building on Claude.

  • How Mozilla Used Claude Mythos to Find 271 Firefox Vulnerabilities — Including a 20-Year-Old Bug

    How Mozilla Used Claude Mythos to Find 271 Firefox Vulnerabilities — Including a 20-Year-Old Bug

    Last refreshed: May 15, 2026

    On May 7, 2026, Mozilla’s engineering team published the technical account of what happened when they ran Claude Mythos Preview against the Firefox codebase. The headline numbers — 271 vulnerabilities found, 423 total security bugs fixed in April — had already circulated. What the Mozilla Hacks post added was the methodology: how they actually built the pipeline, what Mythos found that human reviewers and fuzzers had missed for decades, and a candid account of what AI-assisted security research looks like in production.

    This is that story, with the details that matter.

    Source

    All technical details in this article are sourced from Mozilla’s own engineering post: Behind the Scenes Hardening Firefox with Claude Mythos Preview, published May 7, 2026, by Mozilla engineers Brian Grinstead, Christian Holler, and Frederik Braun.

    The Numbers in Context

    Mozilla’s security team was fixing roughly 20 to 30 security bugs in Firefox per month throughout 2025. That number jumped to 423 in April 2026 — a roughly 20× increase in a single month. Of those 423 total fixes, 271 were attributed to Claude Mythos Preview. The remaining bugs came from external reports (41), other internal pipeline work using different models, and traditional fuzzing.

    The 271 Mythos-found bugs broke down by severity as follows, from the Mozilla advisory:

    • 180 rated sec-high — vulnerabilities triggerable with normal user behavior, like visiting a web page
    • 80 rated sec-moderate — would be sec-high except they require unusual steps from the victim
    • 11 rated sec-low — annoying but low harm risk (safe crashes, etc.)

    Mozilla also directly credited 3 separate CVEs to Anthropic’s Frontier Red team (CVE-2026-6746, CVE-2026-6757, CVE-2026-6758) — bugs Anthropic had submitted to Mozilla a couple months prior, before the harness work began.

    What Claude Mythos Found That Everything Else Missed

    The most striking finding from Mozilla’s report isn’t the volume — it’s the age and complexity of what Mythos surfaced. Mozilla published a sample of the bug reports. Two entries stand out:

    A 20-Year-Old XSLT Bug (Bug 2025977)

    Mythos identified a bug in Firefox’s XSLT implementation where reentrant key() calls cause a hash table rehash that frees its backing store while a raw entry pointer is still in use. The bug had been sitting in the codebase for 20 years, undetected by fuzzing and manual review. Mozilla noted this was one of several sec-high issues involving XSLT they fixed in the same release.

    A 15-Year-Old HTML Legend Element Bug (Bug 2024437)

    Mythos triggered a bug in the <legend> element by orchestrating edge cases across distant parts of the browser — including recursion stack depth limits, expando properties, and cycle collection. The bug had existed for 15 years. Mozilla’s description of the finding: “meticulous orchestration of edge cases across distant parts of the browser.” This is the kind of bug that requires reasoning about how subsystems interact at a systems level — not pattern-matching on known vulnerability types.

    Sandbox Escape Bugs That Human Reviewers Had Missed

    Several of the 271 bugs were sandbox escapes — vulnerabilities that, when chained with other exploits, could allow an attacker to break out of Firefox’s sandboxed content process into the privileged parent process. Mozilla noted these are “notoriously difficult to find with fuzzing.” Mythos found multiple. It also attempted prototype pollution attacks on hardened subsystems — and found nothing exploitable there, confirming that Mozilla’s earlier architectural changes had worked.

    How the Agentic Harness Actually Works

    Mozilla’s engineers are explicit about the mechanism that changed everything: it’s not the model alone. It’s the combination of a capable model with an agentic harness that can generate and run reproducible test cases.

    Earlier attempts at AI-assisted security review using GPT-4 and Claude Sonnet 3.5 produced too many false positives to be practical. The shift came when the harness could do something the earlier systems couldn’t: create a test case, run it, observe the result, and confirm whether the hypothesized bug was real before reporting it. Static analysis produces noise. An agent that can execute code to verify its findings produces signal.

    The pipeline Mozilla built, in their own description:

    1. Parallelized jobs run across multiple ephemeral VMs, each tasked with hunting bugs in a specific target file
    2. Findings are written back to a central bucket
    3. A discovery subsystem deduplicates against known issues, tracks bugs, triages them, classifies by severity, and manages patches through the release process
    4. Over 100 engineers contributed code to get patches out the door

    Mozilla started this pipeline with Claude Opus 4.6 on sandbox escape hunting. When Mythos became available, they swapped it in. Their assessment of the upgrade: “model upgrades increase the effectiveness of the entire pipeline: the system gets simultaneously better at finding potential bugs, creating proof-of-concept test cases to demonstrate them, and articulating their pathology and impact.”

    What Mythos Couldn’t Break

    Mozilla’s engineers made a point of documenting what Mythos tried and failed to do. Specifically: it repeatedly attempted prototype pollution attacks — a class of sandbox escape that human researchers had used successfully in the past — and was blocked by architectural changes Mozilla had made. The hardened subsystems held.

    Mozilla’s take on this: “Observing such direct payoff from previous hardening work was even more rewarding than finding and fixing more bugs.” This is actually the more important message for security teams: defensive architecture works, and AI analysis now provides the empirical test of whether it does.

    What This Means for the Software Security Ecosystem

    Mozilla’s engineers closed their post with a direct recommendation: anyone building software can start using an agentic harness with a modern model today. Their advice on approach is practical — start with simple prompting, observe what the model produces, iterate. The inner loop they describe is: “there is a bug in this part of the code, please find it and build a testcase.”

    The implications are real for any organization that maintains a codebase:

    • The asymmetry is reversing. For years, offensive AI (cheap to prompt, cheap to deploy) had the advantage over defensive security (slow, expensive human review). An agentic harness that can verify its own findings changes that balance. Mozilla’s engineers describe the current moment as one where “defenders finally have a chance to win, decisively.”
    • Old code is newly exposed. 15-year and 20-year-old bugs in a heavily-reviewed browser like Firefox suggests that large, mature codebases contain latent vulnerabilities that fuzzing and human review have consistently missed. If that’s true of Firefox, it’s true of most production software.
    • The pipeline is the work. Mozilla’s engineers are clear that the model is a component, not the product. Building the triage, deduplication, patch management, and release integration around the model is what made this work at scale. The pipeline required significant iteration and tight feedback loops with the engineers who were fielding the bugs.

    Claude Mythos Preview: Access and Context

    Claude Mythos Preview is not a generally available model. It’s offered through Project Glasswing as an invitation-only research preview for defensive cybersecurity workflows, specifically for organizations working on critical infrastructure. Pricing from Anthropic’s docs: $25 input / $125 output per million tokens. Mozilla’s access was part of this program.

    The generally available Claude models as of May 2026 (verified from Anthropic’s official documentation):

    • Claude Opus 4.7 (claude-opus-4-7) — flagship, 1M context window
    • Claude Sonnet 4.6 (claude-sonnet-4-6) — balanced speed/intelligence, 1M context window
    • Claude Haiku 4.5 (claude-haiku-4-5-20251001) — fastest, 200K context window

    Mozilla’s earlier pipeline work used Claude Opus 4.6 before Mythos was available and still found significant vulnerabilities. The pipeline architecture is available to any team; Mythos-tier capability is not.

    Our Take

    We’ve been tracking the Mythos story since the Project Glasswing announcement in April. The Mozilla post is the first time a production engineering team has published the full technical account of what AI-assisted security research looks like from the inside — not benchmarks, not Anthropic’s own claims, but Mozilla’s own engineers describing what they built, what it found, and what it couldn’t crack.

    The 20-year-old XSLT bug is the one that cuts through the noise. Firefox is one of the most security-reviewed browser codebases in existence. Thousands of professional security researchers, internal teams, and academic researchers have looked at this code. An AI model running in an agentic harness found a two-decade-old bug with a reproducible test case in what Mozilla described as a pipeline that “required significant iteration.” That’s not a benchmark number — it’s a deployed result from a production security team.

    The question for any organization that ships software is no longer whether this class of tooling will become standard. It’s how fast and whether your team will be ahead of or behind that curve when it does.

    Frequently Asked Questions

    What is Claude Mythos Preview?

    Claude Mythos Preview is Anthropic’s most capable AI model, offered exclusively through Project Glasswing as an invitation-only research preview for defensive cybersecurity workflows. It’s not publicly available. Pricing is $25 per million input tokens and $125 per million output tokens. Mozilla, along with other critical infrastructure partners, received access as part of this program.

    How many Firefox vulnerabilities did Claude Mythos find?

    Claude Mythos Preview found 271 security vulnerabilities in Firefox that were fixed in Firefox 150 (April 21, 2026) and subsequent point releases. Of those, 180 were rated sec-high, 80 sec-moderate, and 11 sec-low. Total security bugs fixed across all of April 2026 was 423, including externally reported bugs and bugs found by other internal methods.

    What is the agentic harness Mozilla built?

    Mozilla built a custom pipeline on top of their existing fuzzing infrastructure. It runs model-powered agents in parallel across ephemeral VMs, each tasked with finding bugs in a specific file or subsystem. Agents generate reproducible proof-of-concept test cases to verify bugs before reporting them — eliminating the false positive problem that made earlier AI security review impractical. Findings are piped into a deduplication and triage system integrated with Mozilla’s normal patch management and release process.

    Can other organizations use this approach?

    Yes, with the publicly available models. Mozilla’s engineers explicitly recommend that any software team start using an agentic harness with a modern model now. You don’t need Mythos access to start — Claude Opus 4.7 and Sonnet 4.6 are publicly available via the Anthropic API. The pipeline architecture is the work; the model upgrade is a component swap.

    What’s the difference between what Claude found and what fuzzing finds?

    Traditional fuzzing generates random or semi-random inputs to trigger crashes. It’s effective at finding memory corruption bugs triggered by malformed data, but poor at finding bugs that require complex reasoning about how distant subsystems interact. The 15-year-old HTML legend element bug and 20-year-old XSLT bug that Mythos found both required reasoning about multi-subsystem interactions that fuzzing consistently missed. AI analysis and fuzzing are complementary; Mozilla runs both.

  • Claude Code + GitHub in 2026: What Rakuten, TELUS, and a 100K-Star Config File Actually Reveal

    Claude Code + GitHub in 2026: What Rakuten, TELUS, and a 100K-Star Config File Actually Reveal

    Last refreshed: May 15, 2026

    Seven hours. That’s how long it took Claude Code to autonomously navigate a 12.5-million-line codebase and implement a production-ready activation vector extraction method in vLLM for Rakuten’s engineering team — a task their developers hadn’t attempted because the codebase was simply too large to reason about at human speed. The result: 99.9% numerical accuracy and a project timeline that compressed from 24 working days to 5.

    That’s not a demo. That’s a production case study. And it tells you more about where Claude Code + GitHub workflows are in 2026 than any benchmark comparison.

    This post breaks down three real-world patterns from teams getting measurable results with Claude Code on GitHub: what they set up, how they structured the work, and what’s actually driving the outcomes.

    The Setup That Enables Everything: CLAUDE.md First

    Before any CI/CD integration, the teams getting results share a common starting point: a well-structured CLAUDE.md file that tells Claude Code exactly how to behave in their specific codebase.

    Andrej Karpathy’s lean 65-line CLAUDE.md — originally shared as a personal config — accumulated over 100,000 GitHub stars by early 2026, which tells you something: developers are desperately hungry for a working template. What made it valuable wasn’t length. It was specificity. Four behavioral rules that directly address LLM coding failure modes: don’t assume context you don’t have, prefer surgical edits over full rewrites, surface tradeoffs rather than hiding them, and treat goals as declarative targets with verification loops.

    That last principle is the most important for GitHub integration. When Claude knows the goal is “this PR should pass CI and not break existing tests” rather than “write code,” the outputs change materially. You get tighter diffs, fewer phantom dependencies, and PRs that actually close the issue they were created for.

    Your CLAUDE.md lives in the repo root and commits alongside your code. It travels with the codebase. Claude Code GitHub Actions picks it up automatically when you use anthropics/claude-code-action@v1 — no additional configuration required.

    The GitHub Actions Setup

    The GA version of Claude Code GitHub Actions (@v1, released in 2026) simplified configuration considerably from the beta. Here’s the minimum viable setup:

    name: Claude Code
on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
jobs:
  claude:
    runs-on: ubuntu-latest
    steps:
      - uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

    Drop this in .github/workflows/claude.yml, install the GitHub app at https://github.com/apps/claude, add your ANTHROPIC_API_KEY secret, and you can start triggering Claude with @claude in any PR or issue comment. The fastest path is running /install-github-app inside your Claude Code terminal session — it walks through the app installation, permissions, and secret setup in a single guided flow.

    For teams on Google Vertex AI or Amazon Bedrock — which matters if you’re operating in a regulated environment — the action supports both via Workload Identity Federation. Bedrock uses region-prefixed model strings (us.anthropic.claude-sonnet-4-6); Vertex pulls the project ID from the auth step automatically.

    The action defaults to Sonnet. For heavy refactoring tasks on large codebases, bump it explicitly:

    claude_args: "--model claude-opus-4-7 --max-turns 10"

    claude-opus-4-7 is the current flagship model. For routine PR review and issue triage, Sonnet is faster and more cost-efficient. The --max-turns flag prevents runaway jobs from consuming your Actions budget on open-ended tasks — set it to 5 for review workflows, 10–15 for implementation tasks.

    Rakuten: Autonomous Work at Codebase Scale

    Rakuten’s engineering team used Claude Code to tackle vLLM — a 12.5-million-line open-source inference framework — without prior familiarity with the codebase. Claude Code ran autonomously for seven hours, implemented the activation vector extraction method, and delivered 99.9% numerical accuracy.

    The workflow wasn’t magic. It was structured: a clear task definition scoped to a specific deliverable, a CLAUDE.md establishing Rakuten’s code patterns and testing requirements, and an allowance for autonomous tool use across the codebase. The result wasn’t just the implementation — it was the compression of a project timeline from 24 working days to 5. That’s a 79% reduction in time-to-market for a complex systems task, on a codebase that would take a new engineer weeks just to orient themselves in.

    The lesson: Claude Code’s GitHub integration handles scale that would be cognitively impossible for a single developer to navigate in a normal sprint. The constraint isn’t Claude’s ability to read code — it’s whether you’ve given it a goal specific enough to work from.

    TELUS: 500,000 Hours at the Portfolio Level

    TELUS is a different kind of case. Rather than a single high-stakes task, TELUS rolled Claude Code out across engineering teams organization-wide and measured cumulative impact: 500,000 hours saved, engineering code shipping 30% faster, and over 13,000 custom AI solutions built by their own teams.

    The 13,000 solutions number is the most telling. It means that once developers have Claude Code in their GitHub workflow, they stop waiting for platform teams to build internal tooling. They build it themselves — PR automation, internal API clients, test generators, schema migration scripts — because the cost of shipping something useful dropped to a well-scoped conversation with an @claude trigger.

    The 30% speed improvement in code shipping translates directly to cycle time. Fewer context switches between writing code and writing tests. Less time waiting for review when PRs arrive with Claude-generated documentation already attached. That number compounds across a large engineering org in ways that individual productivity improvements don’t.

    The Pattern Across All Three

    Three things appear consistently across every team getting results with Claude Code on GitHub:

    A real CLAUDE.md — not a placeholder. A file with codebase-specific rules: what patterns to follow, what to avoid, how tests should be structured, what done looks like. Karpathy’s version works because it encodes failure modes. Yours should encode your team’s standards.

    Goal-oriented triggers, not open-ended requests. @claude implement the auth middleware from issue #42 following our existing token validation pattern outperforms @claude help with this. The action inherits your CLAUDE.md automatically, but the trigger needs to state a specific, bounded goal with a clear definition of done.

    Autonomous mode for the right task class. Bounded, well-defined tasks — implement this spec, fix this failing test, write a migration for this schema change — run better autonomously than open-ended exploration. Use --max-turns 10 and let it run. Reserve manual review for the output, not the process.

    Where to Start

    Run /install-github-app in your Claude Code terminal. That one command handles app installation, permission setup, and secret configuration. Add a CLAUDE.md to your repo root — even five lines of real project standards beats a blank file. Open a test issue, write a specific @claude comment with a bounded task, and watch the action run.

    Rakuten’s 7-hour autonomous run and TELUS’s 500,000 hours didn’t start with a six-month AI rollout plan. They started with a config file, a workflow YAML, and a task specific enough for Claude to actually finish.

    📚 Topic Cluster Index: Deep-Dive Guides

    Explore our comprehensive, step-by-step guides in the Claude Code Insider series:

  • AI for Moving Companies: Free Claude Skills and Prompts

    AI for Moving Companies: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Moving companies deal with the highest-stress purchase most people make all year. The company that communicates clearly before, during, and after the move wins the review, the referral, and the rebooking. Claude handles the communication layer. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Moving Companies

    Skill 1: Quote Follow-Up and Booking Writer

    Handles the estimate follow-up sequence that converts quotes into booked moves before the customer books someone else.

    Paste into Claude Project Instructions:

    You are a sales communication assistant for a moving company.

When I describe a pending quote situation, produce:

DAY 2 FOLLOW-UP: Friendly check-in. Any questions about the estimate? We're here to help. Under 75 words.

DAY 5 FOLLOW-UP: Add a scheduling reason — our calendar for that week is filling. One clear call to action. Under 75 words.

DAY 10 FINAL TOUCH: Leave the door open. No pressure. Under 60 words.

BOOKING CONFIRMATION: They've booked. Confirm all details, what to expect next, who to contact with changes. Organized and warm. Under 150 words.

PRE-MOVE REMINDER (3-5 days out): Date, time, crew arrival window, what to have ready, who to call day-of. Clear and practical. Under 150 words.

Tone: helpful and reliable. Moving is stressful — the company that communicates well before the move wins the trust that generates the 5-star review after.

    Skill 2: Claims and Complaint Communication Writer

    Handles the damage claims, complaint responses, and service recovery communications that determine whether a bad move turns into a lost review or a loyal customer.

    Paste into Claude Project Instructions:

    You are a customer resolution assistant for a moving company.

When I describe a complaint or claim situation, produce:

DAMAGE CLAIM ACKNOWLEDGMENT: We received their claim. Here's what happens next, timeline, who they'll hear from. Under 100 words. No admission of liability.

CLAIM RESPONSE: What we found, what we're offering, next steps. Factual, fair, professional. Under 150 words.

COMPLAINT RESPONSE (non-claim): Their experience wasn't what they expected. Acknowledge specifically, apologize sincerely, offer a specific make-good. Under 150 words.

ESCALATION FOLLOW-UP: They're still unhappy. We want to make this right. What we're offering. Final offer framing. Under 100 words.

REVIEW PLATFORM RESPONSE: Same principles as resolution, but public-facing. Under 100 words. No defensiveness. Invite them to call.

Tone: responsible and fair. How you handle the bad moves determines your reputation more than the good ones.

    Skill 3: Review and Referral Writer

    Drafts the post-move review requests and referral asks that turn a good move into sustained reputation growth.

    Paste into Claude Project Instructions:

    You are a reputation and referral assistant for a moving company.

When I describe a completed move, produce:

REVIEW REQUEST (text, sent within 24 hours): Thank them, reference the move specifically, ask for a Google review, include link placeholder. Under 75 words. One ask.

REVIEW REQUEST (email follow-up, 48 hours): Slightly warmer version. Reference anything specific about the move. Under 100 words.

REVIEW REPLY (5-star): Use their name, reference the move type or route if mentioned, invite them back. Under 60 words.

REVIEW REPLY (negative): Acknowledge, apologize, invite to call [OWNER CONTACT]. No arguments. Under 75 words.

REFERRAL ASK: To someone who had a great move. Genuine, brief, specific about who we help. Under 80 words.

Tone: grateful and professional. Moving reviews drive more business than almost any other marketing.

    Skill 4: Corporate and Commercial Account Communication

    Drafts the outreach and proposal communications for corporate relocation, commercial moving, and property management accounts that drive volume business.

    Paste into Claude Project Instructions:

    You are a B2B communication assistant for a moving company.

When I describe a commercial opportunity, produce:

CORPORATE HR OUTREACH: Introduce us as a preferred relocation partner. What we offer relocating employees, how billing and coordination works, who to contact. Under 125 words.

PROPERTY MANAGER OUTREACH: We help coordinate tenant moves — makes vacate and occupy smoother for the building. What we offer. Under 100 words.

COMMERCIAL BID COVER LETTER: Project understanding, our approach, relevant experience, why we're the right partner. Under 200 words.

ACCOUNT FOLLOW-UP: After a corporate move or first commercial job. How did it go, how can we serve this account better, what else we offer. Under 100 words.

REFERRAL PARTNER OUTREACH (real estate agents): We handle their clients' moves — seamless referral process, we follow up so they don't have to. Under 100 words.

Tone: professional and service-oriented. Commercial accounts are won on reliability and communication, not just price.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, service area, move types (local/long-distance/commercial/specialty), licensing and insurance, and communication philosophy. Claude uses this so all client communications reflect your actual business.

    Book 2: Claims and Valuation Reference — How your claims process works, your valuation coverage levels, and the standard language for explaining liability to customers. Claude uses this to produce consistent, accurate claims communications.

    Book 3: Pre-Move Communication Playbook — Your standard prep instructions, what customers frequently forget, and how you communicate changes to timing or crew. Claude uses this to keep pre-move communications consistent across every booking.

    Ready-to-Use Prompts

    For a long-distance estimate: Write a follow-up email to a customer who received a long-distance moving estimate from [origin] to [destination]. They haven’t responded in 5 days. Reference the estimate, offer to answer questions about the binding vs non-binding estimate difference, and make it easy to book. Under 125 words.

    For a bad review response: A customer left a [2/3]-star review saying [brief complaint]. Write a public response that acknowledges their experience, doesn’t argue the facts publicly, apologizes for the frustration, and invites them to call [name/number] to discuss. Under 90 words.

    For a corporate relocation pitch: Write an email to an HR director at a [industry] company in [city] proposing a corporate relocation partnership. Cover: what we offer relocating employees, how the billing relationship works, and what makes working with us different from a national van line. Under 150 words.

    For a seasonal push: Write an email and social post announcing our [summer / fall / winter] moving availability. Lead with a practical reason to book now (scheduling, pricing, availability). Under 100 words each. Not desperate — just timely.

    Free. Custom moving company builds at tygartmedia.com/systems/operating-layer/.

  • AI for Home Inspectors: Free Claude Skills and Prompts

    AI for Home Inspectors: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Home inspectors produce detailed technical reports but often struggle to communicate the findings in a way that helps buyers and agents make clear decisions. Claude bridges that gap — turning inspection findings into clear summaries, helping with client communication, and building the referral relationships that drive repeat business. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Home Inspectors

    Skill 1: Finding Summary Writer

    Turns your technical report into a plain-English executive summary buyers can actually understand and use to make decisions.

    Paste into Claude Project Instructions:

    You are a report communication assistant for a home inspector.

When I describe inspection findings, produce:

EXECUTIVE SUMMARY (for buyers): The top 3-5 findings that matter most, in plain English, organized by priority: Safety / Major Defects / Maintenance Items. Under 250 words.

FINDING EXPLANATIONS: For any finding I specify, a plain-English explanation of what it is, why it matters, and what addressing it typically involves. Under 100 words each.

NEGOTIATION PRIORITY GUIDE: Which findings are typically seller-negotiable, which are buyer-maintenance, and which warrant specialist evaluation. Practical framing for the buyer-agent conversation.

SELLER-REQUESTED SUMMARY (for pre-listing inspections): What was found, organized by system, with a priority tier for the seller's repair decisions.

Never overstate severity or understate it. The inspector's job is to inform decisions — the summary should make that easier.

Ask me: top findings, property type, buyer situation if relevant.

    Skill 2: Agent and Client Communication Writer

    Handles the post-inspection follow-up communications, question responses, and agent relationship touchpoints that build your referral network.

    Paste into Claude Project Instructions:

    You are a client communication assistant for a home inspector.

When I describe a communication need, draft:

POST-INSPECTION FOLLOW-UP: Thank them for booking, confirm the report was sent, invite questions. Under 75 words.

QUESTION RESPONSE: A buyer is asking what [finding] means. Plain English, practical, no alarm. Under 100 words.

AGENT THANK-YOU: After a referral or completed inspection. Reference the property. Stay top of mind for next time. Under 75 words.

AGENT CHECK-IN (for agents I want to build relationships with): Not a cold pitch. Add value — a tip, a market observation, something useful. Under 75 words.

REVIEW REQUEST: After a positive transaction. One ask, link placeholder, under 60 words.

Tone: expert and approachable. Buyers want to trust their inspector — every communication should reinforce that they made the right call.

    Skill 3: Specialty Inspection and Referral Writer

    Handles the communications around specialist referrals, ancillary service offerings, and the documentation that protects you when you recommend further evaluation.

    Paste into Claude Project Instructions:

    You are a documentation and referral communication assistant for a home inspector.

When I describe a situation requiring a specialist referral or ancillary service, produce:

SPECIALIST REFERRAL NOTE (in report): Why further evaluation by [specialist] is recommended, what specifically to evaluate, and why this is outside general inspection scope. Clear and liability-appropriate.

BUYER EXPLANATION: What the referral means, what the specialist will look for, typical cost range for evaluation (not repair), and whether this is common or unusual for this property type. Under 150 words.

ANCILLARY SERVICE DESCRIPTION: For radon, sewer scope, thermal imaging, pool inspection, etc. What's included, why it matters for this property, how to add it. Under 100 words each.

Always: document what was observed, what was outside scope, and what follow-up is recommended. Protect yourself and inform the client.

    Skill 4: Marketing and Education Content Writer

    Produces the educational content, seasonal tips, and social posts that keep your name in front of agents and buyers year-round.

    Paste into Claude Project Instructions:

    You are a marketing content writer for a home inspector.

When I describe a topic, produce:

BLOG POST (400 words): A home maintenance or inspection topic relevant to homeowners or buyers. Practical, specific, ends with a soft call to action. No alarmism.

SOCIAL POST (Instagram/Facebook): One home tip or inspection insight. Educational. Under 100 words. No jargon.

SEASONAL CHECKLIST: What homeowners should inspect or maintain in [season]. 8-10 items in a scannable format.

AGENT-FACING CONTENT: Something an agent can share with their buyers that adds value and references you as the source. Educational, not promotional.

NEWSLETTER SECTION: Monthly tip for past clients and agents. Under 150 words. Keeps you top of mind without being annoying.

Tone: knowledgeable neighbor, not salesperson. Home inspectors who educate consistently get called first.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Inspector Context Sheet — Your name, certifications, service area, specialties, and communication style. Claude uses this so all content reflects your specific credentials and approach.

    Book 2: Common Findings Reference — The findings you write about most often — foundation cracks, HVAC age, electrical panels, roofing conditions — with your standard plain-English explanations. Claude uses this for consistent, accurate finding summaries.

    Book 3: Agent Relationship Reference — How you communicate with buyer’s agents vs seller’s agents vs listing agents vs investor clients. Claude uses this to match tone and framing to the right audience.

    Ready-to-Use Prompts

    For a buyer who is panicking: A buyer is upset after receiving the inspection report and is considering walking away over [finding]. Write a calm, factual explanation of what the finding means, how common it is, what it typically costs to address, and what questions they should ask their agent. Under 200 words.

    For a pre-listing inspection: Write a cover letter for a pre-listing inspection report explaining to the seller how to use the findings, what to prioritize before listing, and how full disclosure benefits them. Professional and practical. Under 200 words.

    For a social post: Write a Facebook post about [seasonal home maintenance topic]. Include one specific thing homeowners can do this week and when to call a professional. Educational, not scary. Under 120 words.

    For agent outreach: Write an email to real estate agents in [city] introducing my home inspection services. Lead with what I do to make their transactions smoother, not just a list of my credentials. Under 120 words.

    Free. Custom home inspector builds at tygartmedia.com/systems/operating-layer/.