Define it once.
Run it everywhere.
Built by anyone. Used by everyone. Shipped to every AI runtime your team works in.
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.
A plain-language wizard in the web app for non-technical authors. The apm CLI for engineers. Same output either way: one bundle, every runtime.
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.
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.
Three steps from definition to running everywhere.
Define
Author your agent once: persona, skills, MCPs, guardrails. One canonical source of truth your whole team can review and edit — from the dashboard or your editor.
Distribute
Publish, and the platform produces APM-compatible bundles for all 7 runtimes — Claude Code, Cursor, Copilot, OpenCode, Gemini, Codex, Windsurf. Same agent, every target, re-built on every change.
Use
Anyone in the org installs the agent in their preferred runtime. Engineers run it in Claude Code or Cursor; non-technical teammates click through to a target-shaped zip and drop it in. Same agent everywhere.
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.
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.
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.
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.
Every change is a version.
Every publish is a semver release. Browse the full version history with diffs, roll back to any prior version, deprecate a version to warn consumers on install, or recall it outright to block installs entirely. Lifecycle management for AI agents the way you'd manage a real software dependency.
Reviews before things ship.
Owner, admin, and member roles on every plan. On Business, add department-level admins and configure N-required reviewers — publishes hold until your reviewers sign off. The reviewer sees a structured diff of every change before approving.
Who shipped what, when, and why.
Every publish, install, edit, and rollback is recorded with the actor, timestamp, and before/after diff. Filter by member, department, or agent. Export to CSV for your auditor in one click.
Org-level safety, applied automatically.
Define refusal patterns, tool restrictions, and content rules once at the org level. Every agent inherits them on publish — no per-agent configuration drift, no missed copy-paste between teams.
Set rules once. Override only where it matters.
Define company context, skills, MCPs, and guardrails at the org level — every agent inherits them by default. Each agent can override what it needs (a sales agent gets the CRM MCP, an engineering agent gets GitHub) without touching org defaults. New agents inherit the latest org globals; existing agents pick up changes on next publish.
What teams actually build with it.
A handful of patterns we’ve watched recur. Each one is an end-to-end story: who authored it, who reviewed it, where it ran, and how it evolved.
An on-brand writing assistant the marketing lead authors once. Engineering, sales, and support all run outbound through the same lens.
A research agent that turns transcripts and surveys into themed summaries with quote evidence. Authored by research, used by product, marketing, sales, exec.
An onboarding agent the HR partner authors once. Every new hire across every department uses it for the basics, day one.
A coaching agent the head of sales authors once. AEs use it before calls; sales managers use it during 1:1s; enablement uses it to refresh the playbook.
Engineering and product writing.
Why we’re building AgentBundle, what we shipped, and what we learned along the way.
Why we built AgentBundle to define an agent in one place and ship it to every IDE — Claude, Cursor, Copilot, OpenCode.
Secret scanning and prompt-injection detection run on every agent publish, on every plan. Here is why that is the default.
Free for small teams. Scales as you grow.
Free
Try with your team
Build and publish your first agents to the APM marketplace. Every agent ships to all 7 supported runtimes — Claude Code, Cursor, GitHub Copilot, OpenCode, Gemini, Codex, Windsurf — with built-in secret and prompt-injection scans on every publish.
Team
For growing teams
Scale beyond solo work. Up to 10 teammates and 20 agents, with departments and shared agent edit access — your whole team can build and ship agents together.
Business
For governance-driven orgs
Unlimited capacity plus the full compliance suite — approval workflow with N-required reviews, complete activity audit log, custom org policy enforcement, and department-level admin controls.
Ready to standardize your team’s AI?
Start free. Add your team. Ship the same agent to every tool they use.
No credit card required.