FIRST
STEPS
/// /reload, then a prompt
If there are no providers, first run opens the assistant. You pick a preset (Grok, Kimi, Claude, Ollama, whichever you use), paste the key, see the diff for models.json and auth.json, and confirm. Say no and it writes nothing. Say yes and it backs up, then writes. There is no «next, next, finish» in the dark.
If keys and models are already there, the assistant stays away. You go to the prompt.
After installing the extension you need a /reload so pi loads it. Without that step Alfred-Pi is not in the session even if the symlink exists. Then an ordinary prompt is enough. «Audit the security of this repo». «This 502 in production». «Refactor this module without changing behaviour». «Fix the wording of this README».
The radar reads that sentence. If it matches a pack's triggers (whole word, not a subset), it lights that room. If nobody matches, it looks at the directory root: a Dockerfile, an astro.config.mjs, a sonar-project.properties. If there is still no hint, it does not invent a craft. The model works without a pack.
Skills from packs you enabled in /domains stay available to the model, even if the injected context is one room. After enabling every room you also need a /reload.
/stack shows the active model, whether autopilot is on, which packs exist and how the budget is doing. /providers:doctor (or pi --alfred-pi=doctor) checks that keys and endpoints actually answer, with latency, not a courtesy ping. /usage reads local sessions and tells you what the day cost.
Install (git, symlink, uninstall, the 0.2 to 0.3 move) lives at install. How a turn is built, at how it works. Local, Chrome, the 0.2 move: FAQ.