feat(mcp): implement persistent codebase status and info retrieval from file#217
Open
IvanM9 wants to merge 1 commit intozilliztech:masterfrom
Open
feat(mcp): implement persistent codebase status and info retrieval from file#217IvanM9 wants to merge 1 commit intozilliztech:masterfrom
IvanM9 wants to merge 1 commit intozilliztech:masterfrom
Conversation
…om file - add file-based persistence for codebase status and information - support both v1 and v2 snapshot formats for backward compatibility - fallback to memory if file reading fails - improve error handling and logging for snapshot operations
ayaka209
added a commit
to ayaka209/claude-context
that referenced
this pull request
Sep 27, 2025
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
1 participant
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.
This pull request improves the reliability and consistency of codebase status and information retrieval in the
SnapshotManagerclass by reading from the persisted JSON snapshot file instead of relying solely on in-memory data. The changes also add compatibility for both v1 and v2 snapshot formats and introduce robust error handling.Persistence and consistency improvements:
getCodebaseStatusto read codebase status from the JSON snapshot file, ensuring results reflect the persisted state and supporting both v1 and v2 formats. If file reading fails, it falls back to in-memory data.getCodebaseInfoto retrieve complete codebase information from the JSON snapshot file, constructing results for v1 format and supporting v2 format directly. Falls back to in-memory data on error.Backward compatibility and error handling: