aas-setup
v1.4.0
Published
Initialize Pi, OpenCode, and omp agent environments from a curated snapshot
Maintainers
Readme
aas-setup
Initialize Pi, OpenCode, omp, and Ante agent environments from a curated snapshot.
npx aas-setupWhat it does
- Selects agents — interactive multi-select (TTY), positional args, or all (CI).
- Installs binaries —
pivia npm,opencode/omp/antevia curl. Skips if on PATH. - Deploys configs — overwrites agent homes from bundled
configs/. - Deploys reference docs — copies into
<agent-home>/aas-setup/.
Flags
| Flag | Description |
| --- | --- |
| [agents...] | pi / opencode / omp / ante. 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, omp (oh-my-pi), and Ante (https://ante.run). MCP server binaries are not installed — only declaration/config files (mcp.json, opencode.json, omp's config.yml + AGENTS.md, ante's settings.json + 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. Ante stores its main config as JSON at ~/.ante/settings.json (flat home, no agent/ subdir); edit the file directly or use the /config dialog in the TUI 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 testsReleasing
Create a GitHub Release to trigger npm publish:
npm version <major|minor|patch>
git push
gh release create v1.2.0 --generate-notesThe workflow runs tests (continue-on-error: true) then npm publish. Requires NPM_TOKEN secret.
License
MIT
