The App's Claude Is Not Your Claude

// Lines 1 to 52 elided: the module header, the SDK import, and settingSourcesFor. Full file: server/src/sdk-stream.js at tag module-30.

/**
* Build the `options` object the one `query()` call is given.
*
* Pulled out of `sdkStream` so the options can be read without calling the SDK.
*
* @param {SessionRequest} request
* @returns {Record<string, unknown>}
*/
export function buildQueryOptions(request) {
return {
  // The agent works in the workspace directory, never in the repository that
  // holds this server. See docs/decisions/0004.
  cwd: request.cwd,
  // The full Claude Code system prompt. Omitting `systemPrompt` gives the
  // SDK's minimal default, which covers tool calling and nothing else, an
  // agent that would not know it has a workspace. Declared at sdk.d.ts line
  // 2163 as `string | string[] | { ... }`. See docs/decisions/0005.
  systemPrompt: { type: "preset", preset: "claude_code" },
  // Verified against @anthropic-ai/claude-agent-sdk 0.3.251: sdk.d.ts line
  // 1828 declares `permissionMode?: PermissionMode`, line 2238 gives the
  // union `'default' | 'acceptEdits' | 'bypassPermissions' | 'plan' |
  // 'dontAsk' | 'auto'`, and line 1826 describes `'dontAsk'` as "Don't prompt
  // for permissions, deny if not pre-approved". Record 0011 covers why this
  // version runs under it and what it costs.
  permissionMode: request.permissionMode,
  // Ask for the answer in pieces as the model writes it, rather than one
  // finished assistant message at the end. With this on the stream also
  // carries messages of type "stream_event", each holding one raw API event.
  // Verified against 0.3.251: sdk.d.ts line 1720 declares
  // `includePartialMessages?: boolean`, "When true,
  // `SDKPartialAssistantMessage` events will be emitted during streaming".
  includePartialMessages: true,
  // The environment the subprocess runs under, with `CLAUDE_CONFIG_DIR`
  // pinned to the directory this application owns.
  //
  // `Options.env` is declared at sdk.d.ts line 1520 as `env?: { [envVar:
  // string]: string | undefined }`, and its doc comment at lines 1504 to 1519
  // states the fact the whole arrangement turns on: "When set, this value
  // REPLACES the subprocess environment entirely, it is not merged with
  // `process.env`. Spread `process.env` yourself if the subprocess still
  // needs inherited variables like `PATH`, `HOME`, or `ANTHROPIC_API_KEY`."
  // `isolationEnv` in config.js does the spreading, and does the pinning
  // after it. Record 0031.
  env: request.env,
  // The plugin this session loads: this repository.
  //
  // `Options.plugins` is declared at sdk.d.ts line 1860 as
  // `plugins?: SdkPluginConfig[]`, its doc comment at lines 1847 to 1859 says
  // "Load plugins for this session. Plugins provide custom commands, agents,
  // skills, and hooks" and "Currently only local plugins are supported via
  // the 'local' type", and `SdkPluginConfig` at lines 4696 to 4709 is
  // `{ type: 'local', path: string, skipMcpDiscovery?: boolean }`, `type`
  // being the literal `'local'` at line 4700 and `path` "Absolute or relative
  // path to the plugin directory" at line 4704. Research 13, quoting
  // code.claude.com/docs/en/agent-sdk/plugins as fetched 2026-08-30, gives
  // the same shape and adds that the path "should point to the plugin's root
  // directory: the parent of `skills/`, `agents/`, `hooks/`, `commands/`, or
  // `.claude-plugin/`". That parent is the repository root. Record 0033.
  plugins: [{ type: "local", path: request.pluginPath }],
  // No MCP server this application did not list.
  //
  // `Options.strictMcpConfig` is declared at sdk.d.ts line 2105, and its doc
  // comment at lines 2096 to 2104 says: "Only use MCP servers passed via the
  // `mcpServers` option (and servers declared by explicitly-passed agent
  // definitions in `agents`), ignoring all other MCP configurations: project
  // `.mcp.json`, user settings, plugins, and on-disk agent frontmatter, 
  // including subagent frontmatter MCP."
  //
  // This server passes no `mcpServers` and no `agents`, so the app's list is
  // empty and the session connects nothing. Record 0034 works through what
  // that sentence excludes, one clause at a time.
  strictMcpConfig: true,
  // Which settings files the session reads.
  //
  // Verified against @anthropic-ai/claude-agent-sdk 0.3.251, sdk.d.ts: the
  // doc comment at lines 2047 to 2055 says "Control which filesystem settings
  // to load", lists `'user'` (`~/.claude/settings.json`), `'project'`
  // (`.claude/settings.json`) and `'local'` (`.claude/settings.local.json`),
  // and states three facts this server depends on: "When omitted, all sources
  // are loaded (matches CLI defaults)", "Pass `[]` to disable filesystem
  // settings (SDK isolation mode)", and "Must include `'project'` to load
  // CLAUDE.md files". The option itself is line 2056, and `SettingSource` is
  // `'user' | 'project' | 'local'` at line 8032.
  //
  // A present key holding an empty array is not the same as an absent key,
  // and it is not the same as `settingSources: undefined` either, the doc
  // comment's "omitted" means the key is not there. So "inherited" spreads an
  // empty object rather than setting the key to anything. Records 0012 and
  // 0013.
  //
  // "app", the only value this version produces, names two of the three
  // members and leaves out `'user'`. `'user'` is `~/.claude/settings.json`:
  // the person's own layer, the one thing a closed configuration cannot read.
  // `'project'` and `'local'` are files that live beside the code the app
  // ships. Record 0032, which also says what `'project'` resolving relative
  // to `cwd` costs here.
  ...settingSourcesFor(request.settings),
};
}

// sdkStream, which calls query() with these options, follows.

// Lines 1 to 117 elided: the typedefs and the environment readers. Full file: server/src/config.js at tag module-30.


/**
* Where this platform keeps a desktop application's own data.
*
* Three platforms, three conventions, and each one has a documented environment
* variable that can be missing. The fallbacks are the conventional locations
* those variables name when they are set, so a missing variable produces the
* same directory rather than a failure:
*
*   Windows  %LOCALAPPDATA%, else <home>\AppData\Local
*   macOS    <home>/Library/Application Support
*   other    $XDG_DATA_HOME, else <home>/.local/share
*
* macOS reads no variable at all: `Library/Application Support` is a fixed path
* relative to the home directory, and there is no XDG-style override for it
* that the platform itself honours. A person who wants a different directory on
* any platform sets `WORKBENCH_APP_DATA`, which is checked before this function
* is called.
*
* @param {Record<string, string | undefined>} env
* @param {string} platform `process.platform`, taken as an argument so a test
*   can ask for a platform it is not running on.
* @param {string} home `os.homedir()`, likewise.
* @returns {string} The parent directory, not the app's directory.
*/
export function appDataRoot(env, platform, home) {
if (platform === "win32") {
  const local = env.LOCALAPPDATA;
  if (local !== undefined && local !== "") return local;
  return path.join(home, "AppData", "Local");
}
if (platform === "darwin") {
  return path.join(home, "Library", "Application Support");
}
const xdg = env.XDG_DATA_HOME;
if (xdg !== undefined && xdg !== "") return xdg;
return path.join(home, ".local", "share");
}

/**
* The environment the SDK subprocess is given.
*
* Two operations in one object literal, and the order is the whole point.
*
* The spread comes first because `Options.env` REPLACES the subprocess
* environment rather than merging with it. Verified against
* @anthropic-ai/claude-agent-sdk 0.3.251, sdk.d.ts lines 1504 to 1522: the doc
* comment says "When set, this value REPLACES the subprocess environment
* entirely, it is not merged with `process.env`. Spread `process.env` yourself
* if the subprocess still needs inherited variables like `PATH`, `HOME`, or
* `ANTHROPIC_API_KEY`", and the option is declared at line 1520 as
* `env?: { [envVar: string]: string | undefined }`. Without the spread the
* subprocess would start with no PATH, it could not find `node`, let alone a
* tool, and with no credentials.
*
* The pin comes second because a later key wins in an object literal. Whatever
* `CLAUDE_CONFIG_DIR` the person has exported, the app's value is the one the
* subprocess sees. Pinning first and spreading second would let the person's
* environment overwrite the pin, which is the failure this whole function
* exists to prevent, and it would look almost identical on the screen.
*
* @param {Config} config
* @param {Record<string, string | undefined>} [env] The environment to inherit.
* @returns {Record<string, string | undefined>}
*/
export function isolationEnv(config, env = process.env) {
return { ...env, CLAUDE_CONFIG_DIR: config.appDataDir };
}

// loadConfig, ensureWorkspace and ensureAppData follow; ensureAppData creates this directory at boot, so a permissions problem is a startup crash.

{
"name": "chat-workbench"
}