cocoindex-code 0.2.41__tar.gz → 0.2.43__tar.gz

{cocoindex_code-0.2.41 → cocoindex_code-0.2.43}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: cocoindex-code
-Version: 0.2.41
+Version: 0.2.43
 Summary: MCP server for indexing and querying codebases using CocoIndex
 Project-URL: Homepage, https://github.com/cocoindex-io/cocoindex-code
 Project-URL: Repository, https://github.com/cocoindex-io/cocoindex-code
@@ -47,15 +47,15 @@ Description-Content-Type: text/markdown
 </p>
 
 
-<h1 align="center">AST-based semantic code search that just works</h1>
+<h1 align="center">AST-based semantic code search</h1>
 
 ![effect](https://github.com/user-attachments/assets/cb3a4cae-0e1f-49c4-890b-7bb93317ab60)
 
 
-A lightweight, effective **(AST-based)** semantic code search tool for your codebase. Built on [CocoIndex](https://github.com/cocoindex-io/cocoindex) — a Rust-based ultra performant data transformation engine. Use it from the CLI, or integrate with Claude, Codex, Cursor — any coding agent — via [Skill](#skill-recommended) or [MCP](#mcp-server).
+CocoIndex Code provides AST-based semantic search for your codebase, built on the [CocoIndex](https://github.com/cocoindex-io/cocoindex) Rust data transformation engine. Use it from the CLI or connect Claude, Codex, Cursor, and other coding agents through a [Skill](#skill-recommended) or [MCP](#mcp-server).
 
-- Instant token saving by 70%.
-- **1 min setup** — install and go, zero config needed!
+- 70% token savings.
+- 1 min setup with default settings.
 
 <div align="center">
 
@@ -69,7 +69,7 @@ A lightweight, effective **(AST-based)** semantic code search tool for your code
 [![release](https://github.com/cocoindex-io/cocoindex/actions/workflows/release.yml/badge.svg?event=push&color=5B5BD6)](https://github.com/cocoindex-io/cocoindex/actions/workflows/release.yml)
 
 
-🌟 Please help star [CocoIndex](https://github.com/cocoindex-io/cocoindex) if you like this project!
+Star [CocoIndex](https://github.com/cocoindex-io/cocoindex) if you find it useful.
 
 [Deutsch](https://readme-i18n.com/cocoindex-io/cocoindex-code?lang=de) |
 [English](https://readme-i18n.com/cocoindex-io/cocoindex-code?lang=en) |
@@ -84,7 +84,9 @@ A lightweight, effective **(AST-based)** semantic code search tool for your code
 </div>
 
 
-## Get Started — zero config, let's go!
+<a id="get-started--zero-config-lets-go"></a>
+
+## Get Started
 
 ### Install
 
@@ -117,7 +119,7 @@ Install the `ccc` skill so your coding agent automatically uses semantic search
 npx skills add cocoindex-io/cocoindex-code
 ```
 
-That's it — no `ccc init` or `ccc index` needed. The skill teaches the agent to handle initialization, indexing, and searching on its own. It will automatically keep the index up to date as you work.
+The skill teaches the agent to handle initialization, indexing, and searching, so you don't need to run `ccc init` or `ccc index` yourself. The agent keeps the index up to date as you work.
 
 The agent uses semantic search automatically when it would be helpful. You can also nudge it explicitly — just ask it to search the codebase, e.g. *"find how user sessions are managed"*, or type `/ccc` to invoke the skill directly.
 
@@ -141,7 +143,7 @@ For [Grok](https://github.com/xai-org/grok) users, install via Grok's plugin sys
 | Component | Purpose |
 |-----------|---------|
 | **Skill** (`skills/ccc/`) | Agent runs `ccc search` / `ccc index` via the CLI (same as Claude Code above) |
-| **Hook** (`hooks/hooks.json`) | `SessionStart` → incremental `ccc index` when `.cocoindex_code/` exists |
+| **Hook** (`hooks/hooks.json`) | `SessionStart` + `PostToolUse` (Edit/Write/…) → incremental `ccc index` when `.cocoindex_code/settings.yml` exists (never in the directory holding ccc's user settings, `~` by default) |
 | **MCP** (`.mcp.json`) | `ccc mcp` stdio server — `search` tool with `refresh_index=true` by default |
 
 Grok does **not** import Claude's `enabledPlugins` or plugin cache; install separately even if you already use cocoindex in Claude Code.
@@ -162,7 +164,7 @@ Prefer the GitHub shorthand (`cocoindex-io/cocoindex-code`) for install — `gro
 
 Install and enable as above, then disable the optional components:
 
-1. **Hooks** — open `/hooks`, select the `SessionStart` hook from `cocoindex-code`, press `Space` to disable.
+1. **Hooks** — open `/hooks`, select the `SessionStart` / `PostToolUse` hooks from `cocoindex-code`, press `Space` to disable.
 2. **MCP** — open `/mcps`, select `cocoindex-code`, press `Space` to disable; or persist in `~/.grok/config.toml`:
 
 ```toml
@@ -182,8 +184,32 @@ mcps = false
 mcps = false
 ```
 
+#### Oh My Pi plugin
+
+[Oh My Pi](https://github.com/can1357/oh-my-pi) reads `.omp-plugin/marketplace.json` (preferred) and falls back to `.claude-plugin/marketplace.json`.
+
+```bash
+omp plugin marketplace add cocoindex-io/cocoindex-code
+omp plugin install cocoindex-code@cocoindex-code --scope project
+```
+
+Then restart the session (`/reload-plugins` does not reload extensions). Requires `ccc` on `PATH` (`uv tool install --upgrade 'cocoindex-code[full]'`).
+
+| Component | Purpose |
+|-----------|---------|
+| **Skill** (`skills/ccc/`) | Agent runs `ccc search` / `ccc index` via the CLI |
+| **Hook** (`extensions/ccc-index.ts` via `package.json#omp.extensions`) | `session_start` + post-edit `tool_result` → incremental `ccc index` when `.cocoindex_code/settings.yml` exists (never in the directory holding ccc's user settings, `~` by default) |
+| **MCP** (`.mcp.json`) | `ccc mcp` stdio server |
+
+OMP does **not** execute Claude `hooks/hooks.json` command hooks. The TypeScript extension is the OMP equivalent of the Claude/Grok SessionStart + PostToolUse pair.
+
+Skill-only (no MCP, no auto-index): install the skill via `npx skills add cocoindex-io/cocoindex-code`, or run `ccc search` / `ccc index` from the shell.
+
 ### MCP Server
 
+<!-- Ownership marker for the official MCP registry. It must match "name" in server.json. Keep the next line. -->
+<!-- mcp-name: io.github.cocoindex-io/cocoindex-code -->
+
 Alternatively, use `ccc mcp` to run as an MCP server:
 
 <details>
@@ -246,7 +272,24 @@ Add a local MCP server in `~/.config/kilo/kilo.jsonc`, `kilo.jsonc`, or `.kilo/k
 ```
 </details>
 
-Once configured, the agent automatically decides when semantic code search is helpful — finding code by description, exploring unfamiliar codebases, fuzzy/conceptual matches, or locating implementations without knowing exact names.
+<details>
+<summary>Oh My Pi</summary>
+
+Prefer the marketplace install above. Manual project MCP (`.omp/mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "cocoindex-code": {
+      "command": "ccc",
+      "args": ["mcp"]
+    }
+  }
+}
+```
+</details>
+
+Once configured, the agent can use semantic search to find code by description, explore unfamiliar codebases, and locate implementations without exact names.
 
 > **Note:** The `cocoindex-code` command (without subcommand) still works as an MCP server for backward compatibility. It auto-creates settings from environment variables on first run.
 
@@ -285,6 +328,8 @@ The background daemon starts automatically on first use.
 
 > **Tip:** You can skip `ccc init` and go straight to `ccc index` — it auto-initializes new projects with default settings. If global settings are missing too (first use on the machine), it walks you through the same model setup as `ccc init` when run interactively; non-interactive runs (scripts, hooks) still require a one-time `ccc init` first.
 
+> **Note:** `ccc index` never auto-initializes the directory that holds ccc's user settings directory: your home directory by default (`~/.cocoindex_code` holds the global settings and daemon files), or the parent of `$COCOINDEX_CODE_DIR` when that directory is named `.cocoindex_code`. A project there would cover every repo below it. The editor hooks skip that directory even if it is already a project. If an older ccc made your home directory a project (`~/.cocoindex_code/settings.yml` exists), run `ccc reset --all` in your home directory: it removes that project's settings and indexes and keeps your global settings. To index your whole home directory on purpose, run `ccc init` there.
+
 ### CLI Reference
 
 | Command | Description |
@@ -437,8 +482,8 @@ ccc() {
 }
 ```
 
-Now `cd` into any project under your workspace and run `ccc init`, `ccc index`,
-`ccc search ...`, `ccc status`, etc. — it just works.
+Now `cd` into a project under your workspace and run `ccc init`, `ccc index`,
+`ccc search ...`, or `ccc status`.
 
 ### Connect your coding agent
 
@@ -527,11 +572,11 @@ docker build -t cocoindex-code:local -f docker/Dockerfile .
 ```
 
 ## Features
-- **Semantic Code Search**: Find relevant code using natural language queries when grep doesn't work well, and save tokens immediately.
-- **Ultra Performant**: ⚡ Built on top of ultra performant [Rust indexing engine](https://github.com/cocoindex-io/cocoindex). Only re-indexes changed files for fast updates.
+- **Semantic Code Search**: Find relevant code using natural language queries when grep doesn't work well.
+- **Incremental indexing**: The [Rust indexing engine](https://github.com/cocoindex-io/cocoindex) re-indexes only changed files.
 - **Multi-Language Support**: Python, JavaScript/TypeScript, Rust, Go, Java, C/C++, C#, SQL, Shell, and more.
-- **Embedded**: Portable and just works, no database setup required!
-- **Flexible Embeddings**: Local SentenceTransformers via the `[full]` extra (free, no API key!) or 100+ cloud providers via LiteLLM.
+- **Embedded storage**: No database setup required.
+- **Embedding providers**: Local SentenceTransformers via the `[full]` extra, with no API key, or 100+ cloud providers via LiteLLM.
 
 ## Configuration
 
@@ -647,8 +692,9 @@ After editing `include_patterns`, `exclude_patterns`, `max_file_size`, or `langu
 - Run `ccc doctor` to preview which files match.
 - Run `ccc index` or `ccc search --refresh ...` to update the existing index.
 - You do not need to delete the index or restart the daemon for these file-matching changes.
+- After any `language_overrides` change, the next run re-chunks all files, including files whose content did not change; the run reports them as reprocessed. Chunks whose text did not change keep their cached embeddings.
 
-If you add or change custom `chunkers`, restart the daemon first so the chunker registry is reloaded, then run `ccc index`.
+If you add or change custom `chunkers`, or edit a chunker module, restart the daemon (`ccc daemon restart`), then run `ccc index`. The daemon imports chunkers once at startup, so until it restarts it keeps running the old chunker code. The first run after the restart re-chunks all files, not only the ones the changed entry applies to; chunks whose text did not change keep their cached embeddings. A chunker counts as changed when its `module:` value changes or when the file of the module it names changes. Edits to other modules that file imports are not detected: after such an edit, also change the chunker's own module file (for example, bump a version comment in it).
 
 Use `chunkers` when you want to control how a file type is split into chunks before indexing.
 
@@ -850,6 +896,7 @@ embedding:
 | css | | `.css`, `.scss` |
 | dart | | `.dart` |
 | dtd | | `.dtd` |
+| elixir | | `.ex`, `.exs` |
 | fortran | f, f90, f95, f03 | `.f`, `.f90`, `.f95`, `.f03` |
 | go | golang | `.go` |
 | html | | `.html`, `.htm` |
@@ -899,7 +946,7 @@ Both source and target must be absolute paths. If no mapping matches, the defaul
 
 ## Troubleshooting
 
-Run `ccc doctor` to diagnose common issues. It checks your settings, daemon health, embedding model, file matching, and index status — all in one command.
+Run `ccc doctor` to check your settings, daemon health, embedding model, file matching, and index status.
 
 ### `sqlite3.Connection object has no attribute enable_load_extension`
 
@@ -911,7 +958,7 @@ Some Python installations (e.g. the one pre-installed on macOS) ship with a SQLi
 brew install python3
 ```
 
-Then re-install cocoindex-code (see [Get Started](#get-started--zero-config-lets-go) for install options):
+Then re-install cocoindex-code (see [Get Started](#get-started) for install options):
 
 Using pipx:
 ```bash
@@ -926,7 +973,7 @@ uv tool install --upgrade cocoindex-code
 
 ### `MDB_MAP_FULL: Environment mapsize limit reached`
 
-The index is stored in an LMDB database whose maximum size is fixed when the daemon starts. The default ceiling is **4 GiB**, which is plenty for most projects but can be exhausted by very large codebases (tens of thousands of files), especially with high-dimensional embedding models like `nomic-ai/CodeRankEmbed`.
+The index is stored in an LMDB database whose maximum size is fixed when the daemon starts. The default ceiling is **4 GiB**, which codebases with tens of thousands of files can exhaust, especially with high-dimensional embedding models like `nomic-ai/CodeRankEmbed`.
 
 Raise the ceiling with the `COCOINDEX_LMDB_MAP_SIZE` environment variable (value in **bytes**). LMDB only grows the file as data is written, so a high limit doesn't pre-allocate disk — it's safe to set it generously:
 
@@ -976,15 +1023,15 @@ export COCOINDEX_DISABLE_USAGE_TRACKING=1
 ```
 
 ## Large codebase / Enterprise
-[CocoIndex](https://github.com/cocoindex-io/cocoindex) is an ultra efficient indexing engine that also works on large codebases at scale for enterprises. In enterprise scenarios it is a lot more efficient to share indexes with teammates when there are large or many repos. We also have advanced features like branch dedupe etc designed for enterprise users.
+Teams indexing large or multiple repositories can share [CocoIndex](https://github.com/cocoindex-io/cocoindex) indexes across developers. Enterprise features include deduplication across branches.
 
-> Indexing a very large codebase and hitting `MDB_MAP_FULL`? Raise the LMDB map size — see [`MDB_MAP_FULL: Environment mapsize limit reached`](#mdb_map_full-environment-mapsize-limit-reached) under Troubleshooting.
+> If indexing fails with `MDB_MAP_FULL`, raise the LMDB map size. See [`MDB_MAP_FULL: Environment mapsize limit reached`](#mdb_map_full-environment-mapsize-limit-reached) under Troubleshooting.
 
-If you need help with remote setup, please email our maintainer linghua@cocoindex.io, happy to help!
+For help with remote setup, email linghua@cocoindex.io.
 
 ## Contributing
 
-We welcome contributions! This project uses [uv](https://docs.astral.sh/uv/getting-started/installation/) for development, and every PR is gated on the same lint, format, type-check, and test suite in CI. **Please run these checks locally before opening a PR** — failing pre-commit checks are the most common cause of red CI on incoming PRs.
+We welcome contributions. This project uses [uv](https://docs.astral.sh/uv/getting-started/installation/) for development. CI checks lint, formatting, types, and tests for every PR. Run the same checks locally before opening a PR; failed pre-commit checks are the most common cause of red CI on incoming PRs.
 
 ### 1. Install the dev dependencies
 

{cocoindex_code-0.2.41 → cocoindex_code-0.2.43}/README.md

@@ -3,15 +3,15 @@
 </p>
 
 
-<h1 align="center">AST-based semantic code search that just works</h1>
+<h1 align="center">AST-based semantic code search</h1>
 
 ![effect](https://github.com/user-attachments/assets/cb3a4cae-0e1f-49c4-890b-7bb93317ab60)
 
 
-A lightweight, effective **(AST-based)** semantic code search tool for your codebase. Built on [CocoIndex](https://github.com/cocoindex-io/cocoindex) — a Rust-based ultra performant data transformation engine. Use it from the CLI, or integrate with Claude, Codex, Cursor — any coding agent — via [Skill](#skill-recommended) or [MCP](#mcp-server).
+CocoIndex Code provides AST-based semantic search for your codebase, built on the [CocoIndex](https://github.com/cocoindex-io/cocoindex) Rust data transformation engine. Use it from the CLI or connect Claude, Codex, Cursor, and other coding agents through a [Skill](#skill-recommended) or [MCP](#mcp-server).
 
-- Instant token saving by 70%.
-- **1 min setup** — install and go, zero config needed!
+- 70% token savings.
+- 1 min setup with default settings.
 
 <div align="center">
 
@@ -25,7 +25,7 @@ A lightweight, effective **(AST-based)** semantic code search tool for your code
 [![release](https://github.com/cocoindex-io/cocoindex/actions/workflows/release.yml/badge.svg?event=push&color=5B5BD6)](https://github.com/cocoindex-io/cocoindex/actions/workflows/release.yml)
 
 
-🌟 Please help star [CocoIndex](https://github.com/cocoindex-io/cocoindex) if you like this project!
+Star [CocoIndex](https://github.com/cocoindex-io/cocoindex) if you find it useful.
 
 [Deutsch](https://readme-i18n.com/cocoindex-io/cocoindex-code?lang=de) |
 [English](https://readme-i18n.com/cocoindex-io/cocoindex-code?lang=en) |
@@ -40,7 +40,9 @@ A lightweight, effective **(AST-based)** semantic code search tool for your code
 </div>
 
 
-## Get Started — zero config, let's go!
+<a id="get-started--zero-config-lets-go"></a>
+
+## Get Started
 
 ### Install
 
@@ -73,7 +75,7 @@ Install the `ccc` skill so your coding agent automatically uses semantic search
 npx skills add cocoindex-io/cocoindex-code
 ```
 
-That's it — no `ccc init` or `ccc index` needed. The skill teaches the agent to handle initialization, indexing, and searching on its own. It will automatically keep the index up to date as you work.
+The skill teaches the agent to handle initialization, indexing, and searching, so you don't need to run `ccc init` or `ccc index` yourself. The agent keeps the index up to date as you work.
 
 The agent uses semantic search automatically when it would be helpful. You can also nudge it explicitly — just ask it to search the codebase, e.g. *"find how user sessions are managed"*, or type `/ccc` to invoke the skill directly.
 
@@ -97,7 +99,7 @@ For [Grok](https://github.com/xai-org/grok) users, install via Grok's plugin sys
 | Component | Purpose |
 |-----------|---------|
 | **Skill** (`skills/ccc/`) | Agent runs `ccc search` / `ccc index` via the CLI (same as Claude Code above) |
-| **Hook** (`hooks/hooks.json`) | `SessionStart` → incremental `ccc index` when `.cocoindex_code/` exists |
+| **Hook** (`hooks/hooks.json`) | `SessionStart` + `PostToolUse` (Edit/Write/…) → incremental `ccc index` when `.cocoindex_code/settings.yml` exists (never in the directory holding ccc's user settings, `~` by default) |
 | **MCP** (`.mcp.json`) | `ccc mcp` stdio server — `search` tool with `refresh_index=true` by default |
 
 Grok does **not** import Claude's `enabledPlugins` or plugin cache; install separately even if you already use cocoindex in Claude Code.
@@ -118,7 +120,7 @@ Prefer the GitHub shorthand (`cocoindex-io/cocoindex-code`) for install — `gro
 
 Install and enable as above, then disable the optional components:
 
-1. **Hooks** — open `/hooks`, select the `SessionStart` hook from `cocoindex-code`, press `Space` to disable.
+1. **Hooks** — open `/hooks`, select the `SessionStart` / `PostToolUse` hooks from `cocoindex-code`, press `Space` to disable.
 2. **MCP** — open `/mcps`, select `cocoindex-code`, press `Space` to disable; or persist in `~/.grok/config.toml`:
 
 ```toml
@@ -138,8 +140,32 @@ mcps = false
 mcps = false
 ```
 
+#### Oh My Pi plugin
+
+[Oh My Pi](https://github.com/can1357/oh-my-pi) reads `.omp-plugin/marketplace.json` (preferred) and falls back to `.claude-plugin/marketplace.json`.
+
+```bash
+omp plugin marketplace add cocoindex-io/cocoindex-code
+omp plugin install cocoindex-code@cocoindex-code --scope project
+```
+
+Then restart the session (`/reload-plugins` does not reload extensions). Requires `ccc` on `PATH` (`uv tool install --upgrade 'cocoindex-code[full]'`).
+
+| Component | Purpose |
+|-----------|---------|
+| **Skill** (`skills/ccc/`) | Agent runs `ccc search` / `ccc index` via the CLI |
+| **Hook** (`extensions/ccc-index.ts` via `package.json#omp.extensions`) | `session_start` + post-edit `tool_result` → incremental `ccc index` when `.cocoindex_code/settings.yml` exists (never in the directory holding ccc's user settings, `~` by default) |
+| **MCP** (`.mcp.json`) | `ccc mcp` stdio server |
+
+OMP does **not** execute Claude `hooks/hooks.json` command hooks. The TypeScript extension is the OMP equivalent of the Claude/Grok SessionStart + PostToolUse pair.
+
+Skill-only (no MCP, no auto-index): install the skill via `npx skills add cocoindex-io/cocoindex-code`, or run `ccc search` / `ccc index` from the shell.
+
 ### MCP Server
 
+<!-- Ownership marker for the official MCP registry. It must match "name" in server.json. Keep the next line. -->
+<!-- mcp-name: io.github.cocoindex-io/cocoindex-code -->
+
 Alternatively, use `ccc mcp` to run as an MCP server:
 
 <details>
@@ -202,7 +228,24 @@ Add a local MCP server in `~/.config/kilo/kilo.jsonc`, `kilo.jsonc`, or `.kilo/k
 ```
 </details>
 
-Once configured, the agent automatically decides when semantic code search is helpful — finding code by description, exploring unfamiliar codebases, fuzzy/conceptual matches, or locating implementations without knowing exact names.
+<details>
+<summary>Oh My Pi</summary>
+
+Prefer the marketplace install above. Manual project MCP (`.omp/mcp.json`):
+
+```json
+{
+  "mcpServers": {
+    "cocoindex-code": {
+      "command": "ccc",
+      "args": ["mcp"]
+    }
+  }
+}
+```
+</details>
+
+Once configured, the agent can use semantic search to find code by description, explore unfamiliar codebases, and locate implementations without exact names.
 
 > **Note:** The `cocoindex-code` command (without subcommand) still works as an MCP server for backward compatibility. It auto-creates settings from environment variables on first run.
 
@@ -241,6 +284,8 @@ The background daemon starts automatically on first use.
 
 > **Tip:** You can skip `ccc init` and go straight to `ccc index` — it auto-initializes new projects with default settings. If global settings are missing too (first use on the machine), it walks you through the same model setup as `ccc init` when run interactively; non-interactive runs (scripts, hooks) still require a one-time `ccc init` first.
 
+> **Note:** `ccc index` never auto-initializes the directory that holds ccc's user settings directory: your home directory by default (`~/.cocoindex_code` holds the global settings and daemon files), or the parent of `$COCOINDEX_CODE_DIR` when that directory is named `.cocoindex_code`. A project there would cover every repo below it. The editor hooks skip that directory even if it is already a project. If an older ccc made your home directory a project (`~/.cocoindex_code/settings.yml` exists), run `ccc reset --all` in your home directory: it removes that project's settings and indexes and keeps your global settings. To index your whole home directory on purpose, run `ccc init` there.
+
 ### CLI Reference
 
 | Command | Description |
@@ -393,8 +438,8 @@ ccc() {
 }
 ```
 
-Now `cd` into any project under your workspace and run `ccc init`, `ccc index`,
-`ccc search ...`, `ccc status`, etc. — it just works.
+Now `cd` into a project under your workspace and run `ccc init`, `ccc index`,
+`ccc search ...`, or `ccc status`.
 
 ### Connect your coding agent
 
@@ -483,11 +528,11 @@ docker build -t cocoindex-code:local -f docker/Dockerfile .
 ```
 
 ## Features
-- **Semantic Code Search**: Find relevant code using natural language queries when grep doesn't work well, and save tokens immediately.
-- **Ultra Performant**: ⚡ Built on top of ultra performant [Rust indexing engine](https://github.com/cocoindex-io/cocoindex). Only re-indexes changed files for fast updates.
+- **Semantic Code Search**: Find relevant code using natural language queries when grep doesn't work well.
+- **Incremental indexing**: The [Rust indexing engine](https://github.com/cocoindex-io/cocoindex) re-indexes only changed files.
 - **Multi-Language Support**: Python, JavaScript/TypeScript, Rust, Go, Java, C/C++, C#, SQL, Shell, and more.
-- **Embedded**: Portable and just works, no database setup required!
-- **Flexible Embeddings**: Local SentenceTransformers via the `[full]` extra (free, no API key!) or 100+ cloud providers via LiteLLM.
+- **Embedded storage**: No database setup required.
+- **Embedding providers**: Local SentenceTransformers via the `[full]` extra, with no API key, or 100+ cloud providers via LiteLLM.
 
 ## Configuration
 
@@ -603,8 +648,9 @@ After editing `include_patterns`, `exclude_patterns`, `max_file_size`, or `langu
 - Run `ccc doctor` to preview which files match.
 - Run `ccc index` or `ccc search --refresh ...` to update the existing index.
 - You do not need to delete the index or restart the daemon for these file-matching changes.
+- After any `language_overrides` change, the next run re-chunks all files, including files whose content did not change; the run reports them as reprocessed. Chunks whose text did not change keep their cached embeddings.
 
-If you add or change custom `chunkers`, restart the daemon first so the chunker registry is reloaded, then run `ccc index`.
+If you add or change custom `chunkers`, or edit a chunker module, restart the daemon (`ccc daemon restart`), then run `ccc index`. The daemon imports chunkers once at startup, so until it restarts it keeps running the old chunker code. The first run after the restart re-chunks all files, not only the ones the changed entry applies to; chunks whose text did not change keep their cached embeddings. A chunker counts as changed when its `module:` value changes or when the file of the module it names changes. Edits to other modules that file imports are not detected: after such an edit, also change the chunker's own module file (for example, bump a version comment in it).
 
 Use `chunkers` when you want to control how a file type is split into chunks before indexing.
 
@@ -806,6 +852,7 @@ embedding:
 | css | | `.css`, `.scss` |
 | dart | | `.dart` |
 | dtd | | `.dtd` |
+| elixir | | `.ex`, `.exs` |
 | fortran | f, f90, f95, f03 | `.f`, `.f90`, `.f95`, `.f03` |
 | go | golang | `.go` |
 | html | | `.html`, `.htm` |
@@ -855,7 +902,7 @@ Both source and target must be absolute paths. If no mapping matches, the defaul
 
 ## Troubleshooting
 
-Run `ccc doctor` to diagnose common issues. It checks your settings, daemon health, embedding model, file matching, and index status — all in one command.
+Run `ccc doctor` to check your settings, daemon health, embedding model, file matching, and index status.
 
 ### `sqlite3.Connection object has no attribute enable_load_extension`
 
@@ -867,7 +914,7 @@ Some Python installations (e.g. the one pre-installed on macOS) ship with a SQLi
 brew install python3
 ```
 
-Then re-install cocoindex-code (see [Get Started](#get-started--zero-config-lets-go) for install options):
+Then re-install cocoindex-code (see [Get Started](#get-started) for install options):
 
 Using pipx:
 ```bash
@@ -882,7 +929,7 @@ uv tool install --upgrade cocoindex-code
 
 ### `MDB_MAP_FULL: Environment mapsize limit reached`
 
-The index is stored in an LMDB database whose maximum size is fixed when the daemon starts. The default ceiling is **4 GiB**, which is plenty for most projects but can be exhausted by very large codebases (tens of thousands of files), especially with high-dimensional embedding models like `nomic-ai/CodeRankEmbed`.
+The index is stored in an LMDB database whose maximum size is fixed when the daemon starts. The default ceiling is **4 GiB**, which codebases with tens of thousands of files can exhaust, especially with high-dimensional embedding models like `nomic-ai/CodeRankEmbed`.
 
 Raise the ceiling with the `COCOINDEX_LMDB_MAP_SIZE` environment variable (value in **bytes**). LMDB only grows the file as data is written, so a high limit doesn't pre-allocate disk — it's safe to set it generously:
 
@@ -932,15 +979,15 @@ export COCOINDEX_DISABLE_USAGE_TRACKING=1
 ```
 
 ## Large codebase / Enterprise
-[CocoIndex](https://github.com/cocoindex-io/cocoindex) is an ultra efficient indexing engine that also works on large codebases at scale for enterprises. In enterprise scenarios it is a lot more efficient to share indexes with teammates when there are large or many repos. We also have advanced features like branch dedupe etc designed for enterprise users.
+Teams indexing large or multiple repositories can share [CocoIndex](https://github.com/cocoindex-io/cocoindex) indexes across developers. Enterprise features include deduplication across branches.
 
-> Indexing a very large codebase and hitting `MDB_MAP_FULL`? Raise the LMDB map size — see [`MDB_MAP_FULL: Environment mapsize limit reached`](#mdb_map_full-environment-mapsize-limit-reached) under Troubleshooting.
+> If indexing fails with `MDB_MAP_FULL`, raise the LMDB map size. See [`MDB_MAP_FULL: Environment mapsize limit reached`](#mdb_map_full-environment-mapsize-limit-reached) under Troubleshooting.
 
-If you need help with remote setup, please email our maintainer linghua@cocoindex.io, happy to help!
+For help with remote setup, email linghua@cocoindex.io.
 
 ## Contributing
 
-We welcome contributions! This project uses [uv](https://docs.astral.sh/uv/getting-started/installation/) for development, and every PR is gated on the same lint, format, type-check, and test suite in CI. **Please run these checks locally before opening a PR** — failing pre-commit checks are the most common cause of red CI on incoming PRs.
+We welcome contributions. This project uses [uv](https://docs.astral.sh/uv/getting-started/installation/) for development. CI checks lint, formatting, types, and tests for every PR. Run the same checks locally before opening a PR; failed pre-commit checks are the most common cause of red CI on incoming PRs.
 
 ### 1. Install the dev dependencies
 

{cocoindex_code-0.2.41 → cocoindex_code-0.2.43}/src/cocoindex_code/_daemon_paths.py

@@ -14,6 +14,7 @@ import tempfile
 import time
 from dataclasses import dataclass
 from pathlib import Path
+from typing import NamedTuple
 
 from .settings import user_settings_dir
 
@@ -79,6 +80,45 @@ def daemon_socket_path() -> str:
     return str(short)
 
 
+class SocketIdentity(NamedTuple):
+    """Identifies one socket file, telling a daemon's own apart from one a
+    replacement daemon has since bound at the same path (issue #288).
+
+    ``ctime_ns`` is part of it because ext4/overlayfs hand a freed inode
+    number straight to the next file: once the original socket is closed and
+    unlinked, a replacement's can have the same ``(dev, ino)``.
+    """
+
+    dev: int
+    ino: int
+    ctime_ns: int
+
+
+def socket_identity(path: str) -> SocketIdentity | None:
+    """Return the identity of the socket file at *path*, or None if absent. POSIX only."""
+    try:
+        st = os.stat(path)
+    except OSError:
+        return None
+    return SocketIdentity(st.st_dev, st.st_ino, st.st_ctime_ns)
+
+
+def unlink_socket_if_owned(path: str, identity: SocketIdentity | None) -> None:
+    """Remove the socket file at *path* only if it is still *identity*.
+
+    Leaves alone a socket a replacement daemon has bound there since. Not
+    atomic — POSIX has no unlink-if-inode — so a replacement binding between
+    the stat and the unlink is still lost, but that window is microseconds.
+    Best-effort — never raises.
+    """
+    if identity is None or socket_identity(path) != identity:
+        return
+    try:
+        os.unlink(path)
+    except OSError:
+        pass
+
+
 def daemon_pid_path() -> Path:
     """Return the path for the daemon's PID file."""
     return daemon_runtime_dir() / "daemon.pid"

{cocoindex_code-0.2.41 → cocoindex_code-0.2.43}/src/cocoindex_code/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.2.41'
-__version_tuple__ = version_tuple = (0, 2, 41)
+__version__ = version = '0.2.43'
+__version_tuple__ = version_tuple = (0, 2, 43)
 
 __commit_id__ = commit_id = None

cocoindex_code-0.2.43/src/cocoindex_code/chunking.py

@@ -0,0 +1,54 @@
+"""Public API for writing custom chunkers.
+
+Example usage::
+
+    from pathlib import Path
+    from cocoindex_code.chunking import Chunk, ChunkerFn, TextPosition
+
+    def my_chunker(path: Path, content: str) -> tuple[str | None, list[Chunk]]:
+        pos = TextPosition(byte_offset=0, char_offset=0, line=1, column=0)
+        return "mylang", [Chunk(text=content, start=pos, end=pos)]
+"""
+
+from __future__ import annotations
+
+import dataclasses as _dataclasses
+import pathlib as _pathlib
+from collections.abc import Callable as _Callable
+
+import cocoindex as _coco
+from cocoindex.resources.chunk import Chunk, TextPosition
+
+# Callable alias (not Protocol) — consistent with codebase style.
+# language_override=None keeps the language detected by detect_code_language.
+# path is not resolved (no syscall); call path.resolve() inside the chunker if needed.
+ChunkerFn = _Callable[[_pathlib.Path, str], tuple[str | None, list[Chunk]]]
+
+
+@_dataclasses.dataclass(frozen=True)
+class LoadedChunker:
+    """A chunker the daemon imported from a ``settings.yml`` entry.
+
+    Its memo key is ``(spec, module_sha256)``, never ``fn`` itself: cocoindex
+    fingerprints a function by its module and name only, so an edit to its body
+    would go unnoticed, and it cannot fingerprint lambdas or closures at all.
+    """
+
+    fn: ChunkerFn
+    #: The ``"module.path:callable"`` string from ``settings.yml``.
+    spec: str
+    #: sha256 of the module file named in ``spec``, as it was when imported. Helper
+    #: modules that file imports are not covered.
+    module_sha256: str
+
+    def __coco_memo_key__(self) -> tuple[str, str]:
+        return (self.spec, self.module_sha256)
+
+
+# Keyed by file suffix (e.g. ".toml"). Adding, removing or changing an entry
+# re-processes all files.
+CHUNKER_REGISTRY = _coco.ContextKey[dict[str, LoadedChunker]](
+    "chunker_registry", detect_change=True
+)
+
+__all__ = ["Chunk", "ChunkerFn", "CHUNKER_REGISTRY", "LoadedChunker", "TextPosition"]