{"version":"2.1.301","anchor":"working-directory-tool-also-returns-shelldirectory-and-agent","canonical_anchor":"working-directory-tool-also-returns-shelldirectory-and-agent","heading":"Working-directory report now includes the shell's folder and proxy status","tier":"internal","area":"Agent Proxy","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/working-directory-tool-also-returns-shelldirectory-and-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Working-directory report now includes the shell's folder and proxy status\n\nA tool that reports the working directory now also returns the shell's current folder and whether an agent proxy is in use\n\n**Unclear.** Which tool returns this, and whether it reaches anyone outside remote sessions, is not clear.\n\n**What**\n\nA tool in Claude Code that reports the working directory (the folder Claude is working in) used to return only that folder and whether it is a git repository. It now also returns:\n\n- the folder the shell is currently in, which can differ from the working directory\n\n- whether an agent proxy is in use, taken from a lookup or from the `CCR_AGENT_PROXY_ENABLED` environment variable\n\n**Why**\n\nRemote sessions get more information about where the shell is and whether traffic goes through a proxy.\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}