reload_config

reload_config validates and applies the active workspace's .context-engine/config.toml without rebuilding the workspace session. It selectively clears affected caches and restarts only language servers whose startup settings changed.

Use when

You changed a workspace language-server command, arguments, initialization options, language detection, analysis feature, or resource limit.
You changed file detection rules, roots, or project-root patterns and need the active workspace to use them.

Do not use when

You need to recover a crashed or unresponsive language server without changing configuration; use restart_workspace.
You have not changed .context-engine/config.toml.

Request

{}

Parameters

Parameter	Type	Required	Description
`workspace_root`	string \| null	No	Absolute workspace root or `file://` URI. If omitted, the sole active workspace is used; with multiple active workspaces, specify it.

What it returns

The result identifies languages added, modified, or removed; language servers restarted; whether the outline cache was cleared; and whether root detection was refreshed. Unaffected infrastructure is preserved, and newly configured servers start lazily. If loading or validation fails, the previous active configuration remains unchanged.

Common mistakes

Calling restart_workspace and expecting it to reload configuration; restart does not read .context-engine/config.toml.
Omitting workspace_root with multiple active workspaces.
Assuming a newly configured language server starts immediately; it remains lazy until needed.
Continuing after a validation error without correcting the configuration and retrying.

restart_workspace restarts currently running servers without reloading configuration.
index_workspace eagerly prepares broad analysis after configuration changes.