aas-setup

Initialize Pi, OpenCode, and omp agent environments from a curated snapshot.

npx aas-setup

What it does

1. Selects agents — interactive multi-select (TTY), positional args, or all (CI).
2. Installs binaries — pi via npm, opencode and omp via curl. Skips if on PATH.
3. Deploys configs — overwrites agent homes from bundled configs/.
4. Deploys reference docs — copies into <agent-home>/aas-setup/.

Flags

| Flag | Description | | --- | --- | | [agents...] | pi / opencode / omp. Omit for interactive (TTY) or all (CI). | | --dry-run | Preview planned actions, touch nothing. | | --backup | Tar existing agent homes before overwrite. |

Snapshot Philosophy

This is a snapshot, not a generic installer. Configs ship exactly as the author uses them — personal proxies, extension lists, etc. No templating.

Scope

Pi, OpenCode, and omp (oh-my-pi). MCP server binaries are not installed — only declaration/config files (mcp.json, opencode.json, omp's config.yml + AGENTS.md) are deployed. omp stores its main config as YAML at ~/.omp/agent/config.yml; use omp config set <key> <value> or edit the file directly to mutate.

For skill management, see @kkmila/isc.

Development

npm install                       # required for local development
node bin/aas-setup.mjs --dry-run  # preview
node bin/aas-setup.mjs            # real run
npm test                          # process-seam tests

Releasing

Create a GitHub Release to trigger npm publish:

npm version <major|minor|patch>
git push
gh release create v1.2.0 --generate-notes

The workflow runs tests (continue-on-error: true) then npm publish. Requires NPM_TOKEN secret.

License

MIT