For every team
    Agents are shared infrastructure for your whole organization.
    AgentBundle treats AI agents like the rest of your software stack — versioned, distributable, and governable across every role. A marketing lead authors an on-brand brief-to-draft agent that engineers use for technical RFCs. A platform engineer authors a release-note agent that marketing uses for launch copy. One canonical definition, the same security scans on every publish, available in every team's preferred runtime.

      Author from any seat
      Click New Agent in the dashboard, pick a starting template (or start from scratch), fill in the form. Engineers can scaffold via the apm CLI. Same output either way: one bundle, every runtime.

      Install once, available everywhere
      Run apm install from the CLI, or download the bundle as a zip from the marketplace. Each agent ships to Claude Code, Cursor, GitHub Copilot, OpenCode, Gemini, Codex, and Windsurf — wherever a user already works.

      Governance and audit, by default
      Owner, Admin, and Member roles on every plan. Department-level admins, N-required reviewer approval workflow, and full audit-log retention land on Business — auditable end-to-end.

    How it works
    Three steps from definition to running everywhere.

    Built on APM
    An open package format for AI agents.
    AgentBundle outputs APM-compatible packages — the open packaging spec for AI agents, maintained by Microsoft. AgentBundle is the visual platform that authors and distributes these packages; APM is the standard format and the CLI for installing them. Same artifact, two install paths.

      For developers
      Run apm install owner/repo/agent in the terminal. Microsoft's apm CLI auto-detects your IDE, drops files into the right target directories, wires MCPs, and locks the version in apm.lock.yaml.

      For everyone else
      Open the agent in the AgentBundle dashboard, pick your target, and click Download. Get a zip shaped for your runtime that drops into your project. Identical to what the CLI produces — no terminal needed.

    Read the APM spec →
    APM on GitHub →

    Trust & control
    Built for teams that need a paper trail.
    Versioning, reviews, audit, and guardrails are first-class — not a tier. The whole org sees every change, every publish, every install.