Kognita.Index freshness
Git refresh and branch-aware indexing
Kognita's semantic layer is only useful when it follows the code. Git refresh keeps project repositories current, detects changed revisions, and refreshes the index for the branches and repositories your project is allowed to use.
What Kognita refreshes
A Kognita project can contain one repository or many repositories. During refresh, Kognita checks the git provider connection, sees which authorized repositories and branches have changed, and queues indexing work for code that needs a new semantic representation.
- Repository metadata, available branches, and latest commit revisions.
- Changed files and symbols that need to be re-read by the indexing pipeline.
- Project-level repository membership, so removed repositories stop contributing context.
- Index status shown in the project dashboard, including queued, indexing, indexed, or failed states.
How branch-aware indexing works
The index is tied to git state, not to a generic memory of the repository. When a tracked branch changes, the next refresh can rebuild the semantic chunks, relationships, and summaries for that branch. That lets an agent answer from the version of the system you connected rather than from stale code.
- Protected branches and selected repositories remain the source of truth for production-facing answers.
- New commits can trigger fresh indexing work so the semantic layer catches up after code lands.
- Multi-repo projects are refreshed as one system map, which keeps cross-service answers coherent.
- Access boundaries still come from the git provider and the Kognita project configuration.
What this means for MCP answers
Claude Code, Cursor, Codex, and other MCP clients query the index that belongs to the project. When git refresh and indexing have completed, the MCP can retrieve current files, functions, and relationships. If a repository is still queued or indexing, the dashboard status makes that visible before you rely on it.