initialize_workspace

Activate an additional repository workspace in the current Context Engine session.

initialize_workspace activates another repository or project root so semantic tools can work against it in the current session. The workspace root determines project discovery, configuration loading, language-server startup, and analysis resources.

Use when

You need to work with a repository other than the workspace where the session started.
You need an explicit workspace boundary for a second project.

Do not use when

You are working in the session's already-active workspace; call semantic tools directly.
You only need to refresh configuration or restart an existing workspace.

Request

{"workspace_root":"/absolute/path/to/repository"}

Parameters

Parameter	Type	Required	Description
`workspace_root`	string	Yes	Absolute repository or project root path, or a `file://` URI. Pass the project root rather than a nested source directory.

What it returns

The workspace is activated after .context-engine/config.toml is loaded and its language servers and analysis infrastructure begin starting. Some servers may still be starting or indexing when the call returns, so the first semantic request can wait for readiness.

Common mistakes

Passing a relative path or a nested source directory instead of the project root.
Initializing the workspace repeatedly when it is already active.
Assuming every language server is ready immediately; first use may wait while startup or indexing finishes.

index_workspace eagerly prepares broad workspace analysis.
shutdown_workspace releases an additional workspace when you are finished.
reload_config applies configuration changes to an active workspace.