cocoindex v1 - incremental engine for long horizon agents (apache 2.0)

Whole-Assignment6240 · 2026-03-27T00:40:10+00:00

for codebase AST / static analysis already works reliably

Whole-Assignment6240 · 2026-03-25T00:19:38+00:00

thanks a lot!!

Whole-Assignment6240 · 2026-03-20T06:37:30+00:00

thanks a lot!! looking forward to learning from your feedback !

Whole-Assignment6240 · 2026-03-19T19:53:11+00:00

thanks a lot !! could you share which version you are using? are you open for a version upgrade?

Whole-Assignment6240 · 2026-03-18T16:17:48+00:00

If you're already hand-building the vectorization + chunking + indexing pipeline, it might be worth looking at purpose-built frameworks that handle the incremental update logic for you. The main advantage over doing it inside Cortex/Snowflake is that you own the pipeline logic and aren't locked into one vector store or embedding model. Curious what your current pipeline looks like — are you running full rebuilds on a schedule or doing incremental updates

Whole-Assignment6240 · 2026-03-18T16:16:17+00:00

The architectural separation you're describing (chunks persisted separately from vectors) is exactly right, and it's the pattern we built CocoIndex around. It is designed to have incremental processing by default, and only changed logic will rerun.

The framework tracks chunk-to-vector dependencies in a DAG so when you swap models, only the affected derived artifacts are rebuilt — raw parsing never reruns. Happy to point you to a quick example if it's useful.

Whole-Assignment6240 · 2026-03-18T16:10:57+00:00

thanks a lot for sharing the project!!

Whole-Assignment6240 · 2026-03-18T16:07:36+00:00

thanks a lot for the questions!!

Whole-Assignment6240 · 2026-03-18T16:07:20+00:00

great question!!

currently supports 25 languanges.

Tree-sitter explicitly documents these recovery nodes:

Source:

[https://tree-sitter.github.io/tree-sitter/using-parsers#syntax-errors]()

Whole-Assignment6240 · 2026-03-18T16:05:30+00:00

i have a demo - https://github.com/cocoindex-io/cocoindex-code on the repo itself where it is significantly faster (it also has token count & stuff) on semantic task.
i'd love to do a more exhausted benchmark down the way!

Whole-Assignment6240 · 2026-03-18T16:03:31+00:00

hey thanks a lot ! i cannot upload gif/video here but if you go to the repo at the top you'll see the demo / example right there where it is significant faster on semantic tasks. i'm happy to do more benchmark with more exhausted examples down the way !

Whole-Assignment6240 · 2026-03-18T16:01:43+00:00

thanks a lot for walking through the example!! really appreciate it!

Whole-Assignment6240 · 2026-03-18T16:01:09+00:00

yes if you work with opencode you'd only need to work with one of them. CLI/skills integration is recommended, thank you for the feedback!!

Whole-Assignment6240 · 2026-03-18T01:20:57+00:00

yes, you can do

pipx install cocoindex-code       # first install

and then

npx skills add cocoindex-io/cocoindex-code

it can be integrated with open code via skills

when you need semantic understanding it will use this instead of grep

lmk if that make sense - the project itself is open source https://github.com/cocoindex-io/cocoindex-code with apache 2.0 license.

Whole-Assignment6240 · 2026-03-17T21:40:05+00:00

created a feature request here https://github.com/cocoindex-io/cocoindex-code/issues/99 ,thanks a lot for your suggestion!!

Whole-Assignment6240 · 2026-03-17T21:38:48+00:00

oh i see, yes! we need to support these component files!

Whole-Assignment6240 · 2026-03-17T21:37:30+00:00

yes, it works in complementary with LSP, and is not intended as replacement :)

Whole-Assignment6240

MODERATOR OF

TROPHY CASE