Skip to content

fix: nested branches, session providers, and stale cwd state - #6

Merged
Whamp merged 1 commit into
mainfrom
fix/known-limits
Aug 18, 2026
Merged

fix: nested branches, session providers, and stale cwd state#6
Whamp merged 1 commit into
mainfrom
fix/known-limits

Conversation

@Whamp

@Whamp Whamp commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • Allow git-style memory branch names (feat/auth) while still blocking path escape (../, \, ., .., empty segments). Existing nested dirs are listed again; no rename migration.
  • Forward session extensions into the isolated committer (--no-extensions plus --extension for pi -e, settings.json, and Pi's standard extension directories), skipping this package so Brain cannot reload onto the log it is distilling. committer.extensions still replaces that list when set.
  • Drop in-memory Brain objects and clear the footer when cwd moves to a project with no .memory/.

Providers installed only as Pi packages (pi install npm:some-provider) are still not auto-forwarded; those need committer.extensions or an -e / extensions-directory install.

Test plan

  • pnpm run check in .worktrees/known-limits (226 tests)
  • Create memory_branch with name: feat/auth, confirm files land under .memory/branches/feat/auth/ and ../escape still fails
  • memory_commit with a custom provider loaded via pi -e / ~/.pi/agent/extensions and no committer.extensions in config
  • Mid-session cwd change into a repo without .memory/: footer clears, previous project's log.md is unchanged

Made with Cursor

Keep git-style names like feat/auth inside .memory/branches, forward
session extensions except Brain into the isolated committer, and drop
in-memory Brain objects when cwd moves to an uninitialized project.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Whamp
Whamp merged commit 6e1cac1 into main Aug 18, 2026
2 of 3 checks passed
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