The bot never answers
bot-no-reply
When the window sits still, check whether runs/today.md is still growing. That file comes from this site's Run receipt skill, not a built-in screen.
for Grok Bot · unofficial, not affiliated with xAI
CNPS0.1.02026-11-18New
Paste this note into Grok Bot and say: follow this note.
Note: The bot never answers
When the window sits still, check whether runs/today.md is still growing. That file comes from this site's Run receipt skill, not a built-in screen.
For: People whose window stays on “working” and never shows the next paragraph.
What to check:
1. Uses the time of the last log line to see whether it is still moving.
2. Names the usual waits: a connector prompt, a missing stop rule, or a file that is already complete.
3. Says when it is reasonable to stop the run. Entries in this version do not send.
Steps:
1. Read the time on the last line of runs/today.md. If the file is missing, Run receipt is not saved. Do not treat a blank window as the log.
2. If the last line is waiting on a connector, resolve that authorization. Do not send the same instruction again.
3. Open the output file named in the skill. If the file is complete and the window is silent, add a finish line. Trust the file next time.
4. After you stop it, retry with a shorter instruction and no customer data. Repeating the long one only stacks runs.
runs/today.md exists:
Time of the last line:
That line is start or finish:
Is the output file already complete:
Do not send, delete, or pay:
Do not:
- Do not grant sending, deleting, or paying in order to end a stall.
- Do not copy the stalled chat elsewhere.
- Do not treat a still window as a built-in run log. Read runs/today.md from this site's Run receipt skill.
Paste this note into Grok Bot and say: follow this note.What it does
- Uses the time of the last log line to see whether it is still moving.
- Names the usual waits: a connector prompt, a missing stop rule, or a file that is already complete.
- Says when it is reasonable to stop the run. Entries in this version do not send.
Who it is for
People whose window stays on “working” and never shows the next paragraph.
How to put it in Grok Bot
- Read the time on the last line of runs/today.md. If the file is missing, Run receipt is not saved. Do not treat a blank window as the log.
- If the last line is waiting on a connector, resolve that authorization. Do not send the same instruction again.
- Open the output file named in the skill. If the file is complete and the window is silent, add a finish line. Trust the file next time.
- After you stop it, retry with a shorter instruction and no customer data. Repeating the long one only stacks runs.
Example
Three lines while it sits
runs/today.md exists:
Time of the last line:
That line is start or finish:
Is the output file already complete:
Do not send, delete, or pay:Connectors it needs
No connector.
Safety and permissions
- Do not grant sending, deleting, or paying in order to end a stall.
- Do not copy the stalled chat elsewhere.
- Do not treat a still window as a built-in run log. Read runs/today.md from this site's Run receipt skill.
Risk: Low
Questions
How long should I wait?
There is no universal number of seconds. Watch the log. When the log stops, waiting on the window does nothing.
Does memory disappear when the chat ends?
See Keep memory for the next run. xAI's docs say memory persists across chats (https://docs.x.ai/grok-bot/bots). This site does not say what closing a window does. Write a changing fact in memory/bot.md.
0.1.0
2026-11-18
First published text. Judge a hang from the log. No invented timeout.