Skip to main content
Portable agents are runtime-neutral versions of the Agent Kit workflows. Use them when your organization already runs its own agent runtime, repository workflow, ticketing system, approval system, credential controls, and audit pipeline. You get the Endor Labs workflow without a host-specific plugin. A common example is a team that opens pull requests through its own automation and runs agents in a platform such as Atlassian Rovo. Portable bundles live in the endorlabs/endor-labs-agent-kit repository under portable/<agent>/.

​
What is in a bundle

Each portable bundle includes:
  • agent.md: the runtime-neutral agent instructions.
  • agent.manifest.json: machine-readable transports, capabilities, actions, wrappers, and degradation behavior.
  • output-contract.md: inputs, outputs, adapter contracts, and mechanical workflow gates.
  • Optional actions.yaml adapter contracts, plus endorctl-setup.md and architecture.svg support files.

​
Split-responsibility model

The integration model is deliberately split between the Agent Kit and your runtime:
  • The Agent Kit defines the workflow, evidence requirements, safety contract, and structured output.
  • Your runtime enforces authentication, authorization, logging, audit, adapter execution, and approval policy.
  • Runtime adapters perform the semantic actions the agent requests.
The agent must not claim an action completed unless your adapter returns evidence. Evidence can be a PR or MR URL, ticket ID, policy UUID, branch, validation result, or an explicit data gap.

​
Adapter mapping

Map each portable action to an adapter in your environment.

​
Conformance levels

Your portable integration should target one of three conformance levels:
  • contract-aware: loads the manifest, exposes declared adapters, and returns evidence or data gaps.
  • mutation-safe: adds authorization, explicit confirmation, audit logging, and fail-closed behavior for mutating actions.
  • enterprise-ready: adds adversarial evaluations, data-loss-prevention and secret redaction, and incident review.
For the full set of required runtime controls and the adapter response schema, refer to portable-runtime-conformance.md in the Agent Kit repository. See the safety model for the shared safety contract that every portable bundle preserves.