The week of August 3, 2026 covered 5 product areas across Annie and the Anyshift Product Updates series.
The headline is Cloudflare as a first-class edge source on the graph. Around it: our first Agent Plugins package so coding agents can query graph data, a much deeper Backstage plugin, report deep links that switch projects, and clearer Annie RCA language. For the Cloudflare narrative, start with Annie meets Cloudflare.
Cloudflare integration
Cloudflare is generally available. Open Integrations → Cloudflare, click Connect with Cloudflare, sign in, pick the account, and approve the read-only scopes. An Account API token remains available as a fallback when OAuth is not ready in your environment.
Once connected, Anyshift inventories zones, DNS records, certificates, WAF rulesets, load balancers, Workers, tunnels, and Access onto the versioned resource graph Annie uses for investigations. Hostname and edge config map onto the same topology as your cloud and Kubernetes resources. Zone-scoped grants soft-fail missing families instead of failing the whole sync. See the Cloudflare integration page and the setup guide for the full permission list.
First Agent Plugins package for the graph
We published our first Agent Plugins package so compatible coding agents can query Anyshift graph data over MCP. This is graph evidence for an agent already doing a task. It is not Annie, and it is not an autonomous AI SRE loop.
The package pairs an Agent Skill with authenticated, read-only Graph API tools. Compatible clients discover OAuth, collect consent for one Anyshift project, and store credentials themselves. No tokens or project IDs ship inside the package.
6 deterministic tools are available: resource resolution, dependencies, blast radius, recent changes, operational impact, and constrained graph queries.
The production MCP endpoint is live at https://graph.anyshift.io/mcp, backed by Graph API through v0.2.45 with MCP 2026-07-28 Streamable HTTP support. In the Anyshift app, the consent screen asks you to pick the single project the client may read.
For Codex CLI 0.147.0 or newer:
codex plugin marketplace add anyshift-io/anyshift-production-intelligence --ref main
codex plugin add anyshift-production-intelligence@anyshift
codex mcp add anyshift-production-intelligence --url https://graph.anyshift.io/mcpBackstage plugin: Ask Anyshift and richer service context
The Backstage integration (still on the next npm tag, currently @anyshift/backstage-plugin-anyshift@0.1.0-beta.14) landed a large customer-facing pass on top of last month's beta:
- Cloud resources as first-class catalog entities, with identity, relationships, changes, Terraform provenance, drift, potential impact, and scoped Ask
- Decision-oriented service pages: why now, affected footprint, deployment correlation, evidence coverage, blind spots, and freshness
- Ask Anyshift for all viewers: entity-scoped questions with typed evidence, uncertainty, safe errors, server-side credentials, and rate limiting
- Richer topology: configured ECS dependencies stay distinct from observed APM traffic, and cloud relationships become native catalog relations
- APM HTTP operations on service maps: methods, templated paths, source, and observation time in an HTTP inspector on dependency edges
Upgrade the Anyshift Backstage packages from the setup guide. See also the Backstage product overview.
Report deep links that switch projects
Opening a Proactive or custom report URL now resolves the owning project and switches to it automatically. Conversation deep links already did this. Report links from Slack or your inbox no longer 404 when your default project is different from the report's project.
Clearer Annie RCA language
Annie RCA answers now translate internal graph vocabulary into plain English. Edge names and internal labels stay out of the customer-facing text on RCA cards and chat replies, so investigations that pull dense topology context remain readable.
FAQ
What shipped at Anyshift the week of August 3, 2026?
Five customer-facing updates. Cloudflare is generally available. Our first Agent Plugins package lets coding agents query the Anyshift graph over MCP. The Backstage plugin adds Ask Anyshift for all viewers, first-class cloud entities, and richer service pages. Report deep links auto-switch projects. Annie RCA answers use clearer language.
How do I connect Cloudflare to Anyshift?
Open Integrations then Cloudflare in the Anyshift app and click Connect with Cloudflare. Sign in, pick the account, and approve the read-only scopes. An Account API token remains available as a fallback. Annie inventories DNS, zones, certificates, WAF, load balancers, Workers, tunnels, and Access onto the resource graph.
What is the new Agent Plugins package?
It is our first Agent Plugins 1.0 package for querying Anyshift graph data from compatible coding agents. It is not Annie or an AI SRE agent. 6 read-only Graph MCP tools cover resource resolution, dependencies, blast radius, recent changes, operational impact, and constrained graph queries. OAuth scopes access to one user-selected project. The endpoint is https://graph.anyshift.io/mcp.
What is new in the Backstage plugin this week?
Upgrade the Anyshift Backstage packages on the next npm tag. Cloud resources become first-class catalog entities. Service pages surface why-now context, footprint, deployments, coverage, and freshness. Ask Anyshift is available to all viewers with entity-scoped questions. Topology separates configured ECS dependencies from observed APM traffic, and service maps expose APM HTTP operations.
What changed for report deep links?
Opening a proactive or custom report URL now looks up the owning project and switches to it automatically, the same way conversation deep links already worked. You no longer hit a not-found when your default project is different from the report's project.
Ready to try it? Open app.anyshift.io or start from the docs.
