Fix a frozen coding agent on your home PC from your phone
- Level Intermediate
- Setup1–3 hrs (estimated)
- Evidence Some evidence
- CostNot stated in source
- No-codeYes
What they did
Codex stopped responding on a user's home PC while he was out. From his phone, he asked his Grok Bot what was wrong. It checked the PC remotely and found Codex still running, with 539 threads, hundreds of leftover node processes and his 32GB of RAM nearly full.
How it went
It asked permission, then killed the stuck processes and restarted Codex. Free RAM went from 2.8GB to about 10GB, and he never touched the computer.
Worth knowing
- Self-reported X post; the bot needs remote access to your machine.
- It asked before killing anything, which he says is the part that matters.
Prompt
Cleaned version rewritten from the source — not a direct quote.
[App] on my PC stopped responding. Check what's running: CPU, RAM, threads and process counts. Tell me what's stuck and what you'd kill, and wait for my yes before you kill anything or restart [app].
Recommended
Try it in Grok Bot
- Copy the prompt (button below).
- Open Grok Bot chat and paste it. Replace any [bracketed] placeholders.
- Connect the listed tools (as needed) as connectors when Grok Bot asks.
- If the task repeats, ask: "Make this a daily routine."
Alternatives: the same prompt works in Claude, ChatGPT Agent, OpenClaw.
Set it up
Stack: Grok Bot
- Read the original source for full context.
- Connect the tools your agent needs.
- Paste the prompt and replace [bracketed] placeholders.
- Run once manually and check the output before scheduling it.
Generic suggested steps, not from the source.
Evidence
Self-reported X post; the bot needs remote access to your machine. It asked before killing anything, which he says is the part that matters
Source: X · 2026-09-04 · Verified by us: not yet · Report broken or outdated