feat: support .engram-project file for project name override#63
Open
angel-r wants to merge 1 commit intoGentleman-Programming:mainfrom
Open
feat: support .engram-project file for project name override#63angel-r wants to merge 1 commit intoGentleman-Programming:mainfrom
angel-r wants to merge 1 commit intoGentleman-Programming:mainfrom
Conversation
When a .engram-project file exists in the project root, its content is used as the project name instead of deriving it from basename. This fixes project name mismatches in monorepo setups where the directory name differs from the desired engram project name (e.g. gymfever.poolcomapi → poolcomapi). Closes Gentleman-Programming#62
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
2 participants
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.
Summary
.engram-projectfile support to override auto-detected project namesbasenamebehavior when the file doesn't exist (no breaking change)Motivation
Closes #62
In monorepo setups,
basenameproduces names that don't match the desired engram project name. For example, a directorymyorg.backend-apigets project namemyorg.backend-apiinstead ofbackend-api. This causes duplicate projects when MCP tools (which accept an explicitprojectparam) and hooks (which usebasename) save to different project names.Usage:
Changes
plugin/claude-code/scripts/session-start.sh— check for.engram-projectbefore falling back tobasenameplugin/claude-code/scripts/subagent-stop.sh— sameplugin/claude-code/scripts/post-compaction.sh— sameplugin/opencode/engram.ts—extractProjectName()reads.engram-projectif it existsTest plan
go test ./...— all pre-existing tests pass (failures in store/sync/setup are pre-existing Windows file-locking issues, unrelated to this change).engram-projectwith contentbackend-apiin amyorg.backend-apidirectory, verified hooks resolve the correct project name