Skip to content

Bug: preexisting-host-identity-leaks-in-agent-memory-files #685

Description

@drmoisan
  • Work Mode: full-bug

Summary

Several .claude/agent-memory/** files already committed to main (from unrelated, prior features/issues) contain a real account name and/or machine name in plain text, violating this repo's no-absolute-host-paths policy (.claude/agent-memory/_shared_no_absolute_host_paths.md).

Environment

  • OS/version: Windows, agent-memory files under .claude/agent-memory/**
  • Command/flags used: git grep -lia "<account>\|<machine>" -- .claude/agent-memory/
  • Data source or fixture: N/A

Steps to Reproduce

  1. Run a case-insensitive content grep for the real account name and machine name across .claude/agent-memory/** on main.
  2. Observe multiple hits in files unrelated to the current branch's work.

Expected Behavior

No committed artifact, including agent-memory files, should contain a real account or machine name - per the repo's own stated policy.

Actual Behavior

At least 7 pre-existing agent-memory files on main currently contain the real account name and/or machine name in plain text:

  • .claude/agent-memory/atomic-executor/project_bash_heredoc_collapses_doubled_backslashes.md (introduced by a feature-review commit, unrelated to Bug: quickfiler-search-box-loses-focus-on-dropdown-expand #680)
  • .claude/agent-memory/epic-orchestrator/feedback_measure_whole_volume_before_blaming_worktrees.md
  • .claude/agent-memory/feature-review/project_464-review-residuals.md
  • .claude/agent-memory/feature-review/project_488-review-residuals.md
  • .claude/agent-memory/orchestrator/angle-bracket-redaction-breaks-trx-xml.md
  • .claude/agent-memory/orchestrator/bash-tool-collapses-double-backslash-in-sed.md
  • .claude/agent-memory/orchestrator/collect-pr-context-lands-in-main-checkout.md

All seven pre-date the branch that discovered them (issue #680) and were introduced by unrelated prior commits (issues #464, #488, #445, and various epic fan-in/orchestrator commits), so fixing them is out of scope for that branch's PR.

Logs / Screenshots

Impact / Severity

  • Blocker
  • High
  • Low

Source

From: docs/features/potential/2026-08-28-preexisting-host-identity-leaks-in-agent-memory-files.md

Activity

  1. drmoisan commented on Sep 2, 2026

    @drmoisan
    OwnerAuthor

    Superseded by consolidated issue #728, which tracks this finding along with 1 related one sharing the same blast radius (plain-text committed identity leakage). See #728 for detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions