A dedicated client for OpenClaw.

BROILR is the planned standalone client for OpenClaw flows — the successor to ClawHub. This page describes what the new app is going to do when it ships. For now, AiMANAC carries an in-app fallback so you can drive OpenClaw without leaving the main console; switch to BROILR when you want a dedicated surface for it.

OpenClaw User Phone-First Control Surface

OpenClaw setup path (today) ← Back to suite

What's Planned

A Dedicated Mobile Control Surface

If you run OpenClaw on a separate host, you want a phone-side control surface that's dedicated to OpenClaw — not folded into the AiMANAC main app. BROILR is that. AiMANAC stays the general AI orchestration console; BROILR stays the OpenClaw-specific cockpit.

Hardened launcher

Connects to your OpenClaw runtime host with verified credentials. Today's "Customer OpenClaw Path" in AiMANAC base remains as a fallback when BROILR isn't installed.

Flow control

Start, pause, inspect, terminate OpenClaw flows from the phone. The runtime host keeps the actual execution; the phone is the UI.

Status surface

Live status of running flows, recent failures, queued work. Designed for glance + drill-in patterns over deep editing.

Trust mesh integration

Shares AiMANAC's secure credential slot on the phone so OpenClaw logins stay in one place, ask for re-checks when needed, and are not duplicated across apps.

What Exists Today

In AiMANAC, Not Standalone

Until the standalone BROILR ships, OpenClaw flows are driven from AiMANAC itself. The Customer OpenClaw Path walks through the same runtime layout the BROILR app will eventually sit on.

What AiMANAC does today:

It can ask iOS whether BROILR is installed before trying to hand off.
The MCP cockpit shows a clear “under construction” lane for BROILR so expectations stay honest.
All real OpenClaw work still follows the setup guide until the standalone icon appears on your Home Screen.

When BROILR is listed on the App Store, the launcher flips from placeholder to live and one tap opens the dedicated client.

Identity & Versions (Planned)

Not Yet Registered

Display nameBROILR

Bundle IDnet.llmtech.broilr

URL scheme (planned)broilr://

Pricing (planned)$1 one-time (sibling SKU pattern)

App Store URLRegistration pending

App Store listingPlaceholder until Apple assigns the public ID

Quick Setup (When It Lands)

Two Paths Today

broilr-server ships on GHCR — customer path is pull, not public git clone. Co-host with aimanac on one VM via /setup/llm/.

Path A — GHCR pull. docker pull ghcr.io/everplay-tech/broilr-server:<tag> — walkthrough at Railway / deploy hub panel 00a.
BROILR iOS FirstBoot. Paste your HTTPS broilr URL after /ready is green.
OpenClaw via AiMANAC (today). Until BROILR standalone is App Store live, use /setup/openclaw/ from AiMANAC.

Watch this page for the status LED to flip from stub (red) to pending (amber) when the standalone app archives, and to live (green) when App Store registration completes.

Talk To The Family

Discord · Support & Feedback

A single Discord covers customer support and feedback across the whole AiMANAC family — BROILR included once the standalone ships. We do not run separate forums or in-app feedback chrome.

Support

OpenClaw runtime not pairing, BROILR launcher stuck on placeholder, broilr-rs deploy not staying up? Ask in Discord; the maintainer and operators running broilr-rs are in there.

Invite link pending

Feedback

Control-deck UX, flow-control gestures, OpenClaw integrations you want surfaced — feedback goes through Discord, openly.

Invite link pending

Direct contact until the invite link lands: info@llmtech.net.

Cross-Links