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
In this tutorial, we will build codebase index. [CocoIndex](https://github.com/cocoindex-io/cocoindex) provides built-in support for codebase chunking, with native Tree-sitter support. It works with large codebases, and can be updated in near real-time with incremental processing - only reprocess what's changed.
19
20
20
-
If you don't have Postgres installed, please follow [installation guide](https://cocoindex.io/docs/getting_started/installation).
21
+
## Use Cases
22
+
A wide range of applications can be built with an effective codebase index that is always up-to-date. Some examples include:
21
23
22
-
## Add the codebase as a source.
24
+

25
+
26
+
- Semantic code context for AI coding agents like Claude, Codex, Gemini CLI.
27
+
- MCP for code editors such as Cursor, Windsurf, and VSCode.
- Enhance SRE workflows: enable rapid root cause analysis, incident response, and change impact assessment by indexing infrastructure-as-code, deployment scripts, and config files for semantic search and lineage tracking.
32
+
- Automatically generate design documentation from code—keep design docs up-to-date.
We use the `SplitRecursively` function to split the file into chunks.
75
-
It is integrated with Tree-sitter, so you can pass in the language to the `language` parameter.
76
-
To see all supported language names and extensions, see the documentation [here](https://cocoindex.io/docs/ops/functions#splitrecursively). All the major languages are supported, e.g., Python, Rust, JavaScript, TypeScript, Java, C++, etc. If it's unspecified or the specified language is not supported, it will be treated as plain text.
90
+
We use the `SplitRecursively` function to split the file into chunks. `SplitRecursively` is CocoIndex building block, with native integration with Tree-sitter. You need to pass in the language to the `language` parameter if you are processing code.
`@cocoindex.transform_flow()` is needed to share the transformation across indexing and query. When building a vector index and querying against it, the embedding computation must remain consistent between indexing and querying.
119
+
:::
103
120
104
-
`@cocoindex.transform_flow()` is needed to share the transformation across indexing and query. We build a vector index and query against it,
105
-
the embedding computation needs to be consistent between indexing and querying. See [documentation](https://cocoindex.io/docs/query#transform-flow) for more details.
0 commit comments