code-context-engine 0.4.20__tar.gz → 0.4.22__tar.gz

{code_context_engine-0.4.20/src/code_context_engine.egg-info → code_context_engine-0.4.22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-context-engine
-Version: 0.4.20
+Version: 0.4.22
 Summary: Save 94% on Claude Code tokens. Index your codebase locally, AI agents search instead of reading files. Reduce Claude API costs, save tokens on Cursor, VS Code, Gemini CLI. Free, open source MCP server.
 Author-email: Fazle Elahee <felahee@gmail.com>, Raj <rajkumar.sakti@gmail.com>
 License-Expression: MIT
@@ -115,15 +115,17 @@ Dynamic: license-file
 
 ---
 
-## Quick start (3 lines)
+## Quick start
 
 ```bash
-uv tool install code-context-engine
+uv tool install "code-context-engine[local]"    # or: pipx install "code-context-engine[local]"
 cd /path/to/your/project
-cce init
+cce init                                        # or: cce init --agent all
 ```
 
-That's it. Claude now searches your index instead of reading entire files. No config needed.
+That's it. Your AI coding agent now searches your index instead of reading entire files.
+
+> **Already have Ollama?** You can skip `[local]` and use `uv tool install code-context-engine` instead. CCE auto-detects Ollama at localhost:11434 and uses `nomic-embed-text`.
 
 ---
 
@@ -143,35 +145,42 @@ Tested on all three platforms in CI (macOS, Linux, Windows × Python 3.11/3.12/3
 
 ## Install and see savings in 60 seconds
 
-```bash
-uv tool install code-context-engine   # or: pipx install code-context-engine
-cd /path/to/your/project
-cce init                              # index, install hooks, register MCP server
-```
+You need an embedding backend to index code. Pick one:
+
+| Option | Install command | Size | Requires |
+|--------|----------------|------|----------|
+| **Local (recommended)** | `uv tool install "code-context-engine[local]"` | +60 MB | Nothing else |
+| **Ollama** | `uv tool install code-context-engine` | Core only | Ollama running + `nomic-embed-text` pulled |
 
-**Embedding backends:** CCE auto-detects the best available backend. If you have Ollama running, it uses `nomic-embed-text` with zero extra dependencies. For offline/local embedding without Ollama, install the `[local]` extra:
+Then:
 
 ```bash
-uv tool install "code-context-engine[local]"   # includes fastembed + ONNX Runtime
+cd /path/to/your/project
+cce init                              # index, install hooks, register MCP server
 ```
 
 Restart your editor. Done. Every question now hits the index instead of re-reading files.
 
-`cce init` auto-detects your editor and writes the right config:
+`cce init` auto-detects your editor and writes the right config. To target a
+specific agent, use `--agent claude`, `--agent codex`, `--agent copilot`, or
+`--agent all`.
 
 | Editor | Config written | Instructions |
 |--------|---------------|--------------|
 | Claude Code | `.mcp.json` | `CLAUDE.md` |
-| VS Code / Copilot | `.vscode/mcp.json` | |
+| VS Code / Copilot | `.vscode/mcp.json` | `.github/copilot-instructions.md` |
 | Cursor | `.cursor/mcp.json` | `.cursorrules` |
 | Gemini CLI | `.gemini/settings.json` | `GEMINI.md` |
-| OpenAI Codex | `~/.codex/config.toml` (user-global, per-project section) | |
+| OpenAI Codex | `~/.codex/config.toml` (user-global, per-project section) | `AGENTS.md` |
 | OpenCode | `opencode.json` | |
 | Tabnine | `.tabnine/agent/settings.json` | `TABNINE.md` |
 
 Multiple editors in the same project? All get configured in one command.
 
-**Codex note:** Codex CLI reads MCP servers from `~/.codex/config.toml` only — it has no per-project config. `cce init` adds one `[mcp_servers.cce-<project>-<hash>]` section per project so multiple projects coexist; `cce uninstall` removes only the section for the current project.
+**Codex note:** Codex CLI reads MCP servers from `~/.codex/config.toml` only —
+it has no per-project config. `cce init` adds one `[mcp_servers.cce-<project>-<hash>]`
+section per project so multiple projects coexist; `cce uninstall` removes only
+the section for the current project.
 
 ```
   my-project · 38 queries
@@ -487,6 +496,57 @@ All other text files are chunked by line range. Binary files are skipped.
 
 ---
 
+## FAQ
+
+### Does CCE affect response quality?
+
+No. Quality stays the same or slightly improves.
+
+CCE replaces "dump the entire file" with "search for the relevant function." The model still gets the code it needs (0.90 Recall@10 in benchmarks). Less irrelevant context means less noise competing for attention, which can improve the model's focus on your actual question.
+
+### How does output token savings work?
+
+CCE writes output compression rules directly into your agent's instruction files (`CLAUDE.md`, `AGENTS.md`, `.cursorrules`, etc.) during `cce init`. These rules apply to the **entire session**, not just CCE tool responses, so every reply from the agent follows them.
+
+Set the level in `cce.yaml`:
+
+```yaml
+compression:
+  output: max       # off | lite | standard | max
+```
+
+Then re-run `cce init` to update instruction files. Or change at runtime:
+
+```
+set_output_level output_level=max
+```
+
+| Level | Savings | What it does |
+|-------|---------|--------------|
+| `off` | 0% | No compression |
+| `lite` | ~25% | Removes filler/hedging/pleasantries + diff-only for code changes |
+| `standard` | ~70% | Drops articles, fragments, short synonyms + diff-only for code |
+| `max` | ~80% | Telegraphic style + diff-only for code |
+
+Default is `standard`. All levels include **code output rules** that tell the model to show only changed lines (not full file rewrites), which is where most output tokens go in coding sessions. The `max` level produces very terse prose (similar to "caveman mode"). Code blocks, paths, and commands are never compressed regardless of level.
+
+### Where do the savings come from?
+
+Most savings are **input tokens** (what goes into the model):
+
+| Layer | Type | Typical savings |
+|-------|------|-----------------|
+| Retrieval | Input | 94% (full files → relevant chunks) |
+| Chunk compression | Input | 89% (chunks → signatures) |
+| Grammar compression | Input | 13% (article/filler removal) |
+| Turn summarization | Input | varies (session history) |
+| Progressive disclosure | Input | varies (tool payloads) |
+| Output compression | Output | 25-80% (depends on level) |
+
+Output tokens cost 5x more per token (e.g. Opus: $15/1M input vs $75/1M output), so even a small output reduction has outsized cost impact.
+
+---
+
 ## Roadmap
 
 - [x] Multi-repo benchmarks (FastAPI, chi, fiber)

{code_context_engine-0.4.20 → code_context_engine-0.4.22}/README.md

@@ -64,15 +64,17 @@
 
 ---
 
-## Quick start (3 lines)
+## Quick start
 
 ```bash
-uv tool install code-context-engine
+uv tool install "code-context-engine[local]"    # or: pipx install "code-context-engine[local]"
 cd /path/to/your/project
-cce init
+cce init                                        # or: cce init --agent all
 ```
 
-That's it. Claude now searches your index instead of reading entire files. No config needed.
+That's it. Your AI coding agent now searches your index instead of reading entire files.
+
+> **Already have Ollama?** You can skip `[local]` and use `uv tool install code-context-engine` instead. CCE auto-detects Ollama at localhost:11434 and uses `nomic-embed-text`.
 
 ---
 
@@ -92,35 +94,42 @@ Tested on all three platforms in CI (macOS, Linux, Windows × Python 3.11/3.12/3
 
 ## Install and see savings in 60 seconds
 
-```bash
-uv tool install code-context-engine   # or: pipx install code-context-engine
-cd /path/to/your/project
-cce init                              # index, install hooks, register MCP server
-```
+You need an embedding backend to index code. Pick one:
+
+| Option | Install command | Size | Requires |
+|--------|----------------|------|----------|
+| **Local (recommended)** | `uv tool install "code-context-engine[local]"` | +60 MB | Nothing else |
+| **Ollama** | `uv tool install code-context-engine` | Core only | Ollama running + `nomic-embed-text` pulled |
 
-**Embedding backends:** CCE auto-detects the best available backend. If you have Ollama running, it uses `nomic-embed-text` with zero extra dependencies. For offline/local embedding without Ollama, install the `[local]` extra:
+Then:
 
 ```bash
-uv tool install "code-context-engine[local]"   # includes fastembed + ONNX Runtime
+cd /path/to/your/project
+cce init                              # index, install hooks, register MCP server
 ```
 
 Restart your editor. Done. Every question now hits the index instead of re-reading files.
 
-`cce init` auto-detects your editor and writes the right config:
+`cce init` auto-detects your editor and writes the right config. To target a
+specific agent, use `--agent claude`, `--agent codex`, `--agent copilot`, or
+`--agent all`.
 
 | Editor | Config written | Instructions |
 |--------|---------------|--------------|
 | Claude Code | `.mcp.json` | `CLAUDE.md` |
-| VS Code / Copilot | `.vscode/mcp.json` | |
+| VS Code / Copilot | `.vscode/mcp.json` | `.github/copilot-instructions.md` |
 | Cursor | `.cursor/mcp.json` | `.cursorrules` |
 | Gemini CLI | `.gemini/settings.json` | `GEMINI.md` |
-| OpenAI Codex | `~/.codex/config.toml` (user-global, per-project section) | |
+| OpenAI Codex | `~/.codex/config.toml` (user-global, per-project section) | `AGENTS.md` |
 | OpenCode | `opencode.json` | |
 | Tabnine | `.tabnine/agent/settings.json` | `TABNINE.md` |
 
 Multiple editors in the same project? All get configured in one command.
 
-**Codex note:** Codex CLI reads MCP servers from `~/.codex/config.toml` only — it has no per-project config. `cce init` adds one `[mcp_servers.cce-<project>-<hash>]` section per project so multiple projects coexist; `cce uninstall` removes only the section for the current project.
+**Codex note:** Codex CLI reads MCP servers from `~/.codex/config.toml` only —
+it has no per-project config. `cce init` adds one `[mcp_servers.cce-<project>-<hash>]`
+section per project so multiple projects coexist; `cce uninstall` removes only
+the section for the current project.
 
 ```
   my-project · 38 queries
@@ -436,6 +445,57 @@ All other text files are chunked by line range. Binary files are skipped.
 
 ---
 
+## FAQ
+
+### Does CCE affect response quality?
+
+No. Quality stays the same or slightly improves.
+
+CCE replaces "dump the entire file" with "search for the relevant function." The model still gets the code it needs (0.90 Recall@10 in benchmarks). Less irrelevant context means less noise competing for attention, which can improve the model's focus on your actual question.
+
+### How does output token savings work?
+
+CCE writes output compression rules directly into your agent's instruction files (`CLAUDE.md`, `AGENTS.md`, `.cursorrules`, etc.) during `cce init`. These rules apply to the **entire session**, not just CCE tool responses, so every reply from the agent follows them.
+
+Set the level in `cce.yaml`:
+
+```yaml
+compression:
+  output: max       # off | lite | standard | max
+```
+
+Then re-run `cce init` to update instruction files. Or change at runtime:
+
+```
+set_output_level output_level=max
+```
+
+| Level | Savings | What it does |
+|-------|---------|--------------|
+| `off` | 0% | No compression |
+| `lite` | ~25% | Removes filler/hedging/pleasantries + diff-only for code changes |
+| `standard` | ~70% | Drops articles, fragments, short synonyms + diff-only for code |
+| `max` | ~80% | Telegraphic style + diff-only for code |
+
+Default is `standard`. All levels include **code output rules** that tell the model to show only changed lines (not full file rewrites), which is where most output tokens go in coding sessions. The `max` level produces very terse prose (similar to "caveman mode"). Code blocks, paths, and commands are never compressed regardless of level.
+
+### Where do the savings come from?
+
+Most savings are **input tokens** (what goes into the model):
+
+| Layer | Type | Typical savings |
+|-------|------|-----------------|
+| Retrieval | Input | 94% (full files → relevant chunks) |
+| Chunk compression | Input | 89% (chunks → signatures) |
+| Grammar compression | Input | 13% (article/filler removal) |
+| Turn summarization | Input | varies (session history) |
+| Progressive disclosure | Input | varies (tool payloads) |
+| Output compression | Output | 25-80% (depends on level) |
+
+Output tokens cost 5x more per token (e.g. Opus: $15/1M input vs $75/1M output), so even a small output reduction has outsized cost impact.
+
+---
+
 ## Roadmap
 
 - [x] Multi-repo benchmarks (FastAPI, chi, fiber)

{code_context_engine-0.4.20 → code_context_engine-0.4.22}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "code-context-engine"
-version = "0.4.20"
+version = "0.4.22"
 description = "Save 94% on Claude Code tokens. Index your codebase locally, AI agents search instead of reading files. Reduce Claude API costs, save tokens on Cursor, VS Code, Gemini CLI. Free, open source MCP server."
 readme = {file = "README.md", content-type = "text/markdown"}
 license = "MIT"

{code_context_engine-0.4.20 → code_context_engine-0.4.22/src/code_context_engine.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-context-engine
-Version: 0.4.20
+Version: 0.4.22
 Summary: Save 94% on Claude Code tokens. Index your codebase locally, AI agents search instead of reading files. Reduce Claude API costs, save tokens on Cursor, VS Code, Gemini CLI. Free, open source MCP server.
 Author-email: Fazle Elahee <felahee@gmail.com>, Raj <rajkumar.sakti@gmail.com>
 License-Expression: MIT
@@ -115,15 +115,17 @@ Dynamic: license-file
 
 ---
 
-## Quick start (3 lines)
+## Quick start
 
 ```bash
-uv tool install code-context-engine
+uv tool install "code-context-engine[local]"    # or: pipx install "code-context-engine[local]"
 cd /path/to/your/project
-cce init
+cce init                                        # or: cce init --agent all
 ```
 
-That's it. Claude now searches your index instead of reading entire files. No config needed.
+That's it. Your AI coding agent now searches your index instead of reading entire files.
+
+> **Already have Ollama?** You can skip `[local]` and use `uv tool install code-context-engine` instead. CCE auto-detects Ollama at localhost:11434 and uses `nomic-embed-text`.
 
 ---
 
@@ -143,35 +145,42 @@ Tested on all three platforms in CI (macOS, Linux, Windows × Python 3.11/3.12/3
 
 ## Install and see savings in 60 seconds
 
-```bash
-uv tool install code-context-engine   # or: pipx install code-context-engine
-cd /path/to/your/project
-cce init                              # index, install hooks, register MCP server
-```
+You need an embedding backend to index code. Pick one:
+
+| Option | Install command | Size | Requires |
+|--------|----------------|------|----------|
+| **Local (recommended)** | `uv tool install "code-context-engine[local]"` | +60 MB | Nothing else |
+| **Ollama** | `uv tool install code-context-engine` | Core only | Ollama running + `nomic-embed-text` pulled |
 
-**Embedding backends:** CCE auto-detects the best available backend. If you have Ollama running, it uses `nomic-embed-text` with zero extra dependencies. For offline/local embedding without Ollama, install the `[local]` extra:
+Then:
 
 ```bash
-uv tool install "code-context-engine[local]"   # includes fastembed + ONNX Runtime
+cd /path/to/your/project
+cce init                              # index, install hooks, register MCP server
 ```
 
 Restart your editor. Done. Every question now hits the index instead of re-reading files.
 
-`cce init` auto-detects your editor and writes the right config:
+`cce init` auto-detects your editor and writes the right config. To target a
+specific agent, use `--agent claude`, `--agent codex`, `--agent copilot`, or
+`--agent all`.
 
 | Editor | Config written | Instructions |
 |--------|---------------|--------------|
 | Claude Code | `.mcp.json` | `CLAUDE.md` |
-| VS Code / Copilot | `.vscode/mcp.json` | |
+| VS Code / Copilot | `.vscode/mcp.json` | `.github/copilot-instructions.md` |
 | Cursor | `.cursor/mcp.json` | `.cursorrules` |
 | Gemini CLI | `.gemini/settings.json` | `GEMINI.md` |
-| OpenAI Codex | `~/.codex/config.toml` (user-global, per-project section) | |
+| OpenAI Codex | `~/.codex/config.toml` (user-global, per-project section) | `AGENTS.md` |
 | OpenCode | `opencode.json` | |
 | Tabnine | `.tabnine/agent/settings.json` | `TABNINE.md` |
 
 Multiple editors in the same project? All get configured in one command.
 
-**Codex note:** Codex CLI reads MCP servers from `~/.codex/config.toml` only — it has no per-project config. `cce init` adds one `[mcp_servers.cce-<project>-<hash>]` section per project so multiple projects coexist; `cce uninstall` removes only the section for the current project.
+**Codex note:** Codex CLI reads MCP servers from `~/.codex/config.toml` only —
+it has no per-project config. `cce init` adds one `[mcp_servers.cce-<project>-<hash>]`
+section per project so multiple projects coexist; `cce uninstall` removes only
+the section for the current project.
 
 ```
   my-project · 38 queries
@@ -487,6 +496,57 @@ All other text files are chunked by line range. Binary files are skipped.
 
 ---
 
+## FAQ
+
+### Does CCE affect response quality?
+
+No. Quality stays the same or slightly improves.
+
+CCE replaces "dump the entire file" with "search for the relevant function." The model still gets the code it needs (0.90 Recall@10 in benchmarks). Less irrelevant context means less noise competing for attention, which can improve the model's focus on your actual question.
+
+### How does output token savings work?
+
+CCE writes output compression rules directly into your agent's instruction files (`CLAUDE.md`, `AGENTS.md`, `.cursorrules`, etc.) during `cce init`. These rules apply to the **entire session**, not just CCE tool responses, so every reply from the agent follows them.
+
+Set the level in `cce.yaml`:
+
+```yaml
+compression:
+  output: max       # off | lite | standard | max
+```
+
+Then re-run `cce init` to update instruction files. Or change at runtime:
+
+```
+set_output_level output_level=max
+```
+
+| Level | Savings | What it does |
+|-------|---------|--------------|
+| `off` | 0% | No compression |
+| `lite` | ~25% | Removes filler/hedging/pleasantries + diff-only for code changes |
+| `standard` | ~70% | Drops articles, fragments, short synonyms + diff-only for code |
+| `max` | ~80% | Telegraphic style + diff-only for code |
+
+Default is `standard`. All levels include **code output rules** that tell the model to show only changed lines (not full file rewrites), which is where most output tokens go in coding sessions. The `max` level produces very terse prose (similar to "caveman mode"). Code blocks, paths, and commands are never compressed regardless of level.
+
+### Where do the savings come from?
+
+Most savings are **input tokens** (what goes into the model):
+
+| Layer | Type | Typical savings |
+|-------|------|-----------------|
+| Retrieval | Input | 94% (full files → relevant chunks) |
+| Chunk compression | Input | 89% (chunks → signatures) |
+| Grammar compression | Input | 13% (article/filler removal) |
+| Turn summarization | Input | varies (session history) |
+| Progressive disclosure | Input | varies (tool payloads) |
+| Output compression | Output | 25-80% (depends on level) |
+
+Output tokens cost 5x more per token (e.g. Opus: $15/1M input vs $75/1M output), so even a small output reduction has outsized cost impact.
+
+---
+
 ## Roadmap
 
 - [x] Multi-repo benchmarks (FastAPI, chi, fiber)

{code_context_engine-0.4.20 → code_context_engine-0.4.22}/src/code_context_engine.egg-info/SOURCES.txt

@@ -65,6 +65,7 @@ src/context_engine/storage/graph_store.py
 src/context_engine/storage/local_backend.py
 src/context_engine/storage/remote_backend.py
 src/context_engine/storage/vector_store.py
+tests/test_cli_init_agents.py
 tests/test_cli_init_probe.py
 tests/test_cli_mcp_config.py
 tests/test_cli_safe_cwd.py