[Bug]: Claude launch args --settings is silently replaced by T3's own SDK settings #15073

Activity

1. juliusmarminge commented on Oct 22, 2026

   

   juliusmarminge

   on Oct 22, 2026 – with GitCafe Production

   Member

   More actions

   Reviewed current main b5a226e49c. The launch settings flag still remains in extraArgs while makeClaudeQueryOptions supplies SDK settings. No matching duplicate among 947 open issues; #13934 and #7577 concern different flags.

   This is an ordinary bug report, not a reported exploitable vulnerability. A general settings-merge fix also changes effective permissions.allow, permissions.deny, and bypass restrictions; those settings need maintainer review alongside resolveBypassAvailability. Routing to Julius under the triage fix-scope restriction. No implementation changes or real-app reproduction were performed; the issue remains open.
2. pgilad-rna commented on Oct 25, 2026

   

   pgilad-rna

   on Oct 25, 2026

   More actions

   Related gap that #22864 does not cover: Claude text generation ignores launch arguments completely.

   ClaudeTextGeneration (thread titles, branch names, commit messages, PR descriptions) builds its own argv from binaryPath plus its own --settings JSON, and never reads launchArgs: ClaudeTextGeneration.ts#L196-L208. #22864 changes only ClaudeAdapterV2.ts. So after it ships, an instance with --settings '{"env":{"ANTHROPIC_VERTEX_PROJECT_ID":"..."}}' in its launch arguments runs its turns on that project, but its titles, branch names and commit messages still go to the project in ~/.claude/settings.json.

   The instance's Environment variables do not help here either. Claude Code applies the env block of ~/.claude/settings.json over the process environment, as the comment at ClaudeAdapterV2.ts#L1334 already says. For a key that the user's settings.json also sets, --settings is the only per-instance way in, and text generation drops it.

   Found by reading main at 375da0f; v0.1.2 has the same code. Suggested fix: read the --settings launch argument in ClaudeTextGeneration the same way #22864 does, and merge it beneath T3's own text-generation keys (disableAllHooks, thinking, fast mode).

   Workaround that covers both paths today: set the instance's Binary path to a wrapper that merges your keys into the --settings value T3 passes, then runs claude. Both paths use the Binary path. Putting your own --settings in front of the arguments does not work: the CLI keeps only the last --settings, and T3's comes later.

   Wrapper sketch (inline JSON only)

   #!/usr/bin/env bash
   set -euo pipefail
   patch='{"env":{"ANTHROPIC_VERTEX_PROJECT_ID":"your-project"}}'
   args=()
   merged=0
   while (($# > 0)); do
       case "$1" in
           --settings)
               args+=(--settings "$(jq -c --argjson p "${patch}" '. * $p' <<<"$2")")
               merged=1
               shift 2
               ;;
           *)
               args+=("$1")
               shift
               ;;
       esac
   done
   ((merged)) || args=(--settings "${patch}" ${args[@]+"${args[@]}"})
   exec claude ${args[@]+"${args[@]}"}

   Commented by claude-opus-5-5 on behalf of @pgilad-rna
3. t3dotgg

   added 2 commits that reference this issue on Oct 25, 2026

   fix(server): Claude --settings launch args merge with T3's settings i…

   ...

   This issue will close once commit 5f52390 is merged into the 'main' branch.

   5f52390

   fix(server): Claude --settings launch args merge with T3's settings i…

   ...

   This issue will close once commit 2849d56 is merged into the 'main' branch.

   2849d56
4. t3dotgg

   closed this as completedin #22864on Oct 27, 2026
5. avillagran

   added a commit that references this issue on Oct 29, 2026

   fix(server): Claude --settings launch args merge with T3's settings i…

   ...

   This issue will close once commit 302d9e5 is merged into the 'main' branch.

   302d9e5