Six Text Files Are the Difference Between a Chatbot and a Colleague
Installing an AI assistant takes 20 minutes. Making it useful takes longer.
Phase 1 is mechanical: install the software, pick a model, connect it to a chat app. Phase 2 is tools: API keys for WordPress, Dropbox, email, image generation. An hour, maybe.
Phase 3 is the part I had to figure out myself. I think of it as the brain.
The brain is six text files. A personality file covering how the assistant talks and what it values. A user file with who I am and how I work. A memory file holding every person, project, and lesson from months of collaboration. A playbook of behavioral rules. A daily journal for handoff between sessions. And a guide tying it together.
Phase 3 took longer than the first two combined. Not because the files are hard to write. Because they force you to decide what kind of assistant you actually want. (The AI will do exactly what you tell it; the problem is figuring out what to tell it.)
Plenty of people stop at Phase 2. They install the software, plug in some tools, start chatting. Things go well for a few days. Then the assistant starts forgetting preferences, asking the same questions, giving generic answers. Same software, same model. Six text files are the difference between a chatbot and something that resembles a colleague.
I’ve done this five times now. The personality, memory, and playbook from assistant #1 became the template for #2 through #5. Each got customized for a different job. By the fifth setup, I was cloning a trained employee and assigning them a new role.
OpenClaw is a self-hosted AI assistant on your own server. You control the model, the memory, the tools, the schedule. Over months, it accumulates enough context to function like a colleague who’s been there since the beginning.
I teach two classes on setting up and getting the most from OpenClaw at AI Partner School.
