Testing shows renaming a Git checkout doesn't change MemoraX's memory scope ID
Elegant-Chance-6420 · reddit · 2026-11-22
The author locally tested MemoraX Code v0.1.23's scope resolver to see whether renaming a Git checkout folder affects the project scope used for memory reads and writes.
- Setup: username demo, Git remote org-a/build.git, comparing the effectiveUserId field used in memory requests
- With the folder named build-checkout it returned demo@build; after renaming to review-copy (username and remote unchanged) it still returned demo@build
- Conclusion: for this checkout, changing the local folder name does not change the request scope ID
- Caveat: local resolver check only — live memory retrieval and existing agent sessions weren't tested
More from coding & agent
- Dev ditches SaaS for self-built AI tools; investor sees selective buying opportunity — craigbalding · 2026-11-22
- Charting the Singularity: a Claude-powered world model run on 60K+ prompts — MauiHawk · 2026-11-22
- LangChain's Harrison Chase: Companies Need a 'Knowledge Factory,' Not Better Models — hwchase17 · 2026-11-22
- Beyond AI Coding: Developers Should Move to the Five-Layer Agentic Engineering Stack — Pavan_Belagatti · 2026-11-22
- PSAISuite Pipes Native PowerShell Cmdlets Into Multi-Model Agent Harness — dfinke · 2026-11-22
- Lean 4 formalization of Masullo's Riemann proof hits 51%: 1213 of 2385 theorems proved — bremen79 · 2026-11-22