userType: external

gitBranch: main

slug: enumerated-foraging-wave

type: message

role: assistant

type: text

text:
There's no DeepSeek in this codebase - I searched earlier and found zero references. The Clawdbot system uses **Claude (Anthropic API)** exclusively for AI features.

Are you asking about:

1. **DeepSeek in general** - the Chinese AI company/model capabilities?
2. **Adding DeepSeek** to Clawdbot as an alternative to Claude?
3. **Something else** you saw mentioned somewhere?

If you're thinking about adding DeepSeek, note that `COO.md` has a security rule about Kimi (another Chinese AI):

```
**Never share with Kimi:**
- Codebase
- API keys
- Customer data
- Database access
```

Similar restrictions would likely apply to DeepSeek given it's also a Chinese AI model.

service_tier: standard

type: assistant


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.


text: [Request interrupted by user]