Warn users about session discontinuity when scaffolding a project outside the current workspace

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 7, 2026

Summary

When using Claude Code inside the VS Code extension to scaffold a new project, the tool can create a new project folder (in the user's usual projects directory) without opening that folder as the active workspace. If the user then manually opens the newly created folder in VS Code, the conversation history/context from the scaffolding session is lost — because sessions in the VS Code extension are scoped to the open workspace folder, not to the project being worked on.

Steps to reproduce

  1. Open VS Code with some workspace (or none) active, and start a Claude Code conversation asking it to scaffold a new project.
  2. Claude creates the new project scaffolding in a new folder (e.g. ~/projects/new-app), but does not open that folder as the VS Code workspace.
  3. User manually opens the newly created folder in VS Code.

Result

The previous conversation (including any decisions, rationale, or follow-up context from the scaffolding step) is not retained in the newly opened workspace — it effectively starts a brand-new session with no link back to the conversation that created the project.

Expected behavior

Since this discontinuity is inherent to how sessions are scoped to workspace folders, Claude Code should proactively warn the user before or immediately after scaffolding a new folder that:

  • the new folder is not currently open as the workspace, and
  • opening it separately will start a new session with no continuity from the current conversation.

Ideally, the tool would also offer to open the new folder as the workspace directly (or prompt the user to do so), rather than leaving that as a silent manual step that trips the discontinuity.

Why this matters

Users reasonably expect a "continue in the new project" experience when a tool scaffolds a project on their behalf. Silently losing conversation context is surprising and can lose useful decisions/rationale from the setup phase, especially for larger scaffolds where back-and-forth happened.

View original on GitHub ↗