Skip to content
This repository was archived by the owner on Jul 16, 2026. It is now read-only.

fix(health-check): derive memory-dir slug from workspace path, not repo path - #91

Open
jgluck96 wants to merge 1 commit into
mainfrom
fix/health-check-memory-dir-slug-v2
Open

jgluck96 wants to merge 1 commit into
mainfrom
fix/health-check-memory-dir-slug-v2

Conversation

@jgluck96

@jgluck96 jgluck96 commented Jun 3, 2026

Copy link
Copy Markdown

Summary

  • _default_memory_dir() was slugifying the repo root path (~/Development/core-prod/stando) but Claude Code keys memory to the session's working directory (the workspace root ~/.sutando/workspace/)
  • Result: health-check reported "1 .md files" (wrong dir) instead of the actual memory dir contents
  • Fix: slugify SUTANDO_WORKSPACE (or ~/.sutando/workspace/) and also replace . → - to match Claude's slugification

Test plan

  • Run python3 src/health-check.py — memory-dir row should show correct file count
  • Verify with SUTANDO_MEMORY_DIR override — explicit override still takes precedence

🤖 Generated with Claude Code

…po path

Claude Code keys project memory to the session's CWD. For Sutando that's
the workspace root (~/.sutando/workspace/ by default), not the repo. The
previous slug only replaced '/' but Claude slugifies by replacing both '/'
and '.' with '-', so the health check was pointing at the wrong directory
(-Users-...-Development-core-prod-stando vs -Users-...--sutando-workspace)
and always reporting 1 .md file instead of the actual memory file count.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

@bassilkhilo-ag2 bassilkhilo-ag2 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix is correct. Verified: resolve_workspace() → /Users/bassilkhilo/.sutando/workspace → slug -Users-bassilkhilo--sutando-workspace → matches the actual memory dir. The repo-path anti-pattern is exactly what the workspace contract warns against. Clean fix.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants