Engineering
Local Hermes drives cloud Grok Bot via webhook
Tailscale on the Grok Bot box is flaky; local Hermes still needs the cloud bot.
What hurt
Vibemak (@vibemak) wants a local Hermes agent to drive a cloud Grok Bot. Installing Tailscale on the Grok Bot machine felt unstable, so they sketch a webhook path instead: Hermes → curl POST → Grok Bot webhook routine → Grok Bot runs → Discord notifies both sides (cloud and local). Tip/path only; related to existing webhook wake patterns but names Hermes explicitly.
What to install or create
Skip VPN glue. Create a webhook-triggered routine on Grok Bot. From Hermes, curl POST the routine URL with the task payload. Let Grok Bot execute on its cloud box. Pipe status to Discord so both Hermes (local) and Grok (cloud) can see status.
Bots
Webhook worker
On webhook wake, run the posted task on the cloud box.
Plugins
None on day one. Follow the first-run steps.
Routines
Webhook trigger: accept Hermes curl POST, execute, Discord status.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/vibemak/status/2097851652032299283 (path: Hermes → curl → webhook routine → Discord).
- 2In Grok Bot, create a webhook-triggered routine (copy URL + sender key from the routine panel).
- 3From local Hermes, curl POST that URL with the task body.
- 4Have the routine post status to a shared Discord channel.
- 5Keep the sender key private; confirm before irreversible actions.
Approval fence
Protect the webhook URL/sender key. Do not expose it in public chats. Confirm before any spend/send the routine might trigger.
What to tweak
Steal the path: Hermes posts the wake; webhook routine owns cloud work; Discord is the shared status board.
Source
Vibemak @vibemak · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.