Core indexing engine for Code Context
npm install @zilliz/code-context-coreThe core indexing engine for Code Context - a powerful tool for semantic search and analysis of codebases using vector embeddings and AI.


> 📖 New to Code Context? Check out the main project README for an overview and quick start guide.
``bash`
npm install @zilliz/code-context-core
bash
OPENAI_API_KEY=your-openai-api-key
`#### Zilliz Cloud configuration
Get a free Milvus vector database on Zilliz Cloud.
Code Context needs a vector database. You can sign up on Zilliz Cloud to get a free Serverless cluster.

After creating your cluster, open your Zilliz Cloud console and copy both the public endpoint and your API key.
These will be used as
your-zilliz-cloud-public-endpoint and your-zilliz-cloud-api-key in the configuration examples.Keep both values handy for the configuration steps below.
If you need help creating your free vector database or finding these values, see the Zilliz Cloud documentation for detailed instructions.
`bash
MILVUS_ADDRESS=your-zilliz-cloud-public-endpoint
MILVUS_TOKEN=your-zilliz-cloud-api-key
` > 💡 Tip: For easier configuration management across different usage scenarios, consider using global environment variables.
Quick Start
`typescript
import {
CodeContext,
OpenAIEmbedding,
MilvusVectorDatabase
} from '@zilliz/code-context-core';// Initialize embedding provider
const embedding = new OpenAIEmbedding({
apiKey: process.env.OPENAI_API_KEY || 'your-openai-api-key',
model: 'text-embedding-3-small'
});
// Initialize vector database
const vectorDatabase = new MilvusVectorDatabase({
address: process.env.MILVUS_ADDRESS || 'localhost:19530',
token: process.env.MILVUS_TOKEN || ''
});
// Create context instance
const context = new CodeContext({
embedding,
vectorDatabase
});
// Index a codebase
const stats = await context.indexCodebase('./my-project', (progress) => {
console.log(
${progress.phase} - ${progress.percentage}%);
});console.log(
Indexed ${stats.indexedFiles} files with ${stats.totalChunks} chunks);// Search the codebase
const results = await context.semanticSearch(
'./my-project',
'function that handles user authentication',
5
);
results.forEach(result => {
console.log(
${result.relativePath}:${result.startLine}-${result.endLine});
console.log(Score: ${result.score});
console.log(result.content);
});
`Features
- Multi-language Support: Index TypeScript, JavaScript, Python, Java, C++, and many other programming languages
- Semantic Search: Find code using natural language queries powered by AI embeddings
- Flexible Architecture: Pluggable embedding providers and vector databases
- Smart Chunking: Intelligent code splitting that preserves context and structure
- Batch Processing: Efficient processing of large codebases with progress tracking
- Pattern Matching: Built-in ignore patterns for common build artifacts and dependencies
- Incremental File Synchronization: Efficient change detection using Merkle trees to only re-index modified files
Embedding Providers
- OpenAI Embeddings (
text-embedding-3-small, text-embedding-3-large)
- VoyageAI Embeddings - High-quality embeddings optimized for codeVector Database Support
- Milvus/Zilliz Cloud - High-performance vector database
Code Splitters
- AST Code Splitter - AST-based code splitting with automatic fallback (default)
- LangChain Code Splitter - Character-based code chunking
Configuration
$3
`typescript
interface CodeContextConfig {
embedding?: Embedding; // Embedding provider
vectorDatabase?: VectorDatabase; // Vector database instance (required)
codeSplitter?: Splitter; // Code splitting strategy
supportedExtensions?: string[]; // File extensions to index
ignorePatterns?: string[]; // Patterns to ignore
}
`$3
`typescript
[
// Programming languages
'.ts', '.tsx', '.js', '.jsx', '.py', '.java', '.cpp', '.c', '.h', '.hpp',
'.cs', '.go', '.rs', '.php', '.rb', '.swift', '.kt', '.scala', '.m', '.mm',
// Text and markup files
'.md', '.markdown'
]
`$3
-
node_modules/, dist/, build/, out/
- .git/, .vscode/, .idea/**
- .min.js, .bundle.js, *.map
- Log files, cache directories, and temporary filesAPI Reference
$3
#### Methods
-
indexCodebase(path, progressCallback?) - Index an entire codebase
- semanticSearch(path, query, topK?, threshold?) - Search indexed code semantically
- hasIndex(path) - Check if codebase is already indexed
- clearIndex(path, progressCallback?) - Remove index for a codebase
- updateIgnorePatterns(patterns) - Update ignore patterns
- updateEmbedding(embedding) - Switch embedding provider
- updateVectorDatabase(vectorDB) - Switch vector database$3
`typescript
interface SemanticSearchResult {
content: string; // Code content
relativePath: string; // File path relative to codebase root
startLine: number; // Starting line number
endLine: number; // Ending line number
language: string; // Programming language
score: number; // Similarity score (0-1)
fileExtension: string; // File extension
}
`
Examples
$3
`typescript
import { CodeContext, MilvusVectorDatabase, VoyageAIEmbedding } from '@zilliz/code-context-core';// Initialize with VoyageAI embedding provider
const embedding = new VoyageAIEmbedding({
apiKey: process.env.VOYAGEAI_API_KEY || 'your-voyageai-api-key',
model: 'voyage-code-3'
});
const vectorDatabase = new MilvusVectorDatabase({
address: process.env.MILVUS_ADDRESS || 'localhost:19530',
token: process.env.MILVUS_TOKEN || ''
});
const context = new CodeContext({
embedding,
vectorDatabase
});
`$3
`typescript
const context = new CodeContext({
embedding,
vectorDatabase,
supportedExtensions: ['.ts', '.js', '.py', '.java'],
ignorePatterns: [
'node_modules/**',
'dist/**',
'*.spec.ts',
'*.test.js'
]
});
`File Synchronization Architecture
Code Context implements an intelligent file synchronization system that efficiently tracks and processes only the files that have changed since the last indexing operation. This dramatically improves performance when working with large codebases.
!File Synchronization Architecture
$3
The file synchronization system uses a Merkle tree-based approach combined with SHA-256 file hashing to detect changes:
#### 1. File Hashing
- Each file in the codebase is hashed using SHA-256
- File hashes are computed based on file content, not metadata
- Hashes are stored with relative file paths for consistency across different environments
#### 2. Merkle Tree Construction
- All file hashes are organized into a Merkle tree structure
- The tree provides a single root hash that represents the entire codebase state
- Any change to any file will cause the root hash to change
#### 3. Snapshot Management
- File synchronization state is persisted to
~/.code-context/merkle/` directory#### 4. Change Detection Process
1. Quick Check: Compare current Merkle root hash with stored snapshot
2. Detailed Analysis: If root hashes differ, perform file-by-file comparison
3. Change Classification: Categorize changes into three types:
- Added: New files that didn't exist before
- Modified: Existing files with changed content
- Removed: Files that were deleted from the codebase
#### 5. Incremental Updates
- Only process files that have actually changed
- Update vector database entries only for modified chunks
- Remove entries for deleted files
- Add entries for new files
This package is part of the CodeContext monorepo. Please see:
- Main Contributing Guide - General contribution guidelines
- Core Package Contributing - Specific development guide for this package
- @code-context/mcp - MCP server that uses this core engine
- VSCode Extension - VSCode extension built on this core
MIT - See LICENSE for details