openloomi-setup

Automates end-to-end OpenLoomi desktop installation, Codex provider configuration, and API readiness via a bridge wizard.

1.0k|46|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/melandlabs/openloomi --skill openloomi-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openloomi-setup
Source: https://github.com/melandlabs/openloomi/tree/main/plugins/codex/skills/openloomi-setup
Command: npx skills add https://github.com/melandlabs/openloomi --skill openloomi-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up the OpenLoomi desktop app involves many manual steps — installing the app, wiring the Codex agent provider, launching the GUI, waiting for the local API, and minting a session token. This Skill collapses that entire chain into a single idempotent wizard command with clear stop conditions when human action is genuinely required.

Core Features & Use Cases

  • One-call setup wizard: Runs install → set Codex provider env var → launch desktop → wait for local API on localhost:3414 → mint guest bearer token, all through loomi-bridge.mjs setup --yes.
  • Actionable stop conditions: Returns structured JSON (ready, awaiting_user_action, api_not_ready, install_failed, etc.) with hints, resume commands, and an audit trail of every transition.
  • Post-setup orientation: Prints a guided tour covering health checks, pet widget states, connector linking, Loop ticks, and memory seeding.
  • Use Case: A developer on a fresh machine asks their Codex agent to "set up OpenLoomi" — the wizard installs the app, configures OPENLOOMI_AGENT_PROVIDER=codex, waits for the API, and reports ready in one invocation.

Quick Start

Ask your Codex agent to run the OpenLoomi setup wizard with pre-approved install so it installs the desktop app, configures the Codex provider, and confirms the local API is ready.

Frequently Asked Questions about openloomi-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install and set up OpenLoomi with Codex?

Run the bridge wizard with `node loomi-bridge.mjs setup --yes`. It installs the desktop app, writes the Codex provider environment variable, launches the app, waits for the local API, and mints a guest token in one call.

How do I configure OpenLoomi to use Codex as the AI provider?

The setup wizard writes `OPENLOOMI_AGENT_PROVIDER=codex` automatically before launch — via launchctl and a LaunchAgent on macOS, or `~/.config/environment.d/` on Linux. You can verify the active value with the `codex-runtime-info` bridge command.

Why does OpenLoomi setup fail inside the Codex sandbox?

The wizard needs to write to `/Applications` or `~/.config/environment.d/`, launch a GUI app, and reach localhost:3414, none of which work under read-only or default workspace-write sandbox modes. Request approval and re-run with danger-full-access or outside the sandbox.

What should I do when OpenLoomi setup returns api_not_ready?

The desktop launched but the local API did not respond within the timeout. Print the payload's hints, then re-run the wizard — it is idempotent and resumes at the wait stage. Use the provided resumeCommand to raise the wait budget.

Can I re-run the OpenLoomi setup wizard safely?

Yes, the state machine is idempotent. Already-completed steps like install and environment writes are skipped, and the wizard resumes from wherever the previous run stopped.