Claude BlogMon, Aug 17, 2026

How ABC Legal turned every employee into a builder with Claude Managed Agents

ABC Legal transformed their organization’s AI adoption from scattered experiments to a governed fleet of specialized agents with Claude. When Brandon Fuller, CTO of ABC Legal, a U.S.-based legal document delivery company, rolled out Claude Enterprise to the company's 1,100 employees earlier this year, something clicked immediately. Teams across the company (service of process, eFiling, and appearance counsel operations, plus marketing, compliance, finance, and more) started building automations on their own, without being asked. "Our users really flocked to it," Fuller recalls. "They saw the ease of use of connectors and tools, and suddenly we had people all over the organization automating the tasks that had always eaten up their day." It was exactly the kind of adoption any CTO hopes for. But Fuller saw an opportunity to go further: what if ABC Legal could also run a fleet of AI agents that were versioned, observable, and always on? That ambition came down to infrastructure. Early agents lived wherever their builder happened to put them, as scheduled tasks on individual desktops. Moving them off personal machines would let them run unattended and give Fuller a single view of what had been built, what it cost, and whether it ran last night. So he deployed Claude Managed Agents: one common deployment structure, shared workspaces, a single audit and billing surface, and always-on agents in the cloud instead of on a person’s laptop. As of July 2026, Fuller and his team at ABC Legal have tracked: Here’s how they got there and what they learned in the process. When they first deployed Claude Managed Agents, Fuller had the team define every agent as code. He believes this is the natural form for an agent to take. As he explains, “an agent is really just structured text, a prompt plus configuration, and anything that is text can live in a repository where the whole company can see it, review it, and improve it.” An agent's prompt, tool list, schedule, credentials, and memory all go into configuration files kept in a git repository alongside the company's software. Nothing about an agent changes except through a pull request someone approves, which gives every agent version history, code review, rollback, and an audit trail. He spent a week building a starter kit with two templates, stored in dedicated git repositories. One is for event-driven agents, which start the moment something happens, like a new job arriving or a document coming back from a court. The other is for scheduled agents, which run on a timer: hourly, daily, or weekly. Each agent lives in its own folder with a standard structure: a JSON config file, a system prompt in Markdown, deployment scripts, and operational documentation. Merging a change into the main branch deploys the agent automatically. A builder never has to write software. They clone the repo, copy a starter template, tell Claude Code what the agent should do, and get back everything the agent needs: config, prompt, credential store, and memory. Fuller gathered the company’s 15-person steering committee, drawn from finance, marketing, operations, and development (none of them software developers), and had them clone the repository and build Managed Agents using Claude Code. The goal was to prove that non-developers could build production agents themselves. If every agent had to route through the dev team, that bottleneck would cap how fast the whole company could move. What made it safe is that they were not writing software. Instead, they were filling in configuration and a prompt, and Managed Agents supplied the runtime. "I had to explain what a PR was to them. A lot of [the non-software engineers] thought it meant running, like a PR, the fastest you can,” he said. “Now they're doing pull requests and sending them to each other." Within a week, all 15 employees had working agents. Those builders went back to their teams and trained others. Within a month, roughly 50+ agents were running across ABC Legal. Each agent has a name, an owner, and a single job.

What shipped & dropped across AI labs, today.

·last sync 45m ago

Today

Mon · Aug 17 · 2 posts

Claude Blog19h ago

How ABC Legal turned every employee into a builder with Claude Managed Agents

ABC Legal transformed their organization’s AI adoption from scattered experiments to a governed fleet of specialized agents with Claude from Anthropic.

Modelsclaude.com/blog/how-abc-legal-turned-every-employee-into-a-builder-with-claude-managed-agents

Cursor19h ago

Origin Code Hosting

Cursor can now host your code. Origin begins rolling out today in early beta on all paid plans. We're starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync. Agent-native features ship soon. #Origin Repos The new Codebase tab is home for Origin repos. Click +New to create a new repo and name it. Once you do, a page shows you how to install the CLI, with commands for how to clone a repo or push a local project. Push, and your code is hosted on Origin. Name your codebase when you create your first repo. That name becomes part of every repo's URL: cursor.com/codebase/acme-corp. #Bring your GitHub repos Your GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick your org, and you'll see the repos you can sync. Select one and Cursor pulls it in. You choose what gets synced and can disconnect a repo at any time. Anyone with read or write access to a synced repo can view it in Cursor too. Synced repos update in real time. Browse, search, and pull from the copy in Origin. Pushes keep going to GitHub, which stays the source of truth for anything started there. Icons next to each repo name tell you which ones Cursor hosts and which came from GitHub. #Pull requests Every repo has pull requests. Open one to see the timeline, commits, checks, and files changed. Review the diff, leave comments, and merge. Pull requests on synced repos sync both ways: comment in Cursor and it posts to GitHub, react or reply on GitHub and it shows up in Cursor within seconds. Got a review assigned to you on GitHub? Review and merge it from Cursor. #Agents in every repo Your code, PRs, and agents are now in the same place. Ask Cursor questions about code you're browsing. It can answer, make changes, update PRs, or push a branch. #App extensions for Cursor repos We're building an app ecosystem so your whole stack works seamlessly with Origin. Integrations with Vercel, Depot, and Buildkite are already available, with more coming soon. Connect Vercel from a repo's Apps tab and every PR gets a preview deployment where you can test and make comments. Merge, and it ships to production. For CI, connect Depot or Buildkite. Both run your existing GitHub Actions workflows and Buildkite also runs its native pipelines. #Settings Every repo has settings. Check sync status for GitHub repos, manage who has access, and see which apps are connected. Origin is rolling out in early beta to all paid plan users starting today, except enterprise orgs whose admins opt out. Name your codebase and create your first repo. Learn more in our docs or get started today.

Toolscursor.com/changelog/origin-code-hosting

Friday

Fri · Aug 14 · 4 posts

Anthropic3d ago

How Claude’s text watermark works

Modelsanthropic.com/news/claude-text-watermark

GitHub3d ago

Grok 4.6 is now available in GitHub Copilot

Grok 4.6, xAI’s latest reasoning model, is now rolling out in GitHub Copilot. It is designed for agentic coding and complex multi-step workflows. In our internal testing, Grok 4.6 showed…

Modelsgithub.blog/changelog/2026-08-14-grok-4-6-is-now-available-in-github-copilot

xAI3d ago

Grok 4.6 in GitHub Copilot

Grok 4.6, our latest coding model, is now available in GitHub Copilot.

Modelsx.ai/news/grok-4-6-github-copilot

Claude Blog3d ago

Maximizing the value of your Claude Code sessions

Practical tips for how to run efficient sessions that get the most value from every token.

Practicesclaude.com/blog/maximizing-the-value-of-your-claude-code-sessions

Thursday

Thu · Aug 13 · 8 posts

GitHub4d ago

GitHub Copilot weekly releases — August 10

From new models and portable plugins to smoother agent workflows, this week’s updates make GitHub Copilot more flexible across editors, the command line, and the Copilot app.

Toolsgithub.blog/changelog/2026-08-13-github-copilot-weekly-releases-august-10

Claude Blog4d ago

Securing the frontier: How JetBrains evaluates and deploys Claude Fable 5

How JetBrains uses Claude Fable 5 and why they view safeguards and data retention as central to working with frontier models.

Modelsclaude.com/blog/how-jetbrains-evaluates-and-deploys-claude-fable-5

GitHub4d ago

Gemini 3.7 Flash is now available in GitHub Copilot

Gemini 3.7 Flash, Google’s latest Flash model, is now rolling out in GitHub Copilot. From our early testing, the model has made improvements in web and app development and agentic…

Toolsgithub.blog/changelog/2026-08-13-gemini-3-7-flash-is-now-available-in-github-copilot

Claude Blog4d ago

Self-service data analytics in Slack: how Anthropic deploys Claude Tag for ad-hoc questions

How Anthropic's data team uses Claude Tag for self-service data analytics with the same governed definitions analysts use.

Businessclaude.com/blog/self-service-data-analytics-in-slack-how-anthropic-deploys-claude-tag-for-ad-hoc-questions

Google AI for Developers4d ago

HeyGen x Google Cloud: Bringing Avatar IV to TPUs

HeyGen ported their 18B+ parameter Avatar IV video generation model to Google Cloud's Trillium (v6e) TPUs via torchax and XLA, utilizing FSDP and Ulysses sequence parallelism across an eight-chip mesh. To achieve a 1.86x speedup for real-time streaming, the engineering team pipelined exposed all-to-all collectives, aligned sparse attention block sizes to eliminate mask padding, and bypassed softmax serial dependencies using a precomputed Cauchy-Schwarz upper bound. These custom Pallas kernel and compiler optimizations were deployed only after passing rigorous two-tier quality gates to guarantee byte-identical or mathematically equivalent pixel outputs.

Modelsdevelopers.googleblog.com/heygen-x-google-cloud-bringing-avatar-iv-to-tpus/

Cursor4d ago

Cloud Agents Start 3x Faster with Builds

Agents do their best work when they start in a ready environment: repos cloned, dependencies installed, and your install script already run. This release introduces builds: ready-to-use copies of your development environment that Cursor prepares in the background. Agents boot into a ready environment instead of setting up from scratch each session. Builds are included with Cloud Agents at no additional cost. #Faster starts Cursor runs a new build of your environment regularly. When a build succeeds, it becomes the environment future agents start from. Cursor keeps warm copies ready so the next agent does not wait. Internally, our environments now boot 10x faster, with 3x faster time to first token. Use your install command for anything that can be prepared ahead of time. The start command still runs when you first prompt an agent and should focus on services that need to be fresh in the session. #More resilient agent runs When a bad commit or dependency update breaks your environment, agents keep using the last successful build. The broken build never becomes active, you are notified of the issue, and your agents keep working while you debug in the background. #Build history and debugging Each environment has a Builds tab in the Cloud Agents dashboard. You can inspect build status, logs, commit SHAs, and which build each agent run used. Agents can also inspect and manage builds using built-in tools. #Getting started New environments use Builds automatically. For an existing environment, open it in the Cloud Agents dashboard, go to the Builds tab, and click Enable Builds. Or click Run setup agent first to test the migration and review any proposed config changes. You can also trigger a Build manually, debug a failing Build with an agent, and control how stale Builds refresh with a configurable threshold. Learn more in our announcement post and docs.

Toolscursor.com/changelog/08-13-26

Google AI for Developers4d ago

Introducing Credentio: Open Source C++ Library for C2PA Content Credentials from Google

Credentio is a newly released, open-source C++ library from Google that allows developers to integrate high-performance, local-first validation of C2PA Content Credentials into their client and server applications. By processing assets entirely locally with a highly optimized memory footprint, the library delivers instant validation verdicts for multi-gigabyte media files without incurring cloud latency, bandwidth costs, or data privacy risks. The library currently features deep manifest parsing alongside configurable trust list integration, and is available now on Google Source with future plans to support full credential generation and embedding.

Toolsdevelopers.googleblog.com/introducing-credentio-open-source-c-library-for-c2pa-content-credentials-from-google/

Claude Blog4d ago

Claude Tag now reads even more of the room

Claude has more context to decide when to proactively collaborate in Slack (and when not to)

Modelsclaude.com/blog/claude-tag-now-reads-even-more-of-the-room

Wednesday

Wed · Aug 12 · 3 posts

Claude Blog5d ago

The Claude in Chrome side panel is now Claude Cowork

The Claude in Chrome side panel is now a Claude Cowork session. Your conversations, skills, and connectors carry between the browser and the Claude apps.

Modelsclaude.com/blog/cowork-chrome-side-panel

GitHub5d ago

Agent Plugins 1.0 in VS Code, Copilot CLI, and the Copilot app

You can now build a plugin once and use it across all compatible agent clients. We published Agent Plugins 1.0 on August 6 with AWS, Anysphere, Microsoft, OpenAI, and Vercel.…

Toolsgithub.blog/changelog/2026-08-12-agent-plugins-1-0-in-vs-code-copilot-cli-and-the-copilot-app

xAI5d ago

Introducing Grok 4.6

Grok 4.6 builds on Grok 4.5 with a particular focus on long-running agents and more ambitious interactive and visual work.

Modelsx.ai/news/grok-4-6

Tuesday

Tue · Aug 11 · 3 posts

GitHub6d ago

Copilot memory and Ollama in GitHub Copilot for JetBrains

This update brings persistent memory, local model access, and more enterprise controls to GitHub Copilot for JetBrains. It also improves everyday chat workflows and resolves reliability issues across MCP servers,…

Toolsgithub.blog/changelog/2026-08-11-copilot-memory-and-ollama-in-github-copilot-for-jetbrains

GitHub6d ago

Upcoming deprecation of MAI-Code-1-Flash

With the launch of MAI-Code-1.1-Flash, we will deprecate MAI-Code-1-Flash across all GitHub Copilot experiences on September 10, 2026: Model Deprecation date Suggested alternative MAI-Code-1-Flash 9-10-2026 MAI-Code-1.1-Flash Please update your workflows…

Toolsgithub.blog/changelog/2026-08-11-upcoming-deprecation-of-mai-code-1-flash

GitHub6d ago

MAI-Code-1.1-Flash available in GitHub Copilot

MAI-Code-1.1-Flash, Microsoft’s latest small-tier coding model, is now rolling out in GitHub Copilot. Building on MAI-Code-1-Flash, it adds native vision support for image understanding and delivers improvements across coding quality,…

Modelsgithub.blog/changelog/2026-08-11-mai-code-1-1-flash-available-in-github-copilot

trigger