Show HN: Running local OpenClaw together with remote agents in an open network

Your local & remote AI agents — private, powerful, unified.

Hybro Hub is a lightweight daemon that connects your local AI agents to hybro.ai — so you can use local and cloud agents side by side in one portal, with full control over where your data goes.

pip install hybro-hub

AI agents today force a choice:

Cloud platforms(ChatGPT, Devin, Cursor Cloud) are powerful but require sending your data to third-party servers.Local runtimes(Ollama, LM Studio) keep data private but are isolated — no access to specialized cloud agents, no shared UI.

You shouldn't have to choose between privacy and power.

Hybro Hub bridges local and cloud. Open hybro.ai, see your local Ollama model next to cloud agents like a legal reviewer or code analyst. Chat with any of them. Your local agents process on your machine — your data never leaves. Cloud agents are there when you need more capability.

One portal. Your choice, per conversation.

pip install hybro-hub

Go to hybro.ai/d/discovery-api-keys → API Keys → Generate New Key. Copy the key (starts with hybro_).

hybro-hub start --api-key hybro_your_key_here

The hub starts as a background daemon and returns you to the prompt immediately. Logs are written to ~/.hybro/hub.log. The API key is saved to ~/.hybro/config.yaml — subsequent starts don't need it.

hybro-hub status # check local daemon state and cloud connection
hybro-hub stop # stop the daemon gracefully

Start a local LLM as an A2A agent (requires Ollama installed):

hybro-hub agent start ollama --model llama3.2

You'll see:

🔗 Connected to hybro.ai
📡 Found 1 local agent:
• My Ollama Chat (llama3.2) — localhost:10010
Agents synced to hybro.ai. Open hybro.ai to start chatting.

Refresh hybro.ai. Your local agent appears alongside cloud agents:

☁️ Legal Contract Reviewer (cloud)
☁️ Code Review Pro (cloud)
🏠 My Ollama Chat (llama3.2) (local · online)

Add it to a room, send a message. The response streams back with a 🏠 Local badge — your data never left your machine.

Key properties:

Outbound-only— the hub initiates all connections. No inbound ports, no firewall changes, works behind NAT.Portal-first— you always use hybro.ai. No localhost URLs, no mode switching. Local agents just appear as more agents in the same portal.A2A protocol— local and cloud agents speak the same Agent-to-Agent protocol. Any A2A-compatible agent works.Graceful degradation— if the hub is offline, cloud agents still work. Local agents show as "offline" and messages queue until the hub reconnects.

Hybro Hub doesn't just promise privacy — the architecture enforces it.

Your data stays local when you use local agents. Messages to local agents route through the relay to your hub, get processed entirely on your machine, and only the response travels back. The cloud relay sees message metadata (routing info), not your content.

Every message in hybro.ai shows where it was processed:

• 🏠 Local(green) — processed on your machine, data did not leave
• ☁️ Cloud(blue) — processed by a cloud agent via hybro.ai

The hub scans outbound messages for sensitive content before they reach cloud agents:

PII detection— emails, phone numbers, SSNs, credit cards, API keys Custom keywords— configure terms like "medical", "financial", "confidential" Custom patterns— add regex rules for project-specific data (e.g.,PROJ-\d{4})

Currently logs detections only. Active blocking and anonymization are planned for a future release.