HELM

Why it exists

Without orchestration, “AI on the phone” becomes a pile of disconnected tricks: one app for mail, another for chat, another for research, each with its own accounts and moods. HELM keeps a single operator’s seat while the machinery underneath changes.

It also enforces the family posture: routes prefer your servers, your keys, and your siblings — not a silent detour through our rental cloud.

Who can ring HELM’s bell? Your “main” model inside AiMANAC — and, when you wire it responsibly, a cloud assistant that already supports tool calls (many do this through a shared plug-in pattern called MCP, which is basically standardized plugs so one AI can reach your stack without you pasting passwords into a random website).

Metaphors that stick

• Harbor pilot: knows the channels and brings the ship in without you memorizing every buoy.
• Studio engineer: you describe the take; HELM sets gain staging and calls the session players.
• Three sizes of the same idea: a Swiss Army knife (many tools, one pocketable handle), a cruiser hangar (one ship, many craft for different errands), or a piloted work-suit (you stay in the cockpit; the suit does the lifting). You steer; HELM routes.

Meet the siblings HELM can call →

Support-site manuals — Patchh pages for each app’s install story and wire contracts (relay envelopes, bundle IDs).