August 2026 · 6 min read
Cisco equips all 90,000 staff
with a personal AI agent

Key Definitions
MyAgent The personal AI agent Cisco announced on August 27, 2026, rolling out to all ~90,000 employees: persistent memory, execution across Outlook/Webex/Jira/SharePoint, background operation, and a 'chief dispatcher' that connects to 800+ specialist agents behind it.
Circuit Cisco's internal enterprise AI platform built since 2023 (core team of ~40): a governed, multi-model-agnostic stack offering models, knowledge bases, search, agents and connectors, with an enterprise Agent Registry and MCP Registry — agents pass identity, permission and security review before they can be called.
Intelligent Routing Matching tasks to models by capability and cost: Splunk monitors token consumption, deterministic steps go to rules, APIs and traditional automation, and the LLM handles only planning and judgment — so 90,000 always-on agents never become an unmanageable compute bill.
On August 27, Cisco announced it is rolling out the personal AI agent MyAgent to all ~90,000 employees — not a pilot, a full company-wide launch. This is a structural re-organization of a Fortune 500 company around agents, and the cost and governance architecture it chose is becoming the template every peer is benchmarking against.
Not a chat box — an execution entry point
The notable thing about MyAgent is that Cisco is trying to turn internal AI from a chat box employees open voluntarily into an execution entry point that remembers continuously, calls tools across systems, and advances tasks in the background. It retains employee preferences, past interactions and work context; instead of typing specific instructions, employees describe a goal, context and expected outcome. MyAgent decides the steps, coordinates across Outlook, Webex, Jira and SharePoint, and keeps moving under appropriate human supervision.
It acts more like a chief dispatcher than a universal executor: behind it sit 800+ specialist agents covering inbox triage, spam filtering, reply drafting, market-intelligence aggregation and more. The underlying Circuit platform already hit 90% employee adoption by July, with 21,000 engineers using AI coding tools — over 80% of them weekly.
The economics: not every request needs the strongest model
The binding constraint of company-wide agents is the bill. Cisco's answer is layering: roughly 50-60% of AI requests are handled by open-weight models running on GPUs in Cisco's own data centers; 20-30% go to traditional software automation (rules, APIs, deterministic flows); only a small share calls external frontier models. Tool selection matches capability and cost rather than chasing model call volume and token consumption.
For observability, Cisco uses Splunk to track token usage and an intelligent router that assigns each task to a model with sufficient capability at lower cost; anything a deterministic flow can do is not forced onto an LLM. This is the most pragmatic part of the MyAgent architecture: the LLM is the planning and judgment layer, and high-determinism steps sink down to rules and APIs. Otherwise 90,000 always-on agents would turn the technical vision into an out-of-control compute bill on day one.
The financial signal runs on the same curve: Cisco's AI orders jumped from $2B in FY2025 to a $9B FY2026 guide, with the stock up about 52% year-to-date as of July. Management and Discussion sections in public filings are now 80-90% AI-drafted — even the CFO uses his own agent to benchmark against peers.
Governance: Agent Registry and MCP Registry
At this scale, governance has to be a mechanism, not a slogan. Circuit runs an enterprise Agent Registry and MCP Registry: agents, connectors and MCP servers built by any team are registered in a unified directory and must pass identity, permission and security review before other systems can call them. That is the infrastructure that keeps shadow agents out — no registration, no review, no call rights.
This design answers the hard governance question of company-wide agents: when every employee has an always-on agent, how are permissions granted, scoped, revoked, and how are an agent's actions explained and rolled back? Registry plus identity review plus permission boundaries turns governance into a workflow rather than after-the-fact auditing. Cisco is now selling the same governance model it validated on 90,000 employees — the move it describes as going from experimentation to execution, and from execution to durable advantage.
Read this separately from the layoff narrative
On May 14 Cisco cut 4,000 jobs, officially framed as "realigning resources" toward silicon, optics, security and AI rather than pure cost-cutting. Stanford SIEPR data adds a colder background — the "junior-gap paradox": AI is hollowing out entry-level knowledge work, and enterprises that automate foundational tasks are losing the pipeline that trains the next generation of experts.
Cisco's official position is that MyAgent does not replace the 90,000 employees but expands their capabilities, freeing people for issues that require judgment and impact. But when 80-90% of filing drafts are AI-generated and 4,000 people have been cut, the line between "expanding capability" and "replacing work" is one every enterprise will have to draw for itself.
Four questions for your enterprise
Is your agent a planning layer over deterministic execution?
The cost floor of always-on agents is layering: LLM for planning and judgment, rules and APIs for deterministic steps. An all-LLM architecture breaks at 100 employees, let alone 90,000.
Do you have an agent registry?
No registry, no governance. Agents, connectors and MCP servers register once, pass identity and permission review, then go live. It is the only mechanism that actually eliminates shadow agents.
Can you route each task to a capability-matched model?
Intelligent routing plus token observability (Cisco uses Splunk) is not an optimization — it is the survival condition of company-wide agents. Capability matched to cost, not capability maximized.
Can your agent's actions be explained and revoked?
When employees entrust their work context to an always-on agent, the system must explain every step and roll back on error. An unexplainable, irreversible agent loses trust at the first incident.
Once employees habitually describe goals to a personal agent that then calls Outlook, Jira and SharePoint, the center of gravity in enterprise software shifts: vendors once locked users in through interfaces, workflows and data formats; tomorrow the thing employees touch most may be the agent, with the underlying SaaS retreating into data, permissions and APIs. Whoever controls this new entry point between people and all enterprise systems may hold the most important position in the next generation of enterprise software.
References
- PYMNTS: Cisco Deploys Custom AI Agent to Entire 90,000-Person Workforce (2026-08-27) — https://www.pymnts.com/news/artificial-intelligence/2026/cisco-deploys-custom-ai-agent-to-entire-90000-person-workforce/
- 36Kr: Cisco Deploys Personal AI Agents for 90,000 Employees (2026-08-31) — https://eu.36kr.com/en/p/3960230958693507
- Forkast: Cisco Is Deploying AI Agents to All 90,000 Employees. Here's What the Economics Look Like. (2026-08-08) — https://forkast.news/cisco-is-deploying-ai-agents-to-all-90000-employees-heres-what-the-economics-look-like/
FAQ
Is MyAgent a model Cisco trained itself?+
No. It is a 'super agent' built internally on Circuit, the platform Cisco has run since 2023. Roughly 50-60% of AI requests are handled by open-weight models running on GPUs in Cisco's own data centers, 20-30% by traditional software automation, and only a small share calls external frontier models.
Why not route every task to the strongest model?+
Cost architecture. If 90,000 always-on agents all used the strongest model, the technical vision would immediately become an out-of-control compute bill. Intelligent routing matches capability to cost; deterministic steps go to rules and APIs, with the LLM as the planning and judgment layer.
What review does an agent pass before going live?+
Circuit maintains an enterprise Agent Registry and MCP Registry: agents, connectors and MCP servers are registered in a unified directory and must pass identity, permission and security review before other systems can call them. Governance before rollout, not after.
How large is the deployment?+
Circuit reached 90% employee adoption by July; 21,000 engineers use AI coding tools (over 80% weekly). From August 27, MyAgent became the personal entry point for all ~90,000 employees.
Is this about layoffs or capability expansion?+
Cisco cut 4,000 jobs on May 14, calling it 'realigning resources' toward silicon, optics, security and AI. Officially MyAgent does not replace the 90,000 employees — it expands what they can do. Financially, AI orders rose from $2B in FY2025 to a $9B FY2026 guide.
Related Articles
Agent Economy Outruns Its Meters: IDC on Cost Governance
95% of enterprises run production agent workflows, averaging $117,558 monthly — yet 67% blew budget. An overrun and a governance gap are the same failure.
Toyota's 50+ production agents: platform economics behind 4-day delivery
Toyota ships 50+ production agents on a platform-first model — 4 days to launch, but approval chains and single points of dependency are the other side of platform economics.
McKinsey 2026: Agent scaling accelerates while EBIT contribution stalls
Deployment scales up, profit contribution does not — the gap between scaling and EBIT is exactly the economic account company-wide agentification must get right.
Microsoft Agent 365 governance playbook: from visibility-first to scaled governance
Microsoft stands up Agent 365 in its own tenant: an agent registry as the single source of truth, then rule engines and bulk operations to govern at hundreds of thousands of agents.