feat(v11.30.2): sync with Claude Code v2.1.193#70
Merged
Conversation
Track two new environment variables in the manifest and docs. No schema, hook, or wiring changes — these are opt-in/privacy vars, not set in the settings.json env block. Adopted: - OTEL_LOG_ASSISTANT_RESPONSES — logs the model's response text via the new claude_code.assistant_response OTEL event. Inherits OTEL_LOG_USER_PROMPTS when unset, so prompt-logging deployments start logging responses on upgrade; set =0 to keep prompts-only. - CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP — opt out of auto memory-pressure reaping of idle background shells. Deletions: - None.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Catches cc-settings up to Claude Code v2.1.193 by tracking two new environment variables. Nothing in cc-settings' behavior changes — these vars are opt-in (and one is privacy-relevant), so they're documented and added to the drift manifest but deliberately not set in the installed
settings.json. The one worth knowing about: if your OTEL setup already logs user prompts, v2.1.193 will start logging assistant responses too unless you setOTEL_LOG_ASSISTANT_RESPONSES=0.Summary
OTEL_LOG_ASSISTANT_RESPONSES(v2.1.193) → manifestknownEnvVars+ docs env table. Gates response text on the newclaude_code.assistant_responseOTEL event; inheritsOTEL_LOG_USER_PROMPTSwhen unset.CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP(v2.1.193) → manifestknownEnvVars+ docs env table. Opt-out for auto memory-pressure reaping of idle background shells.lastScan2026-06-26); version → 11.30.2 insrc/setup.ts+plugin.json; CHANGELOG entry added.autoMode.classifyAllShellneeds no change — the schema'sautoMode: z.looseObject({})already accepts it. All other v2.1.193 entries are native client UX / bug fixes with no cc-settings surface.Test Plan
bun run typecheck— cleanbun test— 636 pass, 0 failbun run upstream:scan— no drift detectedbun run compose— confirmed env vars are tracking-only (not in settings.json env block)