{"version":"2.1.286","anchor":"bridge-child-processes-get-claude-code-bridge-source-dir","canonical_anchor":"bridge-child-processes-get-claude-code-bridge-source-dir","heading":"Bridge-started sessions receive their source directory","tier":"use","area":"Bridge","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/bridge-child-processes-get-claude-code-bridge-source-dir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Bridge-started sessions receive their source directory\n\nSessions started over the bridge now get a CLAUDE_CODE_BRIDGE_SOURCE_DIR environment variable holding their source directory\n\n**Unclear.** What reads this variable, and when the source directory is set, are not known.\n\n**What**\n\nWhen Claude Code starts a session through the bridge (the connection that lets it be driven from elsewhere), it now sets the environment variable `CLAUDE_CODE_BRIDGE_SOURCE_DIR` in that session. An environment variable is a named value passed to a program when it starts. This one holds the session's source directory, and it is on the list of variables allowed to pass through.\n\n**Why**\n\nA session started over the bridge can now tell which directory it came from.\n\n- Area: Bridge\n- Names: `CLAUDE_CODE_BRIDGE_SOURCE_DIR`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}