Skip to content

fix: use project-relative memory path in orchestrator-engineer agent#5

Open
xiaolai wants to merge 1 commit into
LukeRenton:mainfrom
xiaolai:fix/nlpm-hardcoded-memory-path
Open

fix: use project-relative memory path in orchestrator-engineer agent#5
xiaolai wants to merge 1 commit into
LukeRenton:mainfrom
xiaolai:fix/nlpm-hardcoded-memory-path

Conversation

@xiaolai

@xiaolai xiaolai commented Jul 7, 2026

Copy link
Copy Markdown

Automated: drive-by fix from NLPM, an NL artifact linter. Reviewed and reproduced before submission.

Bug: The agent's persistent-memory directory is hardcoded to the original author's personal Windows path (C:\Users\luker\Documents\Teaching Claude Code\.claude\agent-memory\orchestrator-engineer\) in a file whose own text says memory is "shared with your team via version control".

Evidence: .claude/agents/engineers/orchestrator-engineer.md line 89 contains the literal absolute path, which does not exist on any machine other than the original author's, or on non-Windows systems.

Fix: Replace the hardcoded absolute path with the project-relative .claude/agent-memory/orchestrator-engineer/, so the memory system works for every contributor regardless of OS or clone location.

The persistent-memory directory was hardcoded to the original author's
personal Windows path (C:\Users\luker\...), which does not exist on any
other contributor's machine or OS, silently breaking the agent's memory
system for everyone else.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 7, 2026

Copy link
Copy Markdown

@xiaolai is attempting to deploy a commit to the lukerenton's projects Team on Vercel.

A member of the Team first needs to authorize it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant