CremindProfiles
How Cremind profiles isolate skills, embeddings, tool visibility, and conversation history so one install can host several assistants at once.
A profile is Cremind's unit of isolation. One install can host several assistants — a work assistant, a coding assistant, a home assistant — side by side, without any of them seeing into the others. Each profile is, in effect, its own little assistant with its own memory and its own toolbox.
What a profile isolates
Each profile keeps the following separate from every other profile:
| Isolated per profile | Why it matters |
|---|---|
| Skills directory | Each profile installs and sees only its own skills. |
| Embeddings | Document and memory vectors are scoped per profile, so retrieval never crosses contexts. |
| Tool visibility | A tool exposed to one profile isn't automatically exposed to another. |
| Conversation history | Chats in one profile are invisible to the rest. |
Because LLM configuration is also per profile (see LLM Model Groups), different profiles can even run on different models for the same kind of work.
Why isolate?
Mixing contexts is how assistants get confused — and how sensitive information leaks. A coding assistant doesn't need your personal calendar in its embeddings; a home assistant doesn't need your work tickets in its conversation history. Profiles draw a hard line so the right context is present for the right job and nothing more.
It's also practical: you can give each profile exactly the skills and tools it needs, keeping the tool surface small and focused for the task at hand.
A profile's documents
Document RAG respects the profile boundary too. Cremind watches both a shared documents root and a per-profile documents/ folder; files dropped into a profile's folder are indexed into that profile's vector store only. See Document RAG for how indexing works.
Creating and using profiles
You create your first profile in the Setup Wizard during first run. From the CLI, cremind exposes profile management commands alongside conversations, tools, and channels — run cremind --help to list them. Every surface (Web UI, Cremind App, CLI, chat channels) operates against a selected profile, so switching profiles switches the whole assistant — skills, tools, history, and embeddings together.
Cremind is version 0.0.1 and community-driven. Profile capabilities are evolving — check the repository for the latest commands and configuration.
Design Principles
The ideas that shape Cremind — self-hosted, built on open protocols, isolated by profile, cost-aware, event-driven, and storage that scales with you.
LLM Model Groups
How Cremind splits work between an expensive "high" reasoning model and a cheap "low" per-tool model to lower token cost.