AgentPM™

Example Project#

See real tools, agents, templates, and generated projects wired up end-to-end.

Goal#

Point you to a working repo with runnable examples across the current AgentPM surfaces. It is useful for learning manifests, publishing, agentpm new, workspaces, CLI execution, MCP exposure, and the SDKs together.

Repository#

Demo-quality code

These examples are for education and demos, not production hardening. Expect simple error handling and minimal security hardening.

What’s inside#

  • Tools — Each has a agent.json (kind:"tool"), an entrypoint, files[], and IO schemas.
  • Agent packages — Published reusable kind:"agent" package sources under agent-packages/*.
  • Workflow templates — Published kind:"template" package sources under template-packages/*.
  • Generated example apps — Checked-in projects created from published templates, showing the actual output of agentpm new.
  • Direct package app examples — Older and current apps that install published agent packages or tools directly rather than starting from a workflow template.
  • SDK usage — Node and Python examples that load() tools or published agent roots.

The examples repo now teaches two complementary flows:

  1. Start from a workflow template Use agentpm new to generate a project, then work inside the generated app.
  2. Install published packages directly Use agentpm install in a hand-maintained app when you want to learn the lower-level package flow.

The clearest current examples are:

Older agent-app-node and agent-app-python directories are still useful for historical context, but they are no longer the main starting point.

Harness Template Family#

Use the focused Harness templates when you want a runnable starter rather than a full reference matrix.

agentpm new @zack/harness-minimal-agent my-harness-agent
agentpm new @zack/harness-sdk-host-node my-node-host
agentpm new @zack/harness-sdk-host-python my-python-host
agentpm new @zack/harness-embedding-provider my-embedding-host
agentpm new @zack/harness-provider-lab my-provider-lab
agentpm new @zack/harness-mcp-bridge my-mcp-bridge

The family is intentionally split by entry point:

  • Start with harness-minimal-agent for ordinary TUI/headless Harness usage.
  • Use the SDK host templates when your app should drive agentpm harness --machine.
  • Use harness-embedding-provider when you need a small copyable EmbeddingProvider shape.
  • Use harness-provider-lab when you are building external runtime providers.
  • Use harness-mcp-bridge when you need MCP import/export behavior.

AgentPM does not ship a single "full reference" Harness template. Focused templates are easier to run, easier to copy, and less likely to mix unrelated runtime surfaces into a confusing starter. Broad compatibility and non-ended terminal-path verification live in Harness docs and manual verification rather than in a beginner scaffold.

How to read the repo#

If you want to learn:

  • How to author and publish a workflow template
    • start in template-packages/*
  • What a real generated project looks like after agentpm new
    • start in the matching generated app directory such as agent-app-research-node or app-mcp-tool-server
  • How published tools and agent packages are authored
    • start in tools-node/*, tools-python/*, or agent-packages/*
  • How a hand-maintained app can consume published packages directly
    • start in agent-app-devwork-python

Contributing#

Issues and PRs welcome, especially corrections, new tool examples, template examples, and small agent demos that illustrate good manifest patterns.

←ExamplesInteroperability Flow