A one-command setup wizard for OpenLoomi, a desktop application with a local web interface.

Use it to install OpenLoomi, start it, wait for its local API, create guest access, and report whether the system is ready.

It removes the need to install, launch, sign in to, and check the application separately. It stops only when a person must provide authentication or configuration.

setup — Command for Claude Code by melandlabs/openloomi

About the project

OpenLoomi is an open-source desktop AI coworker that connects work tools, gathers context, and highlights decisions or actions needing attention. It is for people managing work across multiple apps, and its catalogue add-ons extend the resident desktop for agent frameworks such as Claude Code, Codex, OpenCode, Hermes, and OpenClaw.

melandlabs/openloomi · 1,037 stars · on GitHub · openloomi.ai

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add melandlabs/openloomi

Claude Code

/plugin install openloomi

Made for: Claude Code.

Or install openloomi, the plugin that ships this one along with the rest of its 11 skills, 10 commands, 8 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/melandlabs/openloomi/setup/github.svg)](https://agentmods.dev/commands/melandlabs/openloomi/setup)

Your own site

<a href="https://agentmods.dev/commands/melandlabs/openloomi/setup"><img src="https://agentmods.dev/badge/commands/melandlabs/openloomi/setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/melandlabs/openloomi/setup"><img src="https://agentmods.dev/badge/commands/melandlabs/openloomi/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,412 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00023	$0.03412
Opus 5.5	$0.00009	$0.01365
Sonnet 5.5	$0.00005	$0.00682
Haiku 4.5	$0.00002	$0.00341

Measured 1mo ago against content hash 7928e1ee9fb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/claude/commands/setup.md · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/openloomi:setup

The bridge is now an end-to-end wizard. A single setup invocation walks the full state machine:

install OpenLoomi.app
  → launch the desktop app (`open -a <desktopMarker>`)
  → wait for the local HTTP API to come up
  → mint a guest bearer (one-tap sign-in)
  → { ready: true }

Each transition is automatic. Do not ask the user to click anything in the GUI. The bridge only surfaces a stop condition when the next step truly requires human action (e.g. no selected execution runtime is ready and no direct AI provider is configured — if Claude is selected, point the user at claude auth login; otherwise use OpenLoomi Desktop → API Settings).

Steps

If the install needs explicit consent (the bridge returns setup: install_attempted is the only case where this matters — normally --yes is passed straight through), confirm with the user before re-running.
Run: node ${CLAUDE_PLUGIN_ROOT}/scripts/loomi-bridge.mjs setup --yes [--max-wait <ms>]
Read the JSON. The bridge writes an audit trail of what it did into steps[]. Surface that to the user so they can see which transitions fired.
If setup: ready → done.
If setup: awaiting_user_action → the chain hit a step that genuinely needs the user (e.g. nextAction: login_openloomi but canGuestLogin: false because the local runtime didn't come up, or nextAction: configure_ai_provider because the runtime reports no ready selected execution provider and no per-user provider row). Explain what the user needs to do and stop.

Flags

Flag	Default	Meaning
`--yes`	off	Pre-approve install (otherwise the bridge prompts y/N — but in Claude Code's Bash tool there is no TTY, so without `--yes` the install would silently cancel).
`--max-wait`	120000	Global cap across all wait stages (in milliseconds). Defaults to 120s to absorb the first-run install + TCC prompts.
`--api-timeout`	120000	Per-stage budget for "waiting for local API". Independent of `--max-wait`.
`--install-timeout`	300000	Per-stage budget for "installing OpenLoomi". Covers download + copy on a 50 Mbps link.
`--launch-timeout`	10000	Per-stage budget for `open -a <bundle>`. Almost never actually hit; included for symmetry.
`--permission-timeout`	60000	Extra wait after `--api-timeout` if the desktop process is up but the API never woke up — typical macOS TCC/Accessibility prompt path.
`--bin-path`	auto	Override the discovered helper binary path (advanced).

Read the full file on GitHub · 218 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 218 lines · 23 tokens per session scan A 7928e1ee9fb6

Subscribe to this mod's changes

setup is a command published in the GitHub repository melandlabs/openloomi (1,037 stars, last pushed 24d ago), licensed Apache-2.0. It adds 23 tokens to every session and 3,412 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

LLM agent ai claw harness-engineering llm-model

setup

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/openloomi:setup

Steps

Flags

What this file has done since we first saw it

Other commands, from other repositories

awesome-chatgpt

AGENTS

rem_help

agentlas-local

commit

speckit.archive