production ready

Continuously fresh context for AI.

Turn codebases, meeting notes, inboxes, videos … into live context for your agents to reason over effectively — with minimal incremental processing. Fresh data anytime.

Star on GitHub—
Incremental · only the deltaAny scale · parallel by defaultDeclarative · Python, 5 min
codebase · real-timeΔ onlycocoindex.flowliveSRC/page.tsxlayout.tsxheader.tsxutils.tsdb.tsapi.tscall_graph(file) · who calls whom, rebuilt incrementally as imports changeCALL GRAPHmaininitloadcfgapiHIERARCHY▾ app▾ uiButtonCardapirouteVECTORSSYMBOLSindexCodefnChunkerclsembedfnflowmodsinkfn2,410 FILES18,074 CHUNKSΔ 12
Built with CocoIndex

CocoIndex-code · Super-charge coding agent with live context.

Call graphs, hierarchies, symbol tables, and semantic indexes — all kept fresh as the repo changes. Learn more about CocoIndex Code →

Star on GitHub—
YOUR REPOsrc/flow.pypipeline.pyembed.pyapi/route.tsutils.tsON CHANGEΔCALL GRAPHmainembedSYMBOLSembedfnChunkerclssinkmodVECTORSCHUNKS · ASTCONTEXTLIVE · FRESHCODING AGENT▸where is embed() called?◯3 callers · freshly indexedsrc/flow.py:42src/pipeline.py:18tests/t_embed.py:7▸
Δ +1

Incremental processing

Only the delta is reindexed. Sub-second freshness at any repo size.

Index & semantic search

Less grep. Find by meaning — functions, patterns, intent — not string matches.

Call graphs & blast radius

Know exactly what a change touches before it ships. Trace every caller and callee.

Global view

Spot duplicates. Understand architecture across the whole repo, not one file.

Build your own

Coding agents

Generate · refactor

Code-review agents

Catch · approve

Security-review agents

Scan · audit

Built with CocoIndex

Built with CocoIndex. Let's go!

Working starters. Clone, plug your source, ship. Each one is a handful of files and a flow declaration.

Codebase · real-timedefindex_code(repo):# walk the treefor file in repo.files:chunks = chunk(file)emb = embed(chunks)sink(emb, "postgres")@cocoindex.flowFork This Idea →

Real-time codebase indexing

Keep an index of your repo in sync with every commit. Feed code-review and coding agents with structure, not raw text.

Meetings · knowledge graphperson:noratopic:q2action:shipdoc:rfc-14meetingFork This Idea →

Meeting notes → knowledge graph

Extract people, topics, decisions and action items from notes into a live graph. Query them with your agent.

Hacker News · trendst-6ht-3hnow↑ agents↑ rustFork This Idea →

HN trending topics detector

Ingest Hacker News incrementally. Detect surfacing topics before they peak. Perfect for weekend hacking.

See all examples →
How it works

CocoIndex is an incremental engine for long-horizon agents.

Data transformation for any engineer, designed for AI workloads — with a smart incremental engine for always-fresh, explainable data.

Learn the concept →

Python Native TransformationCodebasesMeeting NotesWeb · APIsFile System · Blob StoresDatabasesMessage QueuesImages · VideoVoice · TranscriptsRelational DBData WarehouseVector DBGraph DBMessage QueueFeature StoreSource file · walk_dir() yields FileLike — this run's inputFileLikeawait coco.map(process_chunk, splitter.split(text))split() → chunksembed(chunk) → vector · memoized (skipped when input+code unchanged)embed(chunk) → vecembed(chunk) → vector · memoizedembed(chunk) → vecSame path, content changed → new fingerprint; downstream re-runs only for delta chunksFileLike (Δ)splitter.split(text) re-runs on the changed file; unchanged chunks stay memoized downstreamsplit() re-runs@coco.fn(memo=True) · input unchanged → embed skipped, cached vector reusedcache hit · no re-rundelta detected · input fingerprint changed → await embed(chunk) re-runsΔ → re-embed
CocoInsightLIVELineagesrcsinkObservabilityCocoIndex Persistent Data Pipeline Control PlaneLIVECachingReuse what hasn't changed — only thedelta runs.Pipeline CatalogEvery flow registered — find, fork,reuse.Version TrackingCode, schema, data — all versionedend-to-end.Continuously LearningThe engine adapts as your data andcode evolve.LineageEvery byte in the target traces backto a source.Task SchedulingParallel by default — low-latency,low-cost.Metrics CollectionThroughput, freshness, cost — allobservable.Failure ManagementRetries, back-off, dead letters — nodata loss.
Built for agents

Reliable. Autonomous. Minimalistic.

Agents break when their data lies. CocoIndex makes the data tell the truth — through every source change, every code change, and every long-running job to back long horizon agents.

Δonly ΔData change

Source data changed. We noticed. Before you did.

When source changes

One file edited → one row re-syncs.

Don't think about it. The framework watches the source, computes the delta, and reconciles the target — at any scale, in parallel.

Incremental by default
v2liveCode change

Code changed. Schema auto evolved. No migration meeting.

When F changes

Ship new code → only affected rows re-run.

Your target store is already connected to live agents? No worries. Only changed code gets rerun. Schemas evolve automatically.

No index swap · no downtime
The mental model

React — for data engineering.

A persistent-state-driven model. You declare the desired state of your target. The engine keeps it in sync with the latest source data and code, across long time horizons, with low latency and low cost.

Your code is as simple as the one-off version.

See the React ↔ CocoIndex mental model →

Target=F(Source)

TARGETF · YOUR CODE@coco.fnprocess(src)SOURCEa.pyb.mdc.pdfd.ts
ENGINE · AUTO-SYNC · Δ ONLY
def

Python, not a DAG.

You write the transform. The engine derives the graph.

Declare target state.

We compute the minimum work to reach it.

Lineage end-to-end.

Every byte in the target traces to a source.

Δ +1

Incremental at any scale.

Only the delta runs — never the full recompute.

CocoInsight

What's going on with my data?

Step-by-step, understand what your pipeline is doing. Think of it as real-time rendering in the browser — for data.

CocoInsight

Every step. Every record. Explainable.

See the shape of your data at every stage of the flow. Trace a single vector back to the paragraph it came from. Debug with your eyes, not grep.

Flow · pdf_ingestlive · 24 rec/s
SOURCECHUNKEMBEDSINKrfc-14.pdfreadme.mdspec.pdfcachednew.pdfe5-mistral · 1024d · 68%postgres · table: docs5 files · 1 new142 chunks · Δ 8142 vec · Δ 8upserted · 8
● running · reused 94%cocoinsight.local
Vibing?

Vibe-coding native. Pipeline ready in 5 min.

Describe the flow. Claude writes the cocoindex. You run it. The framework keeps it fresh forever.

Try the Claude skill →
youindex my /docs folder into Postgres.
claudewiring cocoindex.flow · chunk → embed → sink…
okflow.py · 14 lines · running
log[00:12] 142 chunks · 1024d · 68% cached
Loved by builders

Incredible optimizations, out of the box.

I'm in love with CocoIndex. ❤️ It's a very mature project — with incredible optimizations like incremental processing, parallel chunking, and maximum efficiency built right in. These are hard to design and maintain, yet they just work out of the box.

I'm inspired to learn Rust because I want to contribute to CocoIndex and Zed. Both represent the best of engineering excellence and community spirit.

And honestly — CocoIndex has one of the most responsible, thoughtful communities I've seen.

Shivansh Subramanian · Startup Founder

Your agents deserve fresh context.

Get your agent ready to production in 10 min with reliable and fresh data.

Star on GitHubLearn the Concept