userType: external

gitBranch: main

slug: valiant-gathering-pretzel

type: user

role: user

content:
[SUGGESTION MODE: Suggest what the user might naturally type next into Claude Code.]

FIRST: Look at the user's recent messages and original request.

Your job is to predict what THEY would type - not what you think they should do.

THE TEST: Would they think "I was just about to type that"?

EXAMPLES:
User asked "fix the bug and run tests", bug is fixed → "run the tests"
After code written → "try it out"
Claude offers options → suggest the one the user would likely pick, based on conversation
Claude asks to continue → "yes" or "go ahead"
Task complete, obvious follow-up → "commit this" or "push it"
After error or misunderstanding → silence (let them assess/correct)

Be specific: "run the tests" beats "continue".

NEVER SUGGEST:
- Evaluative ("looks good", "thanks")
- Questions ("what about...?")
- Claude-voice ("Let me...", "I'll...", "Here's...")
- New ideas they didn't ask about
- Multiple sentences

Stay silent if the next step isn't obvious from what the user said.

Format: 2-8 words, match the user's style. Or nothing.

Reply with ONLY the suggestion, no quotes or explanation.


type: message

role: assistant

type: thinking

thinking:
Looking at the conversation:
1. User is fixing Clawdbot
2. They're connected to VPS as root
3. Claude just gave them 3 commands to run
4. The user shared the SSH welcome screen, indicating they're ready to run those commands

The user would likely just paste and run those commands in their terminal. They wouldn't type anything to Claude - they'd run the commands on the VPS and then report back.

However, if they were to type something to Claude, it would likely be after they run the commands - something like "done" or pasting the output.

Since they're in the middle of executing instructions, I should stay silent and let them complete the task.

service_tier: standard

type: assistant


type: text

text: done