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.
-
The administrator enabled the AI assistant configuration for all workspaces. See Install the recommended AI assistant configuration in every workspace.
-
Create the
Secretin your namespace with theLOLA_DISABLEDvariable: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
trueexactly. The init container ignores any other value and continues the initialization. -
If the opt-out has no effect, the administrator may have set
LOLA_DISABLEDon the init container itself. An explicit value there takes precedence over thisSecret, so ask the administrator to remove it. -
If you already have this
Secret, add the variable to it. Other variables in the sameSecretkeep their effect. Do not delete theSecretand re-create it with only this key: while it is gone, the workspace restarts and installs the recommended module. -
The
Secretapplies to every workspace in your namespace. To scope the opt-out to some workspaces, add thecontroller.devfile.io/mount-to-devworkspace-includeannotation with a comma-separated list of workspace name patterns, orcontroller.devfile.io/mount-to-devworkspace-excludeto keep it out of the listed workspaces. See Mounting Secrets. These annotations scope the wholeSecret, including its other variables. If it also holdsLOLA_REPO_URL, create a separateSecretfor the opt-out instead of scoping the shared one: workspaces outside the pattern would otherwise fall back to the recommended module.
-
|
Creating the |
-
Restart the workspace if you set the
mount-on-startannotation. Without it, creating theSecretalready restarted it.
-
In the workspace,
/home/user/.lola/init-statuscontains the following line:ok <timestamp> disabled
-
Every new workspace that mounts this
Secretstarts without the AI assistant configuration.
Removing the installed content
Content that a previous start installed remains in /home/user.
-
Delete the installed skills, commands, and agents from the directory of each assistant of the previous start. See AI assistant configuration reference for the destinations of every assistant.
-
Delete the MCP servers from
/home/user/.mcp.json,/home/user/.claude.json,/home/user/.config/opencode/opencode.json,/home/user/.cursor/mcp.json, and/home/user/.copilot/mcp-config.json. Remove only the servers that the module installed, and keep the ones you added yourself. -
In a file that you also edit yourself, such as
CLAUDE.md,AGENTS.md, orGEMINI.md, delete only the sections between the Lola markers. Lola creates them again at the next installation:Each installed module has its own pair of
lola:modulemarkers inside the instructions block. Delete the whole instructions block to remove every generated section; keep the content you wrote outside the markers.
|
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. |
-
To restore the configuration, remove the
LOLA_DISABLEDvariable from everySecretthat applies to this workspace, and restart it.