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
This release introduces a major upgrade to the embedding architecture and critical stability fixes. We have transitioned to a more powerful embedding model (bge-m3 family) and increased the context window to 1024 tokens, significantly improving semantic search accuracy for larger code blocks.
Key changes include:
Upgraded Embedding Engine: Switched model architecture and increased capacity to 1024 tokens for deeper code understanding and better retrieval of complex functions.
Production Stability: Fixed critical race conditions during background indexing and model migration.
Intelligent Installer: Enhanced the installer to auto-detect environment configurations and handle updates more robustly (Zero-Config).
Resilience: Improved error recovery for long-running worker processes.
# This file is automatically managed by RagCode MCP.
3
+
4
+
## ⚖️ The Golden Rule
5
+
**For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
6
+
7
+
## Available Tools
8
+
- search_code: Primary entry point for semantic search.
9
+
- get_function_details: Get full implementation of a function.
10
+
- find_type_definition: Get struct/interface definitions.
11
+
- list_package_exports: See what a module offers.
12
+
- search_docs: Find project documentation.
13
+
14
+
## Usage Guidelines
15
+
- Always provide 'file_path' to tools to ensure they detect the correct project context.
16
+
- Use 'hybrid_search' if looking for exact variable names or error messages.
17
+
- If the tool says "workspace not indexed", use 'index_workspace' once.
# This file is automatically managed by RagCode MCP.
3
+
4
+
## ⚖️ The Golden Rule
5
+
**For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
6
+
7
+
## Available Tools
8
+
- search_code: Primary entry point for semantic search.
9
+
- get_function_details: Get full implementation of a function.
10
+
- find_type_definition: Get struct/interface definitions.
11
+
- list_package_exports: See what a module offers.
12
+
- search_docs: Find project documentation.
13
+
14
+
## Usage Guidelines
15
+
- Always provide 'file_path' to tools to ensure they detect the correct project context.
16
+
- Use 'hybrid_search' if looking for exact variable names or error messages.
17
+
- If the tool says "workspace not indexed", use 'index_workspace' once.
**For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
5
+
6
+
## Project Overview
7
+
RagCode is a Model Context Protocol (MCP) server that provides semantic code search (RAG) for local codebases using Ollama (embeddings) and Qdrant (vector storage). It supports multiple languages through a pluggable analyzer architecture.
8
+
9
+
## Architecture & Patterns
10
+
-**Core Components**:
11
+
-`Indexer`: Orchestrates analysis, embedding, and storage.
12
+
-`PathAnalyzer`: Interface for language-specific AST analysis (Go, PHP/Laravel, Python, HTML).
13
+
-`CodeChunk`: The canonical v2 data structure for all indexed code symbols (functions, types, files).
14
+
-`Workspace.Manager`: Handles multi-workspace multi-language isolation via language-specific Qdrant collections.
-**Convention**: The project is migrating from `APIChunk` to `CodeChunk`. Always use `CodeChunk` for new features.
17
+
18
+
## Developer Workflows
19
+
-**Build/Install**: Use `go run ./cmd/install/main.go` to build binaries and configure local IDEs.
20
+
-**Runtime Binaries**: Installed to `~/.local/share/ragcode/bin/` by default.
21
+
-**Testing**: Use standard `go test ./...`. Use `t.TempDir()` for workspace/filesystem isolation.
22
+
-**Logging**: MCP server logs to `mcp.log` next to the executable. Check `MCP_LOG_LEVEL=debug` for issues.
23
+
24
+
## MCP Tools Usage
25
+
-`search_code`: Use as the primary entry point for exploration. **Crucial**: Always provide the `file_path` parameter as it's used for workspace and language detection.
26
+
-`index_workspace`: Triggered automatically on first query per workspace, but can be manually invoked for major changes.
27
+
28
+
## Integration Points
29
+
-**Ollama**: Requires `phi3:medium` (reasoning) and `mxbai-embed-large` (embeddings) by default.
30
+
-**Qdrant**: Runs in Docker as `ragcode-qdrant` on port 6333.
31
+
32
+
## Romania/Hungarian Support (Note)
33
+
The project identifies as `rag-code-mcp`. Old configurations naming it `do-ai` or `coderag` are deprecated and paths must be updated to the new project structure in `github.com/doITmagic/rag-code-mcp`.
# This file is automatically managed by RagCode MCP.
3
+
4
+
## ⚖️ The Golden Rule
5
+
**For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
6
+
7
+
## Available Tools
8
+
- search_code: Primary entry point for semantic search.
9
+
- get_function_details: Get full implementation of a function.
10
+
- find_type_definition: Get struct/interface definitions.
11
+
- list_package_exports: See what a module offers.
12
+
- search_docs: Find project documentation.
13
+
14
+
## Usage Guidelines
15
+
- Always provide 'file_path' to tools to ensure they detect the correct project context.
16
+
- Use 'hybrid_search' if looking for exact variable names or error messages.
17
+
- If the tool says "workspace not indexed", use 'index_workspace' once.
Copy file name to clipboardExpand all lines: README.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,11 @@ RagCode is a **Model Context Protocol (MCP) server** that instantly makes your p
23
23
24
24
Built with the official [Model Context Protocol Go SDK](https://github.com/modelcontextprotocol/go-sdk), RagCode provides **9 powerful tools** to index, search, and analyze code, making it the ultimate solution for **AI-ready software development**.
25
25
26
+
## ⚖️ The Golden Rule
27
+
> **"FOR ANY INFORMATION ABOUT YOUR CODE (location, structure, logic, or usage), YOU MUST USE RAGCODE MCP TOOLS."**
28
+
>
29
+
> *By using semantic search instead of simple keyword lookups, your AI assistant gains true context, avoiding hallucinations and missing details even in massive legacy mono-repos.*
0 commit comments