Spaces

A space is a named partition for memories, pages, and recall context. It is for separating work streams that should not automatically inform each other.

Use spaces when you switch between clients, personal projects, experiments, or repos with very different context.

The most explicit override is WENLAN_SPACE. It is useful when launching an agent for a specific context and you want every capture and recall to stay in that bucket.

The CLI also includes wenlan space commands for listing, adding, inspecting, and moving spaces.

Wenlan can read space configuration from ~/.wenlan/spaces.toml. Map directory prefixes to spaces when you want a repo or notes folder to select the same context every time.

Longest matching prefix wins. A top-level default applies when no mapping matches.

Wenlan resolves the active space through a priority chain. Explicit overrides win, then the shell environment, then spaces.toml, then the current git repo name, then topic fallback, then personal.

Use wenlan doctor when you are unsure which layer selected the current space. Doctor prints the resolver state so you can diagnose accidental context bleed.

Recall should start inside the active space so a client project does not accidentally pull personal notes or an unrelated repo history.

If you intentionally need cross-space context, move or recapture the durable fact into the right space rather than relying on accidental bleed.

Spaces are not separate user accounts, encryption boundaries, or permission systems. They are product-level context separation inside your local Wenlan store.

For sensitive work, still treat the whole local machine and connected AI client as part of the privacy boundary.