FAQ and troubleshooting
My Clawne feels too generic
Narrow the role and be more explicit about the personality. The most common cause is a role sentence that covers too much — try rewriting it as one tight job description.
My Clawne forgets what matters
Check whether memory is enabled. If it is, review the stored entries — memory that no longer matches the current job can confuse the Clawne more than help it.
My Clawne feels too opinionated
Reduce the personality intensity and specify where the Clawne should ask before deciding, rather than assuming.
My Clawne uses tools too often or incorrectly
Remove tools that are not clearly required by the workflow. A Clawne that reaches for tools unpredictably is a signal that the role is under-specified, not that the tools are wrong.
My Clawne responds inconsistently between sessions
This usually means the memory is incomplete or the role prompt is ambiguous enough that context changes the output. Tighten the role first, then review memory.
Can I have multiple Clawnes for different jobs?
Yes. That is the intended model. Each Clawne should have one job. Use a naming pattern that reflects the role rather than a version number.
Do I need to understand My Clawster first?
No. Clawne Me is meant to feel product-led. My Clawster becomes relevant when you want to understand deployment, provisioning, or platform-level behavior.
Where should I go if this feels like an infrastructure issue?
Use My Clawster for platform behavior and Operations for deployment concerns.