Verify and operate

OpenCode and Pi activate independently through their package entries, source loader files, and host-owned policy paths. Removing one installation leaves the other host unchanged. After upgrading from 0.2.0, verify migration before removing the shared legacy file.

Verify OpenCode

After installing the plugin, inspect the resolved configuration:

opencode debug config

The resolved plugin list must contain the Auto Mode Gate entry. Restart OpenCode after configuration changes.

Verify Pi

After installing the package, inspect the installed package list:

pi list

Pi 0.84.1 lists installed packages in pi list; it does not list auto-discovered extension files there. A source installation can be checked without contacting model providers:

pi --offline --list-models

Since version 0.2.0, verify session state from Pi with:

/amg-judge status

Use /amg-judge on only after global authorization names an available model. Use /amg-judge off to disable the current session, /amg-judge model <provider> <model-id> to select another available model, and /amg-judge reset to restore the global default. These commands do not edit files or change Pi’s primary model.

What is enforced

Both adapters enforce calls to their built-in bash tool. Other tools remain under native host permissions. The shared conformance suite exercises deterministic and judge outcomes. Pi can judge an eligible request in an active session; OpenCode blocks the same case as unavailable.

A child process must load its own adapter. The hooks do not guarantee that a separately launched child host loaded the gate.

What happens after an allowance

An allowance means that the Auto Mode Gate policy did not block the call. Native OpenCode or Pi permissions still apply after that decision. Passing the gate does not bypass or replace host permissions.

Verify configuration isolation

OpenCode must ignore Pi’s global and .pi project destinations. Pi must ignore OpenCode’s global and .opencode destinations. An existing host-owned file also suppresses legacy discovery for that host. Test changes with harmless policy settings and restart or reload the relevant host.

Useful checks

Run the project test suite from the repository root:

npm test

The published package documents only the validated OpenCode, Pi, and Node baselines. Version 0.3.0 retains the Pi judge introduced in 0.2.0, but no real-model inference was used for its validation. Do not infer broader compatibility or provider safety from a successful local or loopback run.