Adapt the context surface to a task.

What changes

A persona is a configuration layer for how supported context operations behave. It can affect the source/view preferences and sensitivity floor associated with a domain.

It does not create expertise, make a model accurate or turn LeanCTX into an autonomous research or sales agent.

Inspect before selecting

Use the persona commands documented by your installed CLI. Inspect the persona’s actual configuration, including source scope and security implications, before applying it to a project.

A persona name alone does not establish that all required providers are connected or that the corresponding workflow is supported.

Verify on a real task

Compare the resulting sources and returned text with your task requirements. Check whether a restrictive sensitivity floor blocks material you intended to use, and whether a broader context choice introduces irrelevant content.

Keep security enforcement separate from stylistic preferences. A persona must not be used as a reason to bypass source permissions.

Keep the integration boundary visible

Persona behavior in the local runtime is not a new stable SDK interface. An application should depend only on the contract and capabilities negotiated by its SDK release.

For exact available settings, consult configuration and feature status.

Sources & versions2 references · Reviewed 17 Sept 2026

• 10-customization-and-governance.mddocs/reference/10-customization-and-governance.mdGitHub
• mod.rsrust/src/core/config/schema/mod.rsReviewed checkout

Core checkout

0ce2207ee4

Installed runtime

3.10.2

SDK release

1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility