Personal & life admin Security & guardrails𝕏 sourced

Private data stays in Hermes; cloud chores go to Grok Bot

Keep private data in Hermes and cloud chores in Grok Bot. Two-agent user drawing a data boundary.

Share on 𝕏 ↗ Compare with… Read the source ↗

what to steal

Draw a hard line between your local agent and your cloud agent, and you approve what crosses.

Our takeaway from the source, not a quote.

Drawn from this card's sourced fields. Amber = older model named by the source. Rose = cut or replaced.

zhiwehu-hermes-local-grokbot-cloud.toml

# Keep private data in Hermes and cloud chores in Grok Bot
# source: https://x.com/zhiwehu/status/2110230224348873069

[rig]
who     = "Two-agent user drawing a data boundary"
author  = "Jeffrey (@zhiwehu)"
date    = "2026-10-14"

harness = ["Hermes Agent", "Grok Bot"]
models  = []

[keep]
  - Hermes keeps private data local
  - Grok Bot handles cloud chores
  - He decides what crosses over
[cut]
  - Agents chatting freely

thing	status	why (per source)
Agents chatting freely	avoided	"A clean boundary beats clever chatter"

Source: https://x.com/zhiwehu/status/2110230224348873069 · checked 2026-10-14

OpenClaw and Hermes in separate VMs, so neither is a single point of failure

steal → Put each agent in its own snapshot-able VM; fix credentials next.

OpenClawHermes AgentCodex GPT-5.5Qwen3.6 27B / 35B Credentials in the age

by Eli Lap

~/rigs/nathandarker-hermes-three-bo….tomlundated

Three Hermes bots in Docker, one Telegram topic each

steal → Give each bot one domain and mount only the folders it needs.

Hermes Agent Home directory mount

by Nathan Darker

~/rigs/nadimtuhin-mac-controls-pc-r….toml2026-09-01

Laptop as control room, home PC as the engine

steal → Run agents on an always-on box behind one model gateway; reach it with zero open ports.

Claude CodeCodexPi Any model behind 9Rout

by Nadim Tuhin