@agimon-ai/po
Opinionated, composable agent harness for scoped tools, skills, MCP servers, and developer workflows.
Package details
Install @agimon-ai/po from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@agimon-ai/po- Package
@agimon-ai/po- Version
0.0.0-alpha.171- Published
- Nov 19, 2026
- Downloads
- 32.5K/mo · 7,211/wk
- Author
- agiflow-ai
- License
- BUSL-1.1
- Types
- package
- Size
- 4.7 MB
- Dependencies
- 45 dependencies · 0 peers
Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
Po
Po is a configurable agent runtime built on Pi. This package owns the po launcher and the client-neutral po-server. Selected packages supply tools, guidance, workflows, and interfaces; they are not all loaded into every session.
Po is alpha software. Configuration and package boundaries may change between releases. Node.js 24 or newer is required.
Install and start
npm install -g @agimon-ai/po @agimon-ai/po-web
po init
po sync
po
po init seeds personal configuration under ~/.po, preserving existing files unless --force is used. po sync installs configured packages and prepares shared browser/native and MCP artifacts. Bare po starts Po Web, which supervises a headless child; it prints installation guidance if the presentation package is missing.
For direct server clients, use po-server with a private token file. The executable is part of this package, not an extension to add to presets.yaml.
Choose what a session loads
Personal defaults live under ~/.po; repository overrides live under <repository>/.po:
config.yaml: runtime and package settings.presets.yaml: default packages, named layers, and presets.domains.yaml: plugin catalogs and subject-specific skills, agents, hooks, and MCP access.profiles.yaml: optional persona files and environment defaults.
A preset selects the base package layers. Domains select content and integrations. A profile supplies a point of view. Modes expose temporary capabilities where their owning packages provide them. These choices are replaceable; they are not security isolation.
Repository entries replace same-named personal definitions. Relative paths resolve from the declaring root. Keep package-specific settings under their owning package, and pin remote Git/npm plugin sources when reproducibility matters.
Inspect a selection before starting a model:
po --preset copilot --no-domains --explain
po sync --check
--explain can inspect MCP servers and execute their configured startup commands. Add --no-mcp when that inspection is unwanted. sync --check is read-only and reports missing packages or shared builds; it does not prove runtime behavior or API compatibility.
See Getting started and Architecture for configuration and extension ownership. Activate Help in a session for installed package guidance.
Builds, updates, and recovery
Synchronization owns package installation and shared build production. The server can request background synchronization, but scope admission itself reads prepared packages and artifacts. With automatic sync disabled or unsuccessful, inspect notices and run po sync rather than assuming a missing feature loaded.
Built server entries are imported through content-addressed URLs. New sessions can use a new build; running sessions retain their loaded code unless an explicit supported reload replaces it. Host/workspace refresh and session selection changes have separate lifetimes. Browser reconnect is not a server reload.
Headless history uses pi-durable SQLite storage. Earlier pre-durable headless sessions cannot be resumed or converted by this runtime; their files are left untouched. Back up important state before an upgrade. Deleting a session is not a promise to delete files it wrote into a workspace.
Runner chooses matching native artifacts; do not install RMUX or RTK payload packages directly. Non-interactive commands can use a supervised subprocess when no pane backend works; interactive commands require a supported pane backend. Inspect runner status and complete logs before retrying a command that may already have changed state.
Trust and costs
Configured packages, hooks, MCP commands, plugins, and shell commands are executable inputs. They run with the session's admitted environment and execution privileges. Plan mode removes selected editing tools; it does not sandbox Bash or external systems. Workspace containment is an optional, explicitly selected capability, not an effect of remote pairing.
Transcript/model requests follow the configured providers. Voice can use local engines, but that does not make all session data local. Planning, delegation, workflows, compaction, and other enabled capabilities may make additional model calls. Commands and telemetry can contain sensitive caller-supplied values.
Calendar occurrences missed during downtime or busy execution are skipped, not replayed. A workflow launch acknowledgement is not workflow completion. Browser notifications are not durable approval delivery. Read Security before granting remote or unattended access.
Contributor entry points
- Server guides: authenticated clients, protocol, package APIs, and lifecycle.
- API export: compiled OpenAPI/AsyncAPI contracts and strict coverage checks.
- Contributing: repository development and verification.
- Agent Experience: why we design the agent environment and human collaboration together.
Shared contract packages (po-core and po-hashline) must be available before consumers such as Help and the distribution runtime. Release tooling owns changelogs and publication order; architecture checks and packed-install system tests gate release changes.
License
Business Source License 1.1: free for personal use, organisations under USD 1M revenue, non-profits and education. See LICENSE and https://agimon.ai/licensing.