Works with

      The founder doing sales
      Six months of cold-email tuning lives in her personal ChatGPT. She hires a salesperson. The new rep starts from a blank prompt.

      The DevOps engineer's Jira triage
      He built a workflow that classifies tickets, branches off main, and writes RCAs on bugs. He shows it in standup. No teammate can run it on their machine.

      The marketing lead's brand voice
      Pasted the brand guide into ChatGPT a year ago and tuned it until the tone landed. The voice is right. The voice is locked to her laptop.

      The CS lead's renewal playbook
      Two years of refining renewal conversations — what to ask, when to escalate, when to mention the roadmap. Her new CSM hire learns the job from a blank slate.

      The CTO who isn't coding
      He hasn't shipped code in a year. He drafts RFCs and reviews PRs through an agent that knows the codebase, the standards, the postmortem patterns. The next project owner doesn't get the agent.

      The ops lead's everything-handbook
      Half her week is answering the same questions about benefits, vendor invoicing, and approval flows. She built an agent that knows it all. Teammates still Slack her.

  Six different jobs. Same problem. Great agent, one computer.

    Layer 1 — Shared workflow
    Define the shape of the work once.
    Every team has a workflow that's the same shape regardless of who's doing it. Tickets get read, classified, acted on, logged. Leads get researched, qualified, contacted, logged. Briefs get scoped, drafted, reviewed, published. The system of record differs by team; the shape doesn't. With AgentBundle you define that shape once at the org level — every role's agent inherits it.

      Engineering
      Pull the ticket from Jira → classify story vs bug → branch off main → RCA on bugs → PR with the Jira number in the branch.

      Sales
      Pull the lead from the CRM → run discovery against the prospect-research doc → log objections → schedule the follow-up → write the recap.

      Marketing
      Pull the brief from Asana → check it against the brand voice → draft → run the GEO checklist → log the publish.

    Layer 2 — Role skills
    Each role overlays its own skills on top.
    The shared workflow is the same. The skill stack on top is different per role. AgentBundle calls the org-level skills inherited and the per-role additions overrides — but you don't need to think in those terms. You just pick the skills the role needs. Inheritance and overrides are versioned and auditable — every change leaves a trail. See /security for the governance details.

      DevOps engineer
      On top of the ticket workflow:

        terraform-plan-review
        kubernetes-debug
        on-call-playbook

      Full-stack engineer
      On top of the ticket workflow:

        react-best-practices
        nextjs-app-router-patterns
        accessibility-review

      Sales rep
      On top of the lead workflow:

        prospect-research
        objection-handling
        follow-up-cadence

      Marketing lead
      On top of the brief workflow:

        brand-voice
        geo-checklist
        subject-line-audit

    Layer 3 — Share what one person built
    The agent you've been honing is one laptop crash away from gone.
    Every effective AI user is already building agents — in personal ChatGPTs, in , in their own Cursor configs. That polish is real, and it's locked to one machine. AgentBundle moves the agent into shared infrastructure: every teammate runs the same version in their preferred runtime, every new hire inherits it on day one, and updates from the original author roll out the next time anyone syncs.

      Before
      One person, one machine.

      After
      Same agent, every teammate.

  The agent the team wanted to use yesterday — actually shareable today.

    Get started free

    Where this is going
    The agent you polished becomes the agent that runs while you sleep.
    Today the agent runs interactively — a human invokes it from their IDE or the dashboard. Soon, the same agent definition fires on a trigger: a ticket lands → the triage agent runs → the RCA writes itself → the PR opens with the right reviewers. The open runtime for this already exists — Google's Agent Development Kit (Apache 2.0) went GA in April 2026, with workflow agents, scheduled triggers, and managed REST endpoints. AgentBundle's job is to be the authoring and governance layer that exports to those runtimes. Human-in-the-loop becomes human-out-of-loop only after the agent earns it.
    We're building this. We're not selling it yet.

    Build your first agent
    Pick a template, or start from scratch.
    Click New Agent in the dashboard. Pick a starting template — Sales Agent, Customer Support, Content Writer, Code Reviewer — or start from scratch. Fill in the form: name, persona, the documents that already guide the work, the skills the role needs, the connectors. Hit publish. A few minutes from blank to ready-to-share, with no engineer in the loop.

    Create your first agent

    Use it
    Two ways for teammates to install it.
    Once your agent is published, every teammate installs it on their machine in the way that fits them. Same agent definition, either path.

      No code — download the zip
      Open the agent in the AgentBundle dashboard. Pick your target runtime — Claude Code, Cursor, Copilot, OpenCode, Gemini, Codex, or Windsurf. Click Download. Drop the zip into your project. Done.

        Get started free

      Terminal — one command
      Microsoft's open apm CLI auto-detects your runtime, drops in the agent files, and locks the version in apm.lock.yaml.

        Read the APM spec →

      Use cases
      What teams actually build with it.
      A handful of patterns we've watched recur. Each one shows who built it, what they typed into the New Agent form, and how the rest of the team uses it.

    All use cases →

    Pricing
    Free for small teams. Scales as you grow.

    See full pricing →