Разработка

Tip only: phone the bot to fix a stuck PC

Codex hung. You were not home. The machine was melting RAM.

Что болело

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.

Что установить или создать

One desk bot with computer access. Diagnose → explain → ask → fix. You approve kills and restarts.

Боты

Desk Ops
When you ask from your phone: inspect the registered computer, explain what looks stuck, request approval, then fix only what you allowed.

Плагины

В первый день не нужны. Следуйте шагам первого запуска.

Рутины

На первом запуске их нет. Сначала пройдите один раз вручную.

Промпт

Это совет, а не системный промпт, который можно вставить. Автор его не опубликовал. Следуйте шагам первого запуска.

Первый запуск

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.