fix(github): persist GitHub indexer data between CLI invocations #37
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.
Fixes #36
Problem
The GitHub indexer was using in-memory storage (
Map), causing indexed data to be lost between CLI command invocations. Users had to re-index before every search, breaking the dogfooding workflow.Solution
Migrated GitHub indexer to use persistent storage:
.dev-agent/github-state.jsonsinceparameter (future enhancement)Changes
Core Indexer (
packages/subagents/src/github/indexer.ts)isStale()check for auto-updatesinitialize()andclose()lifecycle methodsConfiguration (
packages/subagents/src/github/types.ts)GitHubIndexerConfiginterfaceGitHubIndexerStateinterface for persistenceAgent (
packages/subagents/src/github/agent.ts)GitHubAgentConfigto pass vector storage pathsRepositoryIndexer(was unused)initialize()during agent startupCLI (
packages/cli/src/commands/gh.ts).vectors-github)Tests
indexer.test.ts)Verification
State file created:
Impact