# Atlas per-client context profiles > Atlas Client Context Profiles loads a client's voice rules, people, and constraints automatically when you open that client's repository, so the agent works as the right operator for each client. Atlas Client Context Profiles is for people who work across many client repositories. When you open a client's repository, Atlas loads that client's context from a git-tracked persona file in the project: the voice and formatting rules, the people, and the active constraints. The agent shows up already being the right operator for that client, instead of being told the same context every session. The engine ships today behind the paid tier, and Atlas Pro is not yet on sale. ## Key takeaways - Built and running in Atlas. Included in the paid tier, which is not yet on sale. - Reads a git-tracked persona file in the project. That file alone is enough to work. - Injects a client_persona block into session context from the first prompt. - Shows an always-on status indicator so you can see which client you are operating as. - People and open commitments enrich the profile only when the graph and Intake are on. ## A different operator in every repo A consultant is a different operator for each of their 5 or 10 clients, with different voice rules, people, and constraints. Client Context Profiles switches that context automatically when you open a client's repository, so one client's conventions never leak into another's work and you never re-explain who the people are or how that client wants deliverables written. ## One git-tracked file, not a hidden database The profile is 1 markdown file committed in the client's repository, with no database behind it. Because it is a plain file under version control, the profile is reviewable in a pull request, portable, and readable without Atlas. It is also the reason the capability works on its own: the assembler needs nothing but that file. Everything else is optional enrichment. ## Enrichment is optional, and honest about it Atlas can pull 2 further sources into the profile, and both are genuinely optional. People can come from the project knowledge graph and open commitments from filed call notes, but only when those engines are enabled. When they are not, the assembler falls back cleanly rather than pretending: you get the voice and constraints from your persona file, and nothing is silently invented. You can inspect exactly what is being injected before you trust it. ## Availability Client Context Profiles is 1 of the 8 record engines in Atlas, and it sits behind the paid tier. The engine is built and running in the product, gated to Atlas Pro. Pro has no checkout yet, so it is not something you can buy today. Shipped, the automated work log, is the one record engine available free right now. ## FAQ ### Is Atlas client context loading available now? The engine is built and running in Atlas, but it sits behind the paid tier and Atlas Pro is not yet on sale, so you cannot purchase access today. ### Who is this for? Consultants, agencies, and anyone working across multiple client repositories who needs the agent to adopt each client's voice and constraints without being told each session. ### What context does it load? Voice and formatting rules, the client's people, and active constraints, read from a git-tracked persona file in the project. Open commitments join in when Intake is also enabled. ### Do I have to write a profile for each client? Yes, a small per-client file covering voice and constraints. It is the only required input, and it lives in the client's repository so it is reviewable like any other file. ### Can I see what is actually being injected? Yes. Atlas can show you the assembled block, so you can check exactly what the agent is being told rather than trusting an invisible prompt. --- Canonical HTML: https://runatlas.sh/resources/features/client-context-profiles Source of truth: aeo_pages row `/resources/features/client-context-profiles` (segment: Platform) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.