Enterprise AI Automation.Agents that replace operational work, not just write emails.
Enterprise automation is where agentic AI pays back fastest: operational workflows, support and service pipelines, ERP integrations, content-at-scale. The wins are concrete — hours saved per ticket, headcount that scales sub-linearly, decisions logged for audit. The patterns matter more than the model.
Where automation pays back fastest
Operational triage (routing, processing, escalation), customer support agents that hit ticket systems directly, and content-plus-SEO pipelines (research → outline → write → review). These are workflows with clear inputs, measurable outputs, and decisions that can be logged.
Why IT services teams ship faster than expected
IT services teams have the right combination: existing ops workflows to automate, domain context to write good tool descriptions, and developer headcount to maintain the systems. The blocker is rarely capability — it is usually scoping the first agent narrowly enough to actually ship.
What we deliver on consulting engagements
Architecture design, production-grade implementation using Claude API and MCP, full observability (Langfuse), structured outputs (Pydantic), retry semantics, and a real handoff so your team can maintain and extend it. Working agents, not slides about agents.
Deep dives on Enterprise AI Automation
Claude cyber-eval incidents: the sandbox escape checklist I run before any offensive agent test
On July 30, 2026 Anthropic disclosed three incidents where Claude models reached live production systems during third-party cybersecurity evaluations. The root cause was a harness misconfiguration that left internet access open while prompts claimed there was none. Here is the defense-in-depth checklist I now require before any capture-the-flag or offensive agent eval.
Cursor's agent swarm economics: why frontier planners and cheap workers beat solo GPT bills
Cursor's July 2026 swarm write-up rebuilt SQLite in Rust from the docs and measured planner vs worker spend. Frontier-only GPT-5.5 hit about $10.5k; Opus 4.8 planning with Composer 2.5 workers landed near $1.3k at similar quality. Here is how I translate that into routing rules for production graphs.
Graph engineering with Claude Code: the 14-step roadmap I use when linear agents stall
A straight-line agent is a degenerate graph. Claude Code dynamic workflows move orchestration into JavaScript so subagents fan out, verify, and converge without stuffing every intermediate result into one context window. Here is the 14-step roadmap I map onto production work, with topology diagrams, contracts, and the patterns I already ship.
Gemini 3.6 Flash shipped, 3.5 Pro did not: the routing checklist I run after July 21
On July 21, 2026 Google released Gemini 3.6 Flash ($1.50/$7.50 per million), 3.5 Flash-Lite ($0.30/$2.50, ~350 tok/s), and a limited-access 3.5 Flash Cyber via CodeMender. Gemini 3.5 Pro stays in partner testing. Here is how I re-benchmark cost per completed task against Sonnet 5 and Fable without betting the roadmap on Pro.
Claude Code Week 29: live MCP artifacts change the blast radius of a shared dashboard
Claude Code Week 29 (July 13–17, v2.1.207–v2.1.212) lets published artifacts call MCP connectors on each view through the viewer's own connections, with first-call approval. Public sharing links, editor roles, screen reader mode, and auto-background for long MCP calls shipped in the same window. Treat live artifacts like production integrations, not pretty exports.
MCP just got a rival enterprise protocol: the portability playbook I run before teams pick a side
In mid-July 2026, reporting put Google, Microsoft, Salesforce, Snowflake, and ServiceNow behind a shared enterprise agent backend protocol framed as a counter to Anthropic's MCP. Protocol wars are procurement stories dressed as plumbing. Here is how I keep tool contracts, auth, and gateways portable while MCP 2026-07-28 still ships on July 28.
Claude Code Week 28: the desktop browser and /doctor checklist I run before enabling it org-wide
Claude Code Week 28 (July 6–10, releases v2.1.202 through v2.1.206) shipped a sandboxed in-app browser on Desktop and upgraded /doctor from a read-only report into a repair tool. Auto mode also blocks transcript tampering. Here is the governance checklist I run before teams turn browsing and auto-fix on for every engineer.
Claude Cowork is not Claude Code for civilians: the knowledge-worker playbook after the mobile launch
Anthropic shipped Claude Cowork on mobile and web July 8, starting with Max subscribers. Usage data from 1.2 million sessions shows more than 90% of Cowork work is non-technical: memos, RFP reviews, inbox triage, decks. Tasks run in the cloud, sync across devices, and continue when you close the app. Here is how I govern Cowork without treating it like a coding agent.
Claude Sonnet 5 is the new default: the migration checklist I run before swapping claude-sonnet-4-6 in production
Anthropic shipped Sonnet 5 on June 30 as default on Free and Pro chat and as claude-sonnet-5 on the Platform API at $2/$10 per million through August 31. Three breaking changes matter for agent builders: adaptive thinking on by default, manual extended thinking removed, and non-default sampling parameters return 400. The tokenizer adds roughly 30% tokens for the same text. Here is the swap checklist.
Fable 5 is back globally: the redeployment routing checklist I run before July 7
Anthropic restored Claude Fable 5 worldwide on July 1 after US export controls lifted June 30. Pro through Enterprise plans get up to 50% of weekly usage limits included through July 7, then usage credits. A new safety classifier blocks the Amazon-reported jailbreak in 99%+ of cases. Here is how I re-promote Fable without repeating June's config chaos.
Codex Record and Replay turns one demo into a Computer Use skill: how I inspect generated skills before trusting them unattended
Codex app 26.616 adds Record and Replay on macOS: perform a workflow once, Codex packages it into a skill you replay with different inputs. Thread handoff and automation run history ship alongside. Computer Use must be enabled. Here is the review checklist I run before any recorded skill runs unattended.
One agent spend dashboard for Cursor, Claude Code, and Copilot: what Copilot's ai_credits_used field unlocks
GitHub added ai_credits_used to the Copilot usage metrics API on June 19. It is a per-user total, not yet split by feature or model, but it closes a gap I have been papering over with spreadsheets. Here is how I unify Copilot credits with Claude API keys and Cursor team usage into one attributable spend view.
Fable 5 got suspended worldwide in three days: the frontier model adoption checklist I now run on every engagement
Anthropic launched Claude Fable 5 on June 9, promised included subscription access through June 22, then suspended Fable and Mythos 5 globally on June 12 after a US export-control directive. Most teams never finished piloting. Here is the governance checklist I use when capability, retention, pricing, and access can flip faster than your rollout calendar.
Claude Code Artifacts turn terminal output into live review pages: what Team and Enterprise buyers should pilot first
Artifacts in Claude Code beta publish self-contained HTML to claude.ai that republishes to the same URL as the session progresses, with version history and org-only sharing. Strict CSP, no external fetch, no backend. Requires Team or Enterprise and claude.ai login. Here is the workflow I use for PR walkthroughs and incident timelines without screenshot threads in Slack.
MCP Enterprise-Managed Authorization is stable: how IdP-provisioned connector access replaces per-server OAuth hell
EMA makes the organization IdP the decision-maker for which MCP servers a user can reach. Admins enable connectors once; clients exchange an Identity Assertion JWT for scoped tokens without redirecting every employee through OAuth per server. Anthropic ships it across Claude, Claude Code, and Cowork; VS Code supports it; Okta is the first IdP. Here is the pilot I run before July 28 stateless transport work lands.
Cursor cloud subagents in 2026: /in-cloud, /babysit, and /automate without losing your local guardrails
Cursor 3.7 lets you spin subagents in cloud VMs with /in-cloud, iterate on a PR until merge-ready with /babysit, and hand off between local and cloud sessions. Cursor 3.8 adds /automate and five GitHub review triggers. Here is the workflow I use so parallel cloud work does not bypass Auto-review, environment snapshots, or pre-push /review.
Agentjacking is real: poisoned Sentry errors can hijack Cursor, Claude Code, and Codex without touching your repo
Tenet Threat Labs injected a fake stack trace through a public Sentry DSN and watched 100+ coding agents execute attacker commands during normal triage. No git write access required. The agent treats the error as ground truth. Here is how I harden observability MCP feeds, scope triage prompts, and block auto-exec on untrusted telemetry.
The June 15 Claude billing change: Agent SDK credits, model retirement, and the checklist I run before anything breaks
Two Anthropic changes land on the same day: programmatic Claude usage moves to a separate monthly credit pool, and claude-opus-4-20250514 plus claude-sonnet-4-20250514 stop answering on the API. Interactive Claude Code is fine. Cron jobs and CI agents are not. Here is how I audit auth paths, claim credits, and grep for retiring model IDs before the first failed run.
Governing agent autonomy in 2026: Auto-review, pre-push review, and why approval prompts are not a security model
Cursor made Auto-review the default run mode and shipped /review so Bugbot runs before you push. Together they treat agent autonomy as a dial: low-stakes actions flow, high-stakes actions slow down. Here is how I wire that pattern into local agents, SDK headless runs, and CI without mistaking convenience for a hard security boundary.
Agentic RAG vs vanilla RAG: why a Sufficient Context Agent beats retrieve-then-pray
Google Research shipped Agentic RAG on Gemini Enterprise with a Sufficient Context Agent that refuses to answer when retrieval is incomplete. On factuality benchmarks they report up to 34% higher accuracy versus standard RAG. Here is when one-shot RAG is still enough, when you need iterative retrieval, and how I wire the pattern without blowing latency budgets.
Agentic transformation is an operating-model problem, not a model problem
Microsoft published a 6-step playbook for rolling agents out across an enterprise, and the line that matters is "you do not need a bigger model, you need a better operating model." That matches what I see in consulting: the pilots that die do not die on model quality, they die on ownership, evals, and governance. Here is how I read the playbook for IT services teams, and the operating-model gaps that actually stall agent rollouts.
Your agent's supply chain is the attack surface now
A poisoned VS Code extension spent eighteen minutes on the marketplace and walked off with Claude Code credentials and MCP configs. The model was never the target. Your agent's supply chain is: the extensions, skills, MCP servers, tool definitions, and keys it is allowed to touch. Here is how I harden all four layers, and the checklist I run on every deployment.
Inside Recruiting Atelier: a runnable reference for the primitives of an agentic system
A working open studio that vets duplicates, plans the run, screens, scores, shortlists, and notifies. The whole pipeline lives in roughly ninety lines of supervisor code and a tool registry you can read in one sitting. Here is what is inside, why every piece is there, and what you can copy into your own stack.
How an agentic studio screens, scores and shortlists candidates for your hiring team
Open Recruiting Atelier and you do not see a generic AI dashboard. You see five named specialists doing the work a screening team would do: catching duplicates, checking the brief, scoring on four dimensions, ranking, drafting the dispatch. Drop one CV or fifty. Click any candidate to see exactly why they landed where they did. This is what AI for recruitment looks like when it respects your judgment instead of replacing it.
Code agents vs skill agents: when to give an agent the keyboard and when to give it the toolbox
Two ways to let an agent act in the world. Code agents write fresh code into a sandbox. Skill agents pick from a curated menu. The choice should be made in the kickoff, not the postmortem. Here is the framing I use with clients, the four axes where they diverge, and the hybrid pattern most production systems become.
Tool registry design for agentic AI: how the wrong registry kills accuracy before the prompt is read
I reviewed a system last month with 47 tools in its registry and a 22 percent wrong-tool-selection rate. The team was about to migrate from Sonnet to Opus to fix it. The prompt was fine. The registry was the bug. This is the audit pattern I run on every client codebase before we change anything else, the seven failure modes I see in production, and the numbers from the cleanup.
AI agent vs agentic AI: what the distinction actually means when you ship one
Vendors blur the line because "agentic" sells. The two terms describe different architectures, with different cost shapes, different observability needs, and different scoping conversations. Here is the framing I use with clients and the three-question test for which one your project actually needs.
MCP governance just became a product: what Databricks Unity AI Gateway changes for enterprise agents
Every enterprise MCP deployment I have audited in the last six months has been hand-rolling tool-access policy, payload logging, and per-team cost limits on top of a gateway someone wrote in two days. Databricks just shipped that as a product. Here is what it actually changes, where the gaps still are, and the migration I would run for a Databricks shop.
The cheapest LLM call is the one you do not make. GitHub's 19-62% token cut, decoded
GitHub published an instrumented analysis of their agentic CI workflows and reported 19-62% token-cost reductions. The savings are the headline. The technique (pre-agentic data fetching and tool-registry hygiene) is the story most teams will miss.
MCP 1.0 is here. What changes for the servers you already wrote
The protocol stabilised. Most working servers will keep working. Three places the new spec actually requires changes (auth profile, server registry, streaming-response semantics) with diffs from a real migration.
Why I am replacing supervisor patterns with handoffs
Supervisors looked clean on paper and shipped slow in production. Handoffs read messier in the code but recover better when an agent loses the plot. Two real systems and where supervisors still earn their keep.
Prompt caching is not optional anymore. Measuring a 47% cost drop
A walkthrough from a client engagement: identifying stable prefixes, restructuring the system prompt for cacheability, and the telemetry that proved caching was actually working.
The agent observability stack we ship to every client
Traces, spans, evals, cost-per-completed-task, and the one dashboard panel that catches 80% of regressions. Vendor-agnostic; covers Langfuse, Honeycomb, and rolling your own.
Haiku 4.5 made our router 5x cheaper. The trade-off matters
Replacing Sonnet with Haiku in the dispatcher role cut our orchestration cost dramatically. It also cost us in two specific places I did not predict.
Eval datasets: stop testing your agents on the happy path
If your eval set is the demos you showed the client, you are testing the wrong thing. How we build evals from production failures and the minimum viable suite to ship.
Visual breakdowns on Enterprise AI Automation
Latest in Enterprise AI Automation
Agent Plugins 1.0 generally available in VS Code, Copilot CLI, and the Copilot app
Compliance API beta covers Claude Cowork and Claude Code sessions for Enterprise audits
Copilot for JetBrains: persistent memory, Ollama BYOK, and enterprise managed settings for plugins and MCP
Claude Code auto mode becomes the default August 14 for Pro, Max, and Team; classifier tokens no longer count on those plans
Claude Code self-hosted environments enter public beta on Team and Enterprise
Claude Enterprise inference hooks: inline DLP on prompts and tool responses across chat, Code, and Cowork
OpenAI Fast mode now supports long-context GPT-5.6 Sol, Terra, and Luna prompts above 272K tokens
DeepSeek V4-Flash official API enters public beta: re-post-trained 0731 checkpoint, Responses API and Codex support
Speaking on Enterprise AI Automation
How Enterprise AI Automation ships in our engagements
The pages below are the buyer-focused, conversion-grade versions of this topic — deliverables, methodology, ROI, security considerations, and CTAs to scope a real engagement.
Agentic AI Consulting
Designed, built, and handed off — production agentic systems for enterprise teams.
Explore the Agentic AI Consulting solutionMCP Integration
Custom Model Context Protocol servers that turn your systems into agent tools.
Explore the MCP Integration solutionAI Guardrails
Multi-layer safety, policy, and audit controls for agents in regulated environments.
Explore the AI Guardrails solutionAI Automation for Enterprises
Operational agents that replace manual workflows — triage, support, ERP integration, content pipelines.
Explore the AI Automation for Enterprises solutionEnterprise AI Automation — the questions teams actually ask
Train your team on Enterprise AI Automation
Two tracks — one for developers who build agents, one for business teams who use them. Customised to your stack, hands-on from session 1.
See Enterprise AI Automation training tracksShip your first Enterprise AI Automation system
Architecture design, production implementation on Claude API and MCP, full observability, and a real handoff. Working agents, not slides.
Explore Enterprise AI Automation consultingAdjacent topics to read next
Go deeper on this topic
New breakdowns on this and related agentic AI topics, plus what I am shipping for clients — one email on Thursdays.







