Engineering build desk
Code, review, and audit — you still merge.
6 bots · 30 min to stand up
Open blueprintAll use cases
Engineering
Tip only: phone the bot to fix a stuck PC
Codex hung. You were not home. The machine was melting RAM.
What hurt
Adam (@Adamdesgns) was out when Codex stopped responding. From his phone he asked his Grok Bot what was wrong. She checked the PC remotely, found Codex still running plus hundreds of leftover node processes and almost no free RAM, asked permission, then killed the stuck work and restarted Codex — free RAM jumped from about 2.8GB to about 10GB. He never touched the computer. Tip only.
What to install or create
One desk bot with computer access. Diagnose → explain → ask → fix. You approve kills and restarts.
Bots
Desk Ops
When you ask from your phone: inspect the registered computer, explain what looks stuck, request approval, then fix only what you allowed.
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/Adamdesgns/status/2095976077256712536. Tip only.
- 2Give one Grok Bot access to the computer you leave running (registered machine / agent computer).
- 3From your phone, ask: what is wrong with Codex / why is RAM low — do not pre-authorize kills.
- 4Read the diagnosis. Approve only the kill/restart steps you want.
- 5Confirm free RAM / that the tool is responding before you hang up the chat.
Approval fence
Do not kill processes, restart apps, delete files, or spend without your yes.
What to tweak
Steal the ask-before-kill remote ops loop.
Source
Adam @Adamdesgns · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.