{"version":"2.1.283","anchor":"system-prompt-and-mcp-rootslist-handle-sessions-with-no-wor","canonical_anchor":"system-prompt-and-mcp-rootslist-handle-sessions-with-no-wor","heading":"Sessions without a working folder no longer report one","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/system-prompt-and-mcp-rootslist-handle-sessions-with-no-wor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Sessions without a working folder no longer report one\n\nWith no working folder, Claude leaves the folder and git lines out of its setup notes, and MCP servers are not given a folder\n\n**Unclear.** How a session ends up with no working folder is not known.\n\n**What**\n\nClaude Code tells the model some facts about your computer at the start of a session. When the session has no working folder, it now leaves out the working folder line, the worktree lines and the line saying whether the folder is a git repository. Platform, shell, operating system version and any extra folders are still listed.\n\nMCP servers (add-on servers that give Claude extra tools) can ask Claude Code which folders they may work in. That answer now includes the current folder only when there is one. A session has no working folder when there is no original folder set and no project.\n\n**Why**\n\nThe model and MCP servers are no longer given a working folder that does not mean anything for that session.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}