Persist Claude Code configuration in Che workspaces
To reuse Claude Code skills, settings, MCP servers, and plugins across Che workspaces, persist the configuration in a shared volume or a Git repository. Without persistence, each new workspace requires a fresh setup.
Claude Code configuration files
Claude Code stores configuration in two separate locations in the user’s home directory:
| Path | Contents |
|---|---|
|
Settings, plugins, custom agents, hooks, per-project memory. |
|
Application settings and MCP server configurations. |
|
MCP server configurations are stored in Claude Code writes runtime state to both paths during every session, including session files, caches, and usage statistics. These paths must be writable. Mounting a read-only ConfigMap or Secret directly to these paths causes Claude Code to fail. |
Available approaches
| Approach | Summary |
|---|---|
Both |
|
A dedicated PVC is mounted at |
|
Share Claude Code configuration across workspaces with GitOps |
A Git repository stores the baseline Claude Code configuration. The DevWorkspace Operator clones the repository at startup, and a |
Distributing skills and commands
To distribute team-authored skills, commands, and agents across workspaces without persisting the full configuration, see Distribute AI assistant skills and commands across workspaces with Lola. Lola supports Claude Code and other AI assistants.
Claude Code file reference
| Path | Purpose | Size | Regeneratable |
|---|---|---|---|
|
Permissions, hooks, enabled plugins, model preferences. |
Small |
No |
|
Local setting overrides. |
Small |
No |
|
User-level instructions for Claude. |
Small |
No |
|
Installed plugins and caches. |
Large (100 MB+) |
Partially |
|
Custom agent definitions. |
Small |
No |
|
Shell scripts for session lifecycle. |
Small |
No |
|
Per-project memory and settings. |
Medium |
No |
|
Application settings and MCP server configurations. |
Small |
No |
|
Conversation history. |
Large |
Optional |
|
Plugin download cache. |
Large |
Yes |