KDCube

Agents Get a Phone Book: DNS Identity, IBM–Microsoft's Agent Factory, Antigra...

The Linux Foundation adopted the Agent Name Service, a DNS-anchored standard that gives every agent a verifiable, certificate-backed name, while IBM and Microsoft launched Imagine Enterprise with 6,000+ prebuilt, governed agents. Meanwhile Google Antigravity turned its IDE into a multi...

Highlights

  • The Linux Foundation adopted the Agent Name Service (ANS) at KubeCon NA — an open, DNS-anchored standard giving every agent a verifiable, versioned name (ans://v1.0.0.my-agent.example.com) backed by the same certificate checks a website uses, with Cisco, Cloudflare, DigiCert, GoDaddy, Salesforce, Infoblox, and OWASP aboard. (Linux Foundation)
  • IBM and Microsoft launched Imagine Enterprise, a build-run-govern agent platform seeded with 6,000+ prebuilt IBM Consulting agents and governed through Copilot Studio, Fabric, Entra, and Purview. (IBM)
  • Google Antigravity turned its agent-first IDE into a multi-agent runtime: /swarm coordinates subagents over a message board (v2.31.0), and Dynamic Workflows now run parallel subagents in bundled Python (v2.32.0). (Antigravity)
  • Data-quality firm digna shipped MCP connectors wiring Claude, ChatGPT, Gemini, and open models to on-prem and private-cloud deployments — keeping the data plane inside the customer's perimeter. (AI Agent Store)

Key Signals

  1. Agent identity moves from per-vendor ledgers to open DNS. Nov 10, KubeCon NA
    ANS defines how agents are named, registered, published through DNS, and verified — a name only earns an identity certificate after its domain clears the same DNS/ACME checks as a TLS cert, with transparency logs and integrity monitoring on top. (Linux Foundation) Two days after this issue's predecessor covered Block's signed per-agent ledgers, the industry now has a cross-vendor identity rail instead of eleven proprietary ones.
  2. The "agent factory" pitch gets a big-vendor flagship. Nov 10
    Imagine Enterprise bets that enterprises want to adapt thousands of prebuilt, industry-specific agents rather than assemble frameworks from scratch — financial services, insurance, and retail first, governed via Entra identity and Purview policy on Azure. (IBM) It's a direct challenge to the DIY LangGraph/CrewAI stack for regulated buyers.
  3. IDEs are quietly becoming multi-agent orchestrators. Nov 9–13
    Antigravity's /swarm and Dynamic Workflows push coordination of parallel subagents into the editor itself, backed by Gemini 4 Carbon for long-horizon work and the new Orchestrator for multi-model planning. (Antigravity) The dev surface and the agent runtime are collapsing into one tool.

Why It Matters / What To Watch

  1. DNS-based identity is powerful — and a fresh attack surface.
    • Evaluate ANS against your existing agent-auth story before it becomes the default A2A trust layer; the AGNTCY Agent Directory already verifies ANS identities. (Linux Foundation)
    • Read the Cloud Security Alliance's security analysis first — anchoring agent trust in DNS inherits DNS's spoofing, cache-poisoning, and registrar-takeover failure modes. (CSA)
  2. "Prebuilt agent fleets" shift the build-vs-buy line.
    • If you're standardizing on an enterprise agent platform, pressure-test whether Imagine Enterprise's 6,000 assets are genuinely adaptable or shelfware, and where governance (Purview/Entra) actually enforces vs. observes. (IBM)
  3. Orchestration is leaving the framework and entering the tool.
    • Watch whether message-board subagent coordination like Antigravity's /swarm needs the identity and audit guarantees ANS and enterprise platforms are now standardizing — multi-agent sprawl without verifiable names is the governance gap to close. (Antigravity)

Quick Links