Pi adapter

Status, install flow, configuration surface, and known limitations of Alfred's Pi adapter.

Status

Adapter status: executable-spike — the reference implementation; the first adapter Alfred shipped.

Source package: packages/pi-adapter.

Install flow

1. Run the installer. Alfred detects the active harness.
2. Review the preview — it lists every file Alfred will write.
3. Approve. Alfred writes the config and prints a summary.
4. Restart Pi so the panel is registered.

Configuration surface

The Pi adapter reads .alfred/config.json and:

• Generates the agent panel under .pi/agent/.
• Materializes skills under .pi/skill/ with the same triggers.
• Applies the permission policy unchanged.

Known limitations

• Configuration is loaded at startup — always restart Pi after applying generated harness config.
• Protected paths under the harness's own config directory require --force + human approval.
• Some Pi-specific features (e.g. provider-specific hotkeys) are not yet mapped to Alfred primitives.