Repository navigation
docs(workspace-design): mark Memory env-var rename as shipped - #1444
Closed
qingyun-wu wants to merge 1 commit into
Closed
qingyun-wu wants to merge 1 commit into
qingyun-wu wants to merge 1 commit into
Conversation
…oposed The TL;DR table's "Memory" row described `$SUTANDO_PRIVATE_DIR` with a "proposed rename → SUTANDO_MEMORY_DIR" parenthetical. The rename actually shipped in #870 — `$SUTANDO_MEMORY_DIR` is the canonical name and `$SUTANDO_PRIVATE_DIR` is the legacy alias honored for one release. Owner flagged it 2026-06-04 03:06Z. One-line change. Other refs in the same doc (`$SUTANDO_PRIVATE_DIR` on L80/L87, `$SUTANDO_WORKSPACE`-as-env-override on L26/L61 — post-#1440 that env var is no longer honored either) left for a separate broader sweep if owner wants it; this commit honors the precise scope owner pointed at. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
qingyun-wu
added a commit
that referenced
this pull request
Jun 6, 2026
…orkspace, not a separate space Per owner directive 2026-06-04 closing PR #1444 (memory `project_workspace_only_no_memory`) + #1440 ratification: **Code + Workspace** are the only 2 top-level spaces. Memory is a sub-path under `<workspace>/.claude-sutando/projects/<slug>/memory/`. CLAUDE.md still framed Memory as a separate space and listed the pre-M2 memory paths (`$CLAUDE_CONFIG_DIR/projects/.../memory`) as default — both stale. This commit rewrites three sites: 1. **L54 — Workspace contract intro:** 3-space → 2-space framing. "Code + Workspace ... sync is a property of sub-paths, not a separate container." Memory listed alongside other workspace sub-paths. `$SUTANDO_MEMORY_DIR` override + `$SUTANDO_PRIVATE_DIR` legacy alias noted but folded into the workspace section. 2. **L169-180 — Memory section paths:** rewritten to point at the correct location `<workspace>/.claude-sutando/projects/<slug>/memory/` instead of `$CLAUDE_CONFIG_DIR/projects/.../memory`. The build_log path also corrected to `<workspace>/build_log.md`. 3. **L297-298 — Learn-from-demonstration save paths:** same correction. Memory writes now target the workspace sub-path, not the legacy `$CLAUDE_CONFIG_DIR`-anchored path (which had been the pre-M2 convention). Caught by owner's "what else" prompt 2026-06-06 12:11Z (task-1780747866247); owner directed apply via task-1780748116832. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One-line doc fix
TL;DR table in
docs/workspace-design.mddescribed the Memory space's env var as\$SUTANDO_PRIVATE_DIR (proposed rename → SUTANDO_MEMORY_DIR). The rename actually shipped in #870 —\$SUTANDO_MEMORY_DIRis canonical,\$SUTANDO_PRIVATE_DIRis the legacy alias honored for one release.Owner flagged the staleness 2026-06-04 03:06Z while reading the doc.
Scope kept tight
Honoring owner's "real pain only" directive (2026-06-04 03:02Z), this PR fixes only the precise line owner pointed at. There are ~8 other stale refs in the same doc —
\$SUTANDO_PRIVATE_DIRon L80 / L87 (similar rename staleness), and\$SUTANDO_WORKSPACE-as-env-override on L26 / L61 (post-#1440 the env is no longer honored either). Those are noted for a separate broader sweep PR if owner wants one; not auto-included here to avoid scope creep.Diff