openloomilisted

# OpenLoomi Use this skill when the user wants Codex to work with OpenLoomi as a local personal assistant, memory layer, or setup guide. This skill is intentionally thin. It calls the local bridge and lets OpenLoomi own runtime execution, memory, connectors, settings, and secret storage. Before taking action, check plugin readiness: ```bash node "$SKILL_DIR/../../scripts/loomi-bridge.mjs" setup-status ``` If the bridge returns `ready: false`, follow the reported `nextAction`. Do not ask the user to paste API keys, OAuth tokens, connector secrets, or OpenLoomi auth tokens into Codex chat. When `setup-status` returns `loopbackAccessAmbiguous: true`, do not conclude that OpenLoomi is stopped. Codex network sandboxing can block access to the host's `localhost` even while the desktop API is listening. Prefer the bridge's own auto-recovery path over manual `lsof` / `curl` paste: invoke ```bash node $SKILL_DIR/../../scripts/loomi-bridge.mjs run-host-probe ``` from a Codex shell where loopback is allowed. The command probes `/api/native/providers` outside the sandbox, writes the result to `~/.openloomi/codex-host-probe-cache.json` (5 minute TTL), and the very next `setup-status` call rebuilds its readiness decision from that cache (`ready: true`, `reason: "READY_VIA_HOST_PROBE_CACHE"`). When `setup-status` returns `nextAction: "run_host_probe"`, run this command yourself instead of asking the user to paste anything. Fall back to the manual `loopbackAccess.verification.command