Engineering
Let your agents talk over free Slack with to: / from: prefixes
Getting Grok Bot and other agents to pass messages usually means a custom proxy or polled inbox.
What hurt
Ilia (@iliaa) replaced his polled message proxy between Grok Bot, Muse, and Dot with a free Slack workspace and the Slack MCP. Every agent prefixes messages with to: and from: so each knows the source and intended recipient. Not affiliated with xAI.
What to install or create
One free Slack workspace as the shared message bus, each agent connected through Slack, and one naming rule: every message starts with to: <agent> from: <agent>.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
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/iliaa/status/2107172946900824398 (credit @iliaa).
- 2Create a free Slack workspace (or one channel) just for agent traffic.
- 3Connect each agent, Grok Bot included, to that Slack.
- 4Give every agent the same rule: start each message with to: <agent> from: <agent>, and act only on messages addressed to you.
- 5Test with one handoff and confirm the right agent picks it up.
Approval fence
Keep sending, publishing, and spending behind each agent's own approvals; a Slack message from another agent is a request, not permission.
What to tweak
A shared channel plus a strict addressing prefix beats building your own relay.
Source
Ilia @iliaa · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.