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:
The user needs to paste and run the commands in their root SSH terminal. They just ran a partial command (missing the destination). I gave them the full commands to run.

They would likely just copy and paste the commands again. But that's not something they'd type - they'd just paste what I gave them.

After they run the commands, they'd want to test clawdbot again to see if it's working.

Actually, they might just copy/paste the commands. Not really something to suggest here. Let me stay silent or wait for them to confirm they ran the commands.

I'll stay silent since the next step is for them to run the commands in their SSH terminal, not type something to me.

service_tier: standard

type: assistant


type: text

text: done