Manage contexts and namespaces

A context chooses the tenant endpoint and credential. A namespace chooses the resource scope inside that tenant. They are separate decisions.

How do I prevent a scope mistake?

Launch with xcsh --context <NAME> and inspect /context status. For automation, pass -n <NAMESPACE> to the resource command instead of relying on ambient state. Stop if either value is unexpected.

Where is context data stored?

Context files live under .xcsh/contexts/ at project scope or the xcsh user data directory. Never commit them: they can contain credentials and tenant identifiers.

Select context and namespace before any live read or write, then issue a read-only command for an expected resource and inspect the returned tenant scope. Context files contain connection metadata and may reference credentials; keep them out of repositories and transcripts. Changing the active scope affects later commands only. After a temporary test, restore the prior context and namespace and repeat the read-only check.