Preview PigeonStack before installation

Before you start

Check the current host requirements

• The currently validated host is Windows with PowerShell.
• The synchronization script requires Python 3.11 or newer.
• Installing the plugin requires a compatible Codex CLI and an existing local marketplace registration that resolves pstack@personal.
• Multi-agent work requires native child-agent tools and account access to the selected models.

Step 1

Clone the source

Run these commands in PowerShell from the directory where you keep source repositories.

git clone https://github.com/PigeonAI-Yang/pigeonstack.git
Set-Location pigeonstack

Step 2

Preview in a new sibling directory

These commands copy the managed files and merge the selected configuration in ../pigeonstack-preview-codex. The initial check normally exits with code 1 because that directory is empty. The final check exits with code 0 when the files and configuration align.

python scripts/sync.py check --codex-home ../pigeonstack-preview-codex --skip-plugin-install
python scripts/sync.py deploy --codex-home ../pigeonstack-preview-codex --skip-plugin-install
python scripts/sync.py check --codex-home ../pigeonstack-preview-codex --skip-plugin-install

For a nondefault target, keep --skip-plugin-install. The script rejects source and target paths that overlap.

Before a real install elsewhere

Review the paths and settings

The default sync target points to J:/Users/yangda01/.codex. The repository also contains owner-specific paths in the global rules, the Codex host guide, and the poteto-agent.toml role file.

The script does not register a plugin marketplace. Adapt the source and confirm that the local marketplace can resolve pstack@personal before a real installation on another host.

Observed run

Verified isolated preview

Reviewed 2026-10-03 against release commit 41f7dce. The actual empty-target check returned code 1 for drift. Deployment returned code 0 after 217 writes to managed files and configuration. The final check returned code 0 with the files and configuration aligned.

Run python -m unittest discover -s scripts -p test_sync.py to repeat the four configuration regression tests in scripts/test_sync.py. They verify root and table scope, preservation of unmanaged values, repeat-call idempotence, and the multiline-value guard.

The Documentation health workflow runs ongoing site checks. These checks do not establish plugin activation, model routing, or cost savings.

An example task

Give the Primary a concrete outcome

For example, ask Codex:

Fix the export error when a report has no rows. Preserve the current file format and verify the normal export path too.

This is an illustration, not a recorded run. The Primary checks the evidence, selects a repair, and gives Luna a bounded implementation and verification brief. If Luna cannot solve it, a fresh Sol Senior Executor takes over at medium. The same unresolved problem advances through Sol high and xhigh before Astra high, then Astra xhigh if needed. Send master or system architecture, key interface and data-contract design, and consequential tradeoffs to Astra directly. Explicit task-specific model and effort selections take precedence.