Manage your Clawne

Clawnes improve through small, deliberate changes — not one perfect setup.

Edit a Clawne

Change one thing at a time. The most common updates:

• Tighten the role — if responses drift outside the job, make the role sentence more specific
• Adjust the tone — if responses feel off, update the personality direction before changing anything else
• Add or remove a tool — add only when a specific workflow demonstrates the need; remove if the Clawne uses a tool incorrectly or too eagerly
• Update memory — add entries for preferences that keep repeating; remove entries that no longer apply

Clone a Clawne

Clone when you want to test a variation without affecting the working version, or when one use case has grown into two distinct jobs.

Give the clone a job-specific name immediately. Clawnes named for their role are easier to maintain than ones named for a version.

Archive a Clawne

Archive rather than delete. An archived Clawne preserves its configuration in case you want to reference its role or memory setup later.

Signs it is time to split

• the role sentence requires "and also"
• tone conflicts between different kinds of work
• memory assumptions that contradict each other

Healthy iteration loop

1. test with a real task you did last week
2. note exactly where the response drifted
3. change the smallest thing that would fix it
4. retest with the same task

Small, targeted edits beat large rewrites. If a Clawne needs more than three changes at once, it is probably trying to do two jobs.