@loomboard/app

Run the loomboard chat app locally — no build step, no CORS setup. Works on Linux, macOS, and Windows (anywhere Node ≥ 18 runs).

npm install -g @loomboard/app
loomboard

This starts a local server, opens your browser, and shows the loomboard chat UI. In the connection screen enter your loomcycle Base URL and bearer token, pick an agent, and chat.

Prefer not to install globally? Use it one-shot:

npx @loomboard/app

Why a local server?

loomboard is a browser SPA that talks to a loomcycle runtime over /v1/*. loomcycle sends no CORS headers, so a browser can't call a remote runtime cross-origin. This CLI serves the app and reverse-proxies /v1/* to the loomcycle you name in the connection screen — so any reachable runtime (local, LAN/TrueNAS, remote) works with no extra setup.

Your bearer token stays in the browser (localStorage) and is only forwarded upstream on your requests — this process never reads, stores, or logs it.

Options

loomboard [--port <n>] [--host <addr>] [--loomcycle <url>] [--insecure] [--no-open]

  --port <n>         Port to listen on (default 4173, or $PORT)
  --host <addr>      Interface to bind (default 127.0.0.1)
  --loomcycle <url>  Default loomcycle target when the Base URL is left blank
                     (default $LOOMBOARD_PROXY_TARGET or http://127.0.0.1:8787)
  --insecure         Don't verify the loomcycle's TLS cert (self-signed LAN only)
  --no-open          Don't open the browser automatically

Security

The server binds to loopback (127.0.0.1) by default and validates the Host header, so the /v1 proxy is reachable only from your machine — it is not an open proxy, and DNS-rebinding attacks are refused. TLS certificates are verified by default (--insecure opts out only for a self-signed LAN runtime). Binding a non-loopback --host deliberately exposes the proxy to your network; do that only on a network you trust.

Embedding instead?

If you want the chat inside your own React app rather than as a standalone tool, use the component: @loomboard/chat.