Disable the AI assistant configuration initialization

If you do not want the AI assistant configuration in your workspaces, disable the initialization for your namespace. The init container still runs, but it does not fetch, install, or change any content.

Prerequisites

The administrator enabled the AI assistant configuration for all workspaces. See Configure a recommended AI assistant configuration.

Procedure

Create the Secret in your namespace with the LOLA_DISABLED variable:
```
apiVersion: v1
kind: Secret
metadata:
  name: lola-config
  labels:
    controller.devfile.io/mount-to-devworkspace: "true"
    controller.devfile.io/watch-secret: "true"
  annotations:
    controller.devfile.io/mount-as: env
stringData:
  LOLA_DISABLED: "true"
```
- Set the value to true exactly. The init container ignores any other value and continues the initialization.
- If you already have this Secret, add the variable to it. Other variables in the same Secret keep their effect.

Creating the Secret restarts the running workspaces in your namespace. To avoid that, add the controller.devfile.io/mount-on-start: "true" annotation: the Secret is then mounted at the next workspace start, which is soon enough, because the init container reads it only when the pod starts. See Mounting Secrets.

Restart your workspace.

Verification

In the workspace, /home/user/.lola/init-status contains the following line:
```
ok <timestamp> disabled
```

Result

New workspaces in your namespace start without the AI assistant configuration.
Content that a previous start installed remains in /home/user. To remove it, delete the installed skills, commands, and agents from the directory of each assistant of the previous start: /home/user/.claude for Claude Code, /home/user/.config/opencode for OpenCode, /home/user/.cursor for Cursor, /home/user/.gemini and /home/user/GEMINI.md for Gemini CLI, /home/user/.copilot for Copilot, and /home/user/.openclaw for OpenClaw. Delete the MCP servers from /home/user/.claude.json, /home/user/.config/opencode/opencode.json, and /home/user/.copilot/mcp-config.json. See Prepare a Lola module for Che workspaces for the destinations of every assistant.
In a file that you also edit yourself, such as CLAUDE.md, AGENTS.md, or GEMINI.md, delete only the sections between the Lola markers. Lola creates them again at the next installation:
To restore the configuration, remove the LOLA_DISABLED variable from the Secret and restart the workspace.

You cannot remove the init container from a workspace yourself, because it is part of the cluster configuration. To stop the initialization for the whole cluster, contact your administrator.