You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(code-index): support indexing multiple repositories in a single namespace #870
Reviewer on #721 asked "Can or should we support multiple code bases in the index?" Today, the code_index tool mixin (composed into CodeAgent) is scoped to a single repo_path per instance and stores a single on-disk FAISS index.
Goal
Allow one collection to cover N repos with a repo_id field per chunk so search can scope by repo or span all.
Design sketch
On-disk layout: ~/.gaia/code_index/<collection_name>/{faiss.idx,meta.jsonl} with repos keyed by git remote.
CLI: gaia-code index --repo /path/a --collection team-codebases, then gaia-code index --repo /path/b --collection team-codebases appends to the same collection.
Search: gaia-code index search "..." --repo-id <remote> filters; omitting the flag searches all repos in the collection.
Acceptance
Multi-repo index builds and searches pass unit tests.
Activity
feat(code-index): address review — fold into CodeAgent, drop git/PR s…
feat(code-index): semantic code search via CodeAgent mixin and gaia-c…