Is SeaShell client context loading available now?

The engine is built and running in SeaShell, but it sits behind the paid tier and SeaShell Pro is not yet on sale, so you cannot purchase access today.

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. SeaShell can show you the assembled block, so you can check exactly what the agent is being told rather than trusting an invisible prompt.

SeaShell per-client context profiles for agencies (2026)

SeaShell Client Context Profiles is for people who work across many client repositories. When you open a client's repository, SeaShell 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 SeaShell Pro is not yet on sale.

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 SeaShell. 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

SeaShell 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 SeaShell, and it sits behind the paid tier.

The engine is built and running in the product, gated to SeaShell 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.

Frequently asked questions

Is SeaShell client context loading available now?: The engine is built and running in SeaShell, but it sits behind the paid tier and SeaShell 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. SeaShell can show you the assembled block, so you can check exactly what the agent is being told rather than trusting an invisible prompt.

Try SeaShell in your terminal

The terminal-native AI coding agent. Free core, single binary.

Install SeaShell

Related guides

Atlas with GLM-4.7 Flash in 2026

Explore Atlas with GLM-4.7 Flash, a genuinely free hosted model offering a 200K token context window. Ideal for background tasks, it's a zero-cost option for developers in 2026.

Atlas with Claude Opus 4.6 in 2026

Explore Atlas with Claude Opus 4.6 in 2026. This model offers a 1M token context window and 128K output, ideal for large codebases at $5/$25 per Mtok.

Run the Test Suite and Triage the Failures with Atlas in 2026

How to triage a failing test suite with Atlas in 2026: bash truncates at 2000 lines or 50 KB and saves the full log, then grep groups failures by root cause.

Atlas with GPT-5.4 nano in 2026

Explore Atlas with OpenAI's GPT-5.4 nano in 2026. This model offers a 400K token context window and $0.20/Mtok input pricing, ideal for high-volume, low-stakes coding agent tasks.

Atlas with Qwen3.5 27B (2026)

Drive Atlas with Qwen3.5 27B, Alibaba's dense 27B reasoning model released in February 2026. It offers a 256K token context and 65,536 token output for robust coding tasks.

Atlas with Gemini Flash Latest in 2026

Explore Atlas with Gemini Flash Latest, Google's fast, rolling AI model. Ideal for dynamic teams in 2026 seeking an always-current coding agent with a 1M token context.

Atlas with GPT-5.1 Codex mini in 2026

Explore Atlas with GPT-5.1 Codex mini in 2026. This model offers a 400K token context window at $0.25/Mtok input, making it ideal for tool-driven coding tasks.

Atlas with Mistral 7B in 2026

In 2026, Atlas users can leverage Mistral 7B for quick provider configuration smoke-testing. This 7B model offers an 8,000 token context window and costs $0.25 per 1M tokens.

Browse this resource hub