gemini-cli - 💡(How to fix) Fix Add deterministic redaction and reduce Auto Memory logging [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#26525Fetched 2026-05-06 06:35:44
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Timeline (top)
labeled ×3commented ×1cross-referenced ×1parent_issue_added ×1

Fix Action

Fix / Workaround

  • Secrets or sensitive local details present in transcripts may be sent to the model before deterministic redaction happens.
  • Debug logs may contain memory content, pending patch contents, absolute paths, or sensitive workflow details.
  • The current user-facing setting description does not clearly state that Auto Memory performs model calls over local transcript content.

Auto Memory should scrub sensitive content before model submission and avoid logging full memory or patch content by default.

  • Add deterministic pre-model secret scrubbing for transcript excerpts, session summaries, workflow hints, and pending inbox content.
  • Avoid logging full memory or patch content by default.
  • Keep enough diagnostic information for debugging without dumping sensitive content.
  • Update settings/docs to clearly explain that Auto Memory uses model calls over local transcript content.
  • Tests cover common secret patterns in session summaries, workflow hints, and pending patch content.
RAW_BUFFERClick to expand / collapse

Problem

Auto Memory reads local transcripts and sends selected transcript content to the model used by the background extraction agent. The extraction prompt instructs the model to redact secrets, but that happens after content is already in model context. The service can also log existing skills and pending inbox content.

Relevant code:

  • packages/core/src/agents/skill-extraction-agent.ts
  • packages/core/src/services/memoryService.ts

Impact

  • Secrets or sensitive local details present in transcripts may be sent to the model before deterministic redaction happens.
  • Debug logs may contain memory content, pending patch contents, absolute paths, or sensitive workflow details.
  • The current user-facing setting description does not clearly state that Auto Memory performs model calls over local transcript content.

Expected Behavior

Auto Memory should scrub sensitive content before model submission and avoid logging full memory or patch content by default.

Acceptance Criteria

  • Add deterministic pre-model secret scrubbing for transcript excerpts, session summaries, workflow hints, and pending inbox content.
  • Avoid logging full memory or patch content by default.
  • Keep enough diagnostic information for debugging without dumping sensitive content.
  • Update settings/docs to clearly explain that Auto Memory uses model calls over local transcript content.
  • Tests cover common secret patterns in session summaries, workflow hints, and pending patch content.

Notes

This does not require changing the review-first inbox model. It tightens the privacy boundary before extraction prompts are assembled and before debug logs are emitted.

extent analysis

TL;DR

Implement deterministic pre-model secret scrubbing for sensitive content in Auto Memory to prevent secrets from being sent to the model before redaction.

Guidance

  • Review the memoryService.ts and skill-extraction-agent.ts files to identify areas where sensitive content is being sent to the model without scrubbing.
  • Add secret scrubbing mechanisms for transcript excerpts, session summaries, workflow hints, and pending inbox content before they are submitted to the model.
  • Update logging to avoid dumping full memory or patch content by default, while keeping enough diagnostic information for debugging.
  • Consider implementing tests to cover common secret patterns in session summaries, workflow hints, and pending patch content.

Example

No specific code example can be provided without modifying the existing codebase, but the memoryService.ts file likely contains functions that can be modified to scrub sensitive content before sending it to the model.

Notes

The provided information does not specify the exact implementation details of the secret scrubbing mechanism, so the approach may vary depending on the specific requirements and constraints of the project.

Recommendation

Apply workaround by implementing deterministic pre-model secret scrubbing, as this will directly address the issue of sensitive content being sent to the model before redaction.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix Add deterministic redaction and reduce Auto Memory logging [1 comments, 2 participants]