Skip to content

fix: hardcode user_id, disallow user override - #7

Open
HQidea wants to merge 1 commit into
mainfrom
claude/stoic-mclaren-6a7815
Open

fix: hardcode user_id, disallow user override#7
HQidea wants to merge 1 commit into
mainfrom
claude/stoic-mclaren-6a7815

Conversation

@HQidea

@HQidea HQidea commented May 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Hardcode user_id to "default" across the entire plugin, aligning with the memorylake-openclaw pattern
  • Remove MEMORYLAKE_USER_ID environment variable support from all config sources (env vars, memorylake.json, runtime kwargs)
  • user_id is now set after the memorylake.json overlay merge, ensuring no override path exists

Changed files

  • src/memorylake_hermes/__init__.py — hardcode self._user_id = "default", remove docstring reference
  • src/memorylake_hermes/get_config.py — remove env var read, hardcode after overlay
  • src/memorylake_hermes/skills/memorylake/*/scripts/get_config.py (×3) — same pattern
  • README.md — remove MEMORYLAKE_USER_ID from env var table

Test plan

  • Verify MEMORYLAKE_USER_ID env var is ignored when set
  • Verify user_id in memorylake.json is overridden to "default"
  • Verify plugin initializes with user_id = "default" in logs
  • Verify all memory API calls use "default" as user_id

🤖 Generated with Claude Code

Align with memorylake-openclaw pattern — user_id is no longer
configurable via MEMORYLAKE_USER_ID env var, memorylake.json,
or runtime kwargs. It is always set to "default" after config
loading to prevent any override path.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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