LevelCode v0.7.0

LevelCode v0.7.0

Fixes multi-root workspaces in the agent — added folders were previously invisible and unreachable — and finishes the de-branding sweep.

Highlights

Multi-root workspaces now work end-to-end in the agent

The agent's tool layer resolved every path against workspaceFolders[0], and its sandbox check rejected anything outside it — so any folder added with File → Add Folder was invisible and unreachable.

Worse, the failure was self-contradicting: list_files was already multi-root aware (via findFiles/asRelativePath), so it happily listed folder-name-prefixed paths that every other tool then refused to resolve. The agent could see a file and not read it.

• resolveWorkspacePath() — one shared resolver. The sandbox is now the union of workspace folders, read live per call, so a folder added mid-session works on the very next tool call. It accepts the asRelativePath folder-name-prefix convention, probes the other folders for reads, and on create targets the named folder (else the first).
• search sweeps every folder and prefixes hits with the folder name, so results feed straight back into read_file / edit_file.
• run_command takes an optional folder input to pick the working directory.
• System prompt names every workspace folder per run, and path errors hint the addressable folder names.
• reviewSession (applyEdit / applyDelete) uses the same resolver, so the agent and the Keep/Undo pipeline can never disagree about where a file lives.

Adds test/workspacePaths.test.js — 14 cases, including a literal repro of the mid-session Add Folder bug and folder-escape rejections.

The Agents aquarium is ours now

The Agents-window easter egg (sessions.developerJoy.enabled) rendered its swimming "fish" as the literal VS Code logo silhouette, tinted with VS Code's three release-channel colours (#007ACC / #24bfa5 / #E04F00). It's now the LevelCode double chevron in our brand-gradient stops (#6a3fe0 / #7069ff / #4fb2ff) — same easter egg, our mark.

This was the last reachable Microsoft mark in the shipped app, completing the de-branding that landed in v0.6.0.

Also — landed server-side since v0.6.0 (no update needed)

v0.6.0's notes flagged that the metered LevelCode Cloud gateway still had to forward cache_control upstream before prompt caching would land. It now does, and it's verified in production: cache reads are non-zero and grow across turns, with OpenRouter reporting an ~87% cache-read discount on affected generations. Because it's server-side, every client already benefits — including builds older than v0.7.0.

Changed files

• extensions/levelcode-ai/agent.js
• extensions/levelcode-ai/reviewSession.js
• extensions/levelcode-ai/test/workspacePaths.test.js
• scripts/de-brand.mjs
• docs/CORE-PATCHES.md

Full changelog: v0.6.0...v0.7.0