Skip to content

fix: keep project memory paths within the project - #143

Open
lorenzozanee wants to merge 1 commit into
CyberStrikeus:devfrom
lorenzozanee:fix/project-memory-path
Open

fix: keep project memory paths within the project#143
lorenzozanee wants to merge 1 commit into
CyberStrikeus:devfrom
lorenzozanee:fix/project-memory-path

Conversation

@lorenzozanee

Copy link
Copy Markdown

What does this PR do?

Fixes #132 by keeping memory files inside the active project when a non-Git project uses / as its worktree sentinel.

Type of change

  • Bug fix
  • New feature / agent
  • Security tool / MCP server / Bolt plugin
  • Agent skill / knowledge base
  • UI / TUI improvement
  • Documentation
  • Refactor / performance
  • CI / infrastructure

Security impact

  • This PR adds or modifies tool execution (shell, file, network)
  • This PR changes agent permissions or scope
  • This PR modifies authentication / authorization logic
  • This PR has no security impact

How did you verify it works?

The regression test writes daily and long-term memory through a real non-Git project and verifies both files are created under that project.

Checklist

  • bun turbo typecheck passes
  • Tested locally with at least one LLM provider
  • PR is focused on a single change
  • No secrets, credentials, or API keys in the diff
  • Breaking changes are documented (if any)

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

  1. Open an issue describing the bug/feature (if one doesn't exist)
  2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant