userType: external

gitBranch: main

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 is asking about OAuth tokens and why Claude Code's token works but Clawdbot's doesn't. I explained that they're separate applications with separate configurations.

I offered to look at where CB stores its Notion credentials.

What would the user naturally type next? They'd probably want me to find where CB's config is so they can update the token. They seem to be in troubleshooting mode.

"yes" or "yeah check it" or "find cb's notion config" would be natural responses to my offer.

service_tier: standard

type: assistant


type: text

text: yeah find cb's notion config