OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Infrastructure

Agent Package Manager

Agent Package Manager (APM) is an open-source Python command-line dependency manager for AI agent configuration. It uses an apm.yml manifest to declare items such as instructions, skills, prompts, plugins, hooks and MCP servers, then resolves packages for supported coding-agent environments.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Agent Package Manager — OpenViST project profile in Agent Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use APM when agent context needs to be managed as project dependencies, shared across developers or governed by installation policy. It is also relevant when packaging agent plugins or configuring MCP servers as part of a repository's setup.

Who it is for

  • Developers who want agent configuration declared and versioned with a project repository.
  • Teams seeking a repeatable setup across supported coding-agent tools.
  • Maintainers who want to author, bundle or distribute agent configuration packages and plugins.

Documented uses

  • Declare agent configuration dependencies in apm.yml and resolve them, including transitive dependencies.
  • Install shared configuration from supported Git hosts and reproduce a project setup using a lockfile.
  • Compile configuration for GitHub Copilot into .github/copilot-instructions.md.
  • Create plugins with dependency management and export plugin.json packages.
  • Set installation policies and inspect configuration through audit, drift-detection and SBOM features.
Before you choose

Requirements & limits

APM is presented as an open-source CLI project with an MIT license. Its documented implementation is in Python.

  • Configuration is declared in apm.yml, with apm.lock.yaml recording resolved dependencies and content hashes.
  • Documented targets include GitHub Copilot, Claude Code, Grok Build, Cursor, OpenCode, Codex, Gemini, Windsurf and Kiro.
  • The project documents installation checks, MCP consent gates, auditing, policy enforcement and drift detection.
  • The policy controls what gets installed; the agent harness controls what runs.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install agent dependencies from an APM manifest

Reproduce the agent configuration declared in a repository’s apm.yml.

Before you start

  • A repository containing an apm.yml manifest.
  • The APM CLI available to run the documented apm install command.

Steps

  1. Clone the repository and change into its directory: git clone && cd .

  2. Run apm install to install the declared agent dependencies.

Expected outcome

APM installs the dependencies declared in the manifest, including resolved transitive dependencies, to configure detected agent clients.

Guide limitations

  • The example uses a placeholder repository path; no particular repository or dependency set is specified.
  • No agent execution or deployment procedure is documented.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
10 October 2026
Original website title
microsoft/apm · Official homepage title · retained in its source language
How we review sourcesSuggest a correction