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 asked to fix clawdbot
2. We went through a debugging process
3. User helped run sudo commands via SSH
4. Fix is now complete - clawdbot is working

The user's original request was just to fix clawdbot. That's done now. There's no obvious next step that the user indicated they wanted to do.

The conversation is essentially complete. The user might want to test clawdbot, or they might just be done. There's no clear "next step" that they explicitly mentioned.

I should stay silent since there's no obvious follow-up from what the user originally asked for.

service_tier: standard

type: assistant


type: text

text: test clawdbot