Persist AI assistant configuration
Persist Claude Code configuration across OpenShift Dev Spaces workspaces so that skills, settings, MCP servers, and plugins survive workspace restarts. Choose from PVC direct mount, PVC tmp copy, or GitOps approaches based on your storage and workflow requirements.
- Persist Claude Code configuration across workspaces
Persist Claude Code skills, settings, MCP servers, and plugins across OpenShift Dev Spaces workspaces by storing them in a shared volume or a Git repository. Without persistence, each new workspace requires a fresh setup. - Share Claude Code configuration with PVC tmp copy
Share Claude Code configuration across OpenShift Dev Spaces workspaces by copying files from a dedicated PVC mounted at/tmp/claude. No init pod is required, but changes must be synced back manually before stopping the workspace. - Share Claude Code configuration with PVC direct mount
Share Claude Code configuration across OpenShift Dev Spaces workspaces by mounting a dedicated PVC directly to the configuration paths. All changes persist automatically without manual sync steps. - Share Claude Code configuration across workspaces with GitOps
Share Claude Code configuration across OpenShift Dev Spaces workspaces by storing it in a Git repository. Each workspace gets its own isolated, writable copy of the configuration, preventing multi-attach errors and data corruption risks. - Distribute AI assistant skills and commands across workspaces with Lola
Distribute team-authored skills, commands, and agents from a central Git repository into OpenShift Dev Spaces workspaces using Lola. Lola supports multiple AI assistants, including Claude Code, Cursor, Copilot, Gemini CLI, and OpenCode. - Troubleshoot Claude Code configuration persistence
Diagnose and resolve issues with persisting Claude Code configuration in OpenShift Dev Spaces workspaces. Match the symptoms below to identify the root cause and apply the corresponding solution.
Related information