Agentic Config

agentic-config

Project-agnostic, composable AI workflow automation via pi packages and Claude Code plugins.

Quick Start

Pi

Primary install from the current public release tag:

The -l flag installs it into the local project config. For a global/user install, remove -l.

For teams and automation, prefer the tagged git ref in committed .pi/settings.json so the rollout stays reproducible.

For local testing or development, use a branch ref instead of a tag, for example:

If you prefer SSH transport, use the equivalent SSH git source for the same repository and ref.

The current git root install exposes the full shipped pi surface. Individual package-root installs remain useful for local package development and validation. npm publication remains future work.

Claude Code
Note: Auto-updates are disabled by default for third-party marketplaces.
Enable them via /plugins > Marketplaces > agentic-plugins > Enable auto-update
to stay in sync with new releases automatically.

See Getting Started for pi and Claude Code setup.

Pi Packages

Pi is supported today through a validated root umbrella package installable from git refs, with local package-root installs for development and validation. Publishing the per-package npm surface remains future work.

For teams, prefer a committed .pi/settings.json pinned to a release tag. For local testing and development, use branch refs or direct local package paths as appropriate.

Upstream Pi attribution

agentic-config ships third-party packages for Pi. Pi itself, including the CLI, package loader, extension API, and runtime, is maintained upstream at pi.dev and earendil-works/pi. The package surface here imports upstream Pi APIs such as @earendil-works/pi-coding-agent and @earendil-works/pi-ai where needed.

See Upstream Pi…