Разработка
Run an agency from your phone: Grok Bot as the front door, Tailscale + SSH to your machines, run locks and an approval hook
Your real work and your keys live on machines at home, but you want to run everything from your phone.
Что болело
BH (@brendenvonhouse) runs an SEO agency from one Grok Bot chat on his phone. The bot's cloud computer joins his private Tailscale network, SSHes into two home machines, and hands work to whichever machine owns it. Not affiliated with xAI.
Что установить или создать
Ask the bot to install Tailscale on its computer and approve the device on your phone; give it its own SSH key on each machine (no public ports). The main bot only routes and checks; specialists own one lane each. Routine logic lives in scripts on your machines, described in one driver-neutral runbook, and each run first takes a lock file so a second agent prints SKIP. A pre-tool hook on the machine holding the keys blocks sends, publishing, deploys and deletes until you say yes.
Боты
Router (main bot)
Takes every message from your phone, routes it, checks receipts. Never does client work.
Lane specialists
One lane each; start from the handoff and nothing else.
Плагины
В первый день не нужны. Следуйте шагам первого запуска.
Рутины
На первом запуске их нет. Сначала пройдите один раз вручную.
Промпт
Это совет, а не системный промпт, который можно вставить. Автор его не опубликовал. Следуйте шагам первого запуска.
Первый запуск
- 1Read https://x.com/brendenvonhouse/status/2109070749046604027 (credit @brendenvonhouse).
- 2Ask your bot: "Can you get Tailscale and connect to my computer?" Approve it on your phone, then add one SSH key just for the bot.
- 3Move one routine's logic into a script on that machine, and write its runbook entry with "the driver" instead of an agent's name.
- 4Add a run lock at the top of the script (one lock file per routine per day) so a second run prints SKIP.
- 5Add the approval hook before you let anything send, publish or deploy; add a second driver only after a clean week.
Барьер одобрения
Keys stay on your own machine. The hook answers "needs a yes" for any send, publish, deploy or delete, and a yes only counts where it was given.
Что поправить
The boundary lives in the network, the keys and the approval hook, not in the shared cloud computer.
Источник
BH @brendenvonhouse · Исходный пост
Не связаны с xAI. Этот промпт написали не мы. Условия сторонних шаблонов по-прежнему действуют.
Пакет Pro
Нужна полная настройка, а не только идея?
В пакетах Pro — текст задачи, промпты, расписания и подводные камни для популярных сценариев.