The CLI already honors HYPERIA_MCP_URL, so cross-host control is mostly endpoint + network + auth. Goal: from my terminal, target a Hyperia on another box and send a pane a message / query a pane there — same model the n8 container uses to reach the host, pointed at a remote host instead. NOT console streaming (separate issue).
Scope:
--host <box>:9800 / --url flag as sugar over HYPERIA_MCP_URL (hyperia --host box status|run|call ...).- Remote sidecar bind: it currently listens on 127.0.0.1 only. Add an opt-in routable bind that REQUIRES a token (default stays localhost-only).
- Identity/consent for a remote caller: mint/cache
hyp_agent_ against the remote (hyperia login --host), Bearer on every call, consent prompts surface on the remote box's UI.
hyperia doctor --host for reachability/identity against a remote.
Security: remote bind must be explicit opt-in + token-gated; never expose an unauthenticated sidecar. SSH tunnel remains a valid transport (no console-streaming dependency).
The CLI already honors
HYPERIA_MCP_URL, so cross-host control is mostly endpoint + network + auth. Goal: from my terminal, target a Hyperia on another box and send a pane a message / query a pane there — same model the n8 container uses to reach the host, pointed at a remote host instead. NOT console streaming (separate issue).Scope:
--host <box>:9800/--urlflag as sugar overHYPERIA_MCP_URL(hyperia --host box status|run|call ...).hyp_agent_against the remote (hyperia login --host), Bearer on every call, consent prompts surface on the remote box's UI.hyperia doctor --hostfor reachability/identity against a remote.Security: remote bind must be explicit opt-in + token-gated; never expose an unauthenticated sidecar. SSH tunnel remains a valid transport (no console-streaming dependency).