code-context-control 2.28.2__tar.gz → 2.28.3__tar.gz

code_context_control-2.28.3/PKG-INFO

@@ -0,0 +1,331 @@
+Metadata-Version: 2.4
+Name: code-context-control
+Version: 2.28.3
+Summary: Local code-intelligence layer for AI coding tools (Claude Code, Codex, Gemini, Copilot). Retrieve less, read less, edit safer.
+Author-email: Dimitri Tselenchuk <dtselenc@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/drknowhow/code-context-control
+Project-URL: Documentation, https://github.com/drknowhow/code-context-control#readme
+Project-URL: Repository, https://github.com/drknowhow/code-context-control
+Project-URL: Changelog, https://github.com/drknowhow/code-context-control/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/drknowhow/code-context-control/issues
+Keywords: claude,claude-code,mcp,ai,code-intelligence,code-context,developer-tools,llm-tools
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: tiktoken>=0.7.0
+Requires-Dist: fastmcp>=2.0.0
+Requires-Dist: watchdog>=4.0.0
+Requires-Dist: tree-sitter>=0.22.0
+Requires-Dist: tree-sitter-python>=0.21.0
+Requires-Dist: tree-sitter-javascript>=0.21.0
+Requires-Dist: tree-sitter-typescript>=0.21.0
+Requires-Dist: tree-sitter-html>=0.21.0
+Requires-Dist: tree-sitter-markdown>=0.3.2
+Requires-Dist: tree-sitter-css>=0.21.0
+Requires-Dist: tree-sitter-go>=0.21.0
+Requires-Dist: tree-sitter-rust>=0.21.0
+Requires-Dist: tree-sitter-json>=0.21.0
+Requires-Dist: tree-sitter-yaml>=0.6.0
+Requires-Dist: flask>=3.0.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: click>=8.0.0
+Requires-Dist: pyyaml>=6.0.0
+Provides-Extra: vector
+Requires-Dist: scikit-learn>=1.3.0; extra == "vector"
+Requires-Dist: numpy>=1.24.0; extra == "vector"
+Requires-Dist: chromadb>=0.4.24; extra == "vector"
+Provides-Extra: tui
+Requires-Dist: textual>=0.50.0; extra == "tui"
+Provides-Extra: telemetry
+Requires-Dist: sentry-sdk>=2.0.0; extra == "telemetry"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pyright>=1.1.350; extra == "dev"
+Requires-Dist: ruff>=0.6.0; extra == "dev"
+Requires-Dist: build>=1.0.0; extra == "dev"
+Requires-Dist: twine>=5.0.0; extra == "dev"
+Requires-Dist: numpy>=1.24.0; extra == "dev"
+Requires-Dist: scikit-learn>=1.3.0; extra == "dev"
+Dynamic: license-file
+
+<h1 align="center">Code Context Control</h1>
+
+<p align="center">
+  <strong>The local code-intelligence layer for AI coding tools.</strong><br>
+  Stop burning tokens on whole-file reads, blind greps, and unbounded log dumps.<br>
+  Works with Claude Code, Codex, Gemini CLI, Copilot, Cursor, and Antigravity.
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/code-context-control/"><img alt="PyPI" src="https://img.shields.io/pypi/v/code-context-control?color=blue&logo=pypi&logoColor=white"></a>
+  <a href="LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache--2.0-blue.svg"></a>
+  <img alt="Python 3.10+" src="https://img.shields.io/badge/python-3.10%2B-blue.svg">
+  <img alt="Platforms" src="https://img.shields.io/badge/platform-windows%20%7C%20macos%20%7C%20linux-lightgrey">
+  <img alt="Status: Beta" src="https://img.shields.io/badge/status-beta-yellow">
+</p>
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_dashboard.png" alt="C3 per-project dashboard" width="900">
+</p>
+
+---
+
+## The problem
+
+LLM-driven coding tools have one expensive failure mode: **they read too much.** They `cat` whole files, regex the entire repo, dump 10k-line logs into context, edit-and-pray, and burn through budget before they touch a single line of code. On a half-day session you can spend $20+ on token waste that adds zero value.
+
+## What C3 does about it
+
+A thin **local** layer that sits between your IDE and your repo. Every AI tool call gets routed through narrow, surgical operations instead of broad, wasteful ones:
+
+| Without C3 | With C3 |
+|---|---|
+| `Read` the whole 2,000-line file | `c3_compress` returns a 70%-smaller structural map → `c3_read(symbols=...)` for the exact function |
+| `Grep` the whole repo blindly | `c3_search` returns ranked candidates with TF-IDF + symbol awareness |
+| Dump full `pytest` output into the prompt | `c3_filter` distills 500 lines → 30 actionable ones |
+| Edit, hope it compiled | `c3_edit` writes via a ledger + `c3_validate` runs `pyright`/`tsc` automatically |
+| `Bash` test runs that hang on Windows | `c3_shell` returns structured `{exit_code, stdout, stderr, duration}` with auto-filter |
+| Lose all context on `/clear` | `c3_session(snapshot)` + `c3_memory` persist decisions across sessions |
+| Re-explain the project every session | Auto-synced `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` / `copilot-instructions.md` from a single source of truth |
+
+Everything runs **locally**. No source code, prompts, or model output ever leaves your machine unless you explicitly opt into a third-party model API.
+
+---
+
+## Install
+
+Requires Python 3.10+.
+
+```bash
+pip install code-context-control
+c3 init /path/to/your/project
+```
+
+The interactive setup walks you through:
+1. **IDE selection** (Claude Code CLI/App, Codex CLI, Gemini CLI, VS Code, Cursor, Antigravity, or Custom)
+2. Optional local `git init`
+3. MCP server registration (auto-wired into your IDE)
+4. (Claude Code only) Permission tier selection
+
+Headless / scripted install:
+
+```bash
+c3 init /path/to/project --force --ide claude --mcp-mode direct --permissions standard
+```
+
+Or install from source:
+
+```bash
+git clone https://github.com/drknowhow/code-context-control.git
+cd code-context-control
+pip install .[tui]      # add the optional Textual TUI
+```
+
+---
+
+## A tour of the UI
+
+C3 ships with two web UIs (no electron, no install — pure Flask + vanilla JS):
+
+- **The Hub** (`c3-hub`, port 3330) — manage all your C3 projects from one dashboard.
+- **The per-project UI** (`c3 ui`, per-project port) — deep dive into one project's session, memory, edits, instructions, and settings.
+
+### 1. Project Hub — multi-project mission control
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_projects.png" alt="C3 Project Hub - all projects" width="900">
+</p>
+
+Every C3-initialized project on your machine appears here. Group them by tag, filter by active/idle, see which IDE each project uses, jump straight into your IDE with one click, and monitor session activity at a glance. Each project card shows live status, version, MCP wiring mode, port, and last activity.
+
+Same data, grid layout:
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_projects_grid.png" alt="C3 Project Hub - grid view" width="900">
+</p>
+
+**Open in your IDE of choice** — C3 auto-detects which CLIs you have installed and gives you one-click launchers:
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_ide_config.png" alt="C3 Hub IDE picker" width="700">
+</p>
+
+Hub runs as a **background Windows service** if you want it to (no terminal, auto-starts on login):
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_settings.png" alt="C3 Hub settings" width="700">
+</p>
+
+### 2. Per-project dashboard — at-a-glance health
+
+```bash
+c3 ui                             # opens http://127.0.0.1:3333
+```
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_dashboard.png" alt="C3 per-project dashboard" width="900">
+</p>
+
+Real metrics from a real project: **448K tokens saved** (89.9% rate), 208 files indexed, 20 sessions, codebase breakdown by language, current-session live counters (in/out tokens, cache reads, services online), and a stream of recent tool calls and file changes.
+
+### 3. Edit Ledger — every AI-driven edit tracked
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_edits.png" alt="C3 Edit Ledger" width="900">
+</p>
+
+A complete audit trail of every file change made via `c3_edit` (or via Bash git commands intercepted by the C3 shell). Each entry shows timestamp, file, version number, change summary, and +/- line counts. Filter by file path, switch to **Stats** view for aggregate trends. Backed by a content-addressable store so any prior version is one click away.
+
+### 4. Memory — durable knowledge across sessions
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_memory.png" alt="C3 Memory" width="900">
+</p>
+
+A categorized store of facts the AI has learned about your project (architecture decisions, conventions, gotchas, references). Categories, full-text + semantic search, decision tracking, list ↔ graph toggle, and one-click Markdown export. Backed by TF-IDF + optional Ollama embeddings + `chromadb` (when the `[vector]` extra is installed).
+
+### 5. Sessions — history, decisions, costs
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_sessions.png" alt="C3 Sessions" width="900">
+</p>
+
+Every session you've ever run, with duration, decision count, file count, tool calls, token usage, and cost. Captured automatically via the IDE's Stop hook — nothing to remember to click. Click any row to see the full task list, decisions, and file diffs from that session.
+
+### 6. Instructions — sync your project context across IDEs
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_instructions.png" alt="C3 Instructions" width="900">
+</p>
+
+Manage `CLAUDE.md`, `AGENTS.md` (Codex), `GEMINI.md`, and `.github/copilot-instructions.md` from one editor. Generate from project state, run a Health Check (drift detection vs the actual codebase), Compact stale sections, or Promote insights captured during sessions. **One source of truth** instead of four out-of-sync files.
+
+### 7. Chat — browse prior AI conversations
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_chat.png" alt="C3 Chat" width="900">
+</p>
+
+C3 syncs and indexes your IDE's chat transcripts (currently Claude Code; others coming). Filter by source, search, click a row to view the full conversation. Useful for "wait, what did we decide about X last week?".
+
+### 8. Settings — feature flags + integrations
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_settings.png" alt="C3 Settings" width="900">
+</p>
+
+Per-project knobs for everything: budget thresholds, feature flag mode, edit ledger, background agents, delegate routing, Codex/Gemini integrations, agent workflows, proxy mode, MCP servers, Claude Code permission tier, and more.
+
+---
+
+## The MCP tool suite
+
+C3 exposes 14 tools as a native MCP server. Your IDE calls them directly:
+
+| Tool | What it does |
+|---|---|
+| `c3_search` | TF-IDF / regex / semantic search ranked across the indexed repo |
+| `c3_compress` | AST-based file map (modes: `map`, `dense_map`, `smart`, `diff`, `bug_scan`, `ast`) |
+| `c3_read` | Surgical reads — by symbol name, regex, or line ranges |
+| `c3_edit` | Atomic patch with automatic ledger logging + content-addressable history |
+| `c3_validate` | Type / syntax check (pyright, tsc, ruff, etc. — auto-detected) |
+| `c3_filter` | Distill long terminal/log output via pattern + LLM summarization |
+| `c3_shell` | Run shell commands with structured returns + auto-filtered stdout |
+| `c3_status` | Project health, token budget, notifications, ghost-file detection |
+| `c3_memory` | Persistent fact store with categories, recall, and graph queries |
+| `c3_session` | Snapshot, restore, log decisions, compact session history |
+| `c3_impact` | Blast-radius analysis before edits to shared symbols |
+| `c3_delegate` | Offload heavy work to local Ollama / Codex / Gemini / etc. |
+| `c3_agent` | Multi-step agentic workflows (review, investigate, refactor) |
+| `c3_edits` | Edit-ledger queries + version diffs + restore points |
+
+Every tool is **read-only safe in plan mode** (except `c3_edit` and `c3_shell`).
+
+---
+
+## Tiered local AI (optional)
+
+C3 ships with optional Ollama integration so the primary model doesn't have to waste context on grunt work:
+
+| Tier | Model class | Used for | Latency target |
+|---|---|---|---|
+| **Nano** | `qwen2:0.5b` | Intent routing, classification | <100 ms |
+| **Micro** | `deepseek-r1:1.5b` | Last-turn Q&A, summarization | <1 s |
+| **Base** | `llama3.2:3b`+ | Code analysis, technical reasoning | <5 s |
+
+```text
+c3_delegate(task="summarize this 4k-line stacktrace", backend="ollama")
+c3_delegate(task="rate-limit refactor", backend="auto")    # picks the right tier
+```
+
+Ollama is **fully optional**. C3 works without it.
+
+---
+
+## Permissions (Claude Code)
+
+C3 manages `.claude/settings.local.json` for you, with three sensible tiers:
+
+| Tier | What it allows |
+|---|---|
+| `read-only` | Exploration only — no file writes, no git writes, no installs |
+| `standard` | Normal dev workflow — edit, build, test, local git **(recommended)** |
+| `permissive` | Full trust — everything except destructive ops |
+
+All tiers always allow C3 MCP tools and include a hard deny list (`rm -rf`, `sudo`, `git push --force`, etc.).
+
+```bash
+c3 permissions show
+c3 permissions standard
+```
+
+---
+
+## Benchmarks
+
+```bash
+c3 benchmark /path/to/project
+c3 bench aider                    # Aider Polyglot suite
+c3 bench swe                      # SWE-bench Lite
+```
+
+Real-world A/B tests: same task, with and without C3 mounted. Reports include token deltas, cost deltas, win rates, tool-usage analysis, and per-task breakdowns. See the **Benchmark Dashboard** under Settings → Background Agents in the Hub.
+
+---
+
+## Security & privacy
+
+- **Hub binds to `127.0.0.1` by default.** Setting `host` to a non-loopback interface in `~/.c3/hub_config.json` is opt-in and warned at startup. **Do not expose the Hub to a public network without auth/TLS in front of it.**
+- **No telemetry by default.** The OSS package collects nothing. Opt-in Sentry crash reporting requires the `[telemetry]` extra plus both `SENTRY_DSN` and `C3_TELEMETRY_OPT_IN=1`. Even when enabled, request bodies, local variables, and prompts are stripped before sending.
+- **API keys** for third-party model providers are read from environment variables and never persisted by C3.
+- See [`SECURITY.md`](SECURITY.md) for the full hardening guide and disclosure policy.
+
+---
+
+## License
+
+- **Current OSS license** — Apache License 2.0 ([`LICENSE`](LICENSE)). Free for any use, including commercial. Modify, fork, redistribute — all permitted under Apache-2.0 terms.
+- **Third-party deps** — see [`THIRD_PARTY_LICENSES.md`](THIRD_PARTY_LICENSES.md).
+
+The author may introduce a paid offering or relicense future major versions; no commitment either way. Releases already published under Apache-2.0 (including all 2.x versions) keep their Apache-2.0 grant — that grant is irrevocable. Background and FAQ in [`LICENSING.md`](LICENSING.md). No warranty or support obligation; see LICENSE Sections 7–8.
+
+---
+
+## Links
+
+- **PyPI:** https://pypi.org/project/code-context-control/
+- **Changelog:** [`CHANGELOG.md`](CHANGELOG.md)
+- **Security policy:** [`SECURITY.md`](SECURITY.md)
+- **Licensing FAQ:** [`LICENSING.md`](LICENSING.md)
+- **Issues:** https://github.com/drknowhow/code-context-control/issues

code_context_control-2.28.3/README.md

@@ -0,0 +1,270 @@
+<h1 align="center">Code Context Control</h1>
+
+<p align="center">
+  <strong>The local code-intelligence layer for AI coding tools.</strong><br>
+  Stop burning tokens on whole-file reads, blind greps, and unbounded log dumps.<br>
+  Works with Claude Code, Codex, Gemini CLI, Copilot, Cursor, and Antigravity.
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/code-context-control/"><img alt="PyPI" src="https://img.shields.io/pypi/v/code-context-control?color=blue&logo=pypi&logoColor=white"></a>
+  <a href="LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache--2.0-blue.svg"></a>
+  <img alt="Python 3.10+" src="https://img.shields.io/badge/python-3.10%2B-blue.svg">
+  <img alt="Platforms" src="https://img.shields.io/badge/platform-windows%20%7C%20macos%20%7C%20linux-lightgrey">
+  <img alt="Status: Beta" src="https://img.shields.io/badge/status-beta-yellow">
+</p>
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_dashboard.png" alt="C3 per-project dashboard" width="900">
+</p>
+
+---
+
+## The problem
+
+LLM-driven coding tools have one expensive failure mode: **they read too much.** They `cat` whole files, regex the entire repo, dump 10k-line logs into context, edit-and-pray, and burn through budget before they touch a single line of code. On a half-day session you can spend $20+ on token waste that adds zero value.
+
+## What C3 does about it
+
+A thin **local** layer that sits between your IDE and your repo. Every AI tool call gets routed through narrow, surgical operations instead of broad, wasteful ones:
+
+| Without C3 | With C3 |
+|---|---|
+| `Read` the whole 2,000-line file | `c3_compress` returns a 70%-smaller structural map → `c3_read(symbols=...)` for the exact function |
+| `Grep` the whole repo blindly | `c3_search` returns ranked candidates with TF-IDF + symbol awareness |
+| Dump full `pytest` output into the prompt | `c3_filter` distills 500 lines → 30 actionable ones |
+| Edit, hope it compiled | `c3_edit` writes via a ledger + `c3_validate` runs `pyright`/`tsc` automatically |
+| `Bash` test runs that hang on Windows | `c3_shell` returns structured `{exit_code, stdout, stderr, duration}` with auto-filter |
+| Lose all context on `/clear` | `c3_session(snapshot)` + `c3_memory` persist decisions across sessions |
+| Re-explain the project every session | Auto-synced `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` / `copilot-instructions.md` from a single source of truth |
+
+Everything runs **locally**. No source code, prompts, or model output ever leaves your machine unless you explicitly opt into a third-party model API.
+
+---
+
+## Install
+
+Requires Python 3.10+.
+
+```bash
+pip install code-context-control
+c3 init /path/to/your/project
+```
+
+The interactive setup walks you through:
+1. **IDE selection** (Claude Code CLI/App, Codex CLI, Gemini CLI, VS Code, Cursor, Antigravity, or Custom)
+2. Optional local `git init`
+3. MCP server registration (auto-wired into your IDE)
+4. (Claude Code only) Permission tier selection
+
+Headless / scripted install:
+
+```bash
+c3 init /path/to/project --force --ide claude --mcp-mode direct --permissions standard
+```
+
+Or install from source:
+
+```bash
+git clone https://github.com/drknowhow/code-context-control.git
+cd code-context-control
+pip install .[tui]      # add the optional Textual TUI
+```
+
+---
+
+## A tour of the UI
+
+C3 ships with two web UIs (no electron, no install — pure Flask + vanilla JS):
+
+- **The Hub** (`c3-hub`, port 3330) — manage all your C3 projects from one dashboard.
+- **The per-project UI** (`c3 ui`, per-project port) — deep dive into one project's session, memory, edits, instructions, and settings.
+
+### 1. Project Hub — multi-project mission control
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_projects.png" alt="C3 Project Hub - all projects" width="900">
+</p>
+
+Every C3-initialized project on your machine appears here. Group them by tag, filter by active/idle, see which IDE each project uses, jump straight into your IDE with one click, and monitor session activity at a glance. Each project card shows live status, version, MCP wiring mode, port, and last activity.
+
+Same data, grid layout:
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_projects_grid.png" alt="C3 Project Hub - grid view" width="900">
+</p>
+
+**Open in your IDE of choice** — C3 auto-detects which CLIs you have installed and gives you one-click launchers:
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_ide_config.png" alt="C3 Hub IDE picker" width="700">
+</p>
+
+Hub runs as a **background Windows service** if you want it to (no terminal, auto-starts on login):
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/hub_settings.png" alt="C3 Hub settings" width="700">
+</p>
+
+### 2. Per-project dashboard — at-a-glance health
+
+```bash
+c3 ui                             # opens http://127.0.0.1:3333
+```
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_dashboard.png" alt="C3 per-project dashboard" width="900">
+</p>
+
+Real metrics from a real project: **448K tokens saved** (89.9% rate), 208 files indexed, 20 sessions, codebase breakdown by language, current-session live counters (in/out tokens, cache reads, services online), and a stream of recent tool calls and file changes.
+
+### 3. Edit Ledger — every AI-driven edit tracked
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_edits.png" alt="C3 Edit Ledger" width="900">
+</p>
+
+A complete audit trail of every file change made via `c3_edit` (or via Bash git commands intercepted by the C3 shell). Each entry shows timestamp, file, version number, change summary, and +/- line counts. Filter by file path, switch to **Stats** view for aggregate trends. Backed by a content-addressable store so any prior version is one click away.
+
+### 4. Memory — durable knowledge across sessions
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_memory.png" alt="C3 Memory" width="900">
+</p>
+
+A categorized store of facts the AI has learned about your project (architecture decisions, conventions, gotchas, references). Categories, full-text + semantic search, decision tracking, list ↔ graph toggle, and one-click Markdown export. Backed by TF-IDF + optional Ollama embeddings + `chromadb` (when the `[vector]` extra is installed).
+
+### 5. Sessions — history, decisions, costs
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_sessions.png" alt="C3 Sessions" width="900">
+</p>
+
+Every session you've ever run, with duration, decision count, file count, tool calls, token usage, and cost. Captured automatically via the IDE's Stop hook — nothing to remember to click. Click any row to see the full task list, decisions, and file diffs from that session.
+
+### 6. Instructions — sync your project context across IDEs
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_instructions.png" alt="C3 Instructions" width="900">
+</p>
+
+Manage `CLAUDE.md`, `AGENTS.md` (Codex), `GEMINI.md`, and `.github/copilot-instructions.md` from one editor. Generate from project state, run a Health Check (drift detection vs the actual codebase), Compact stale sections, or Promote insights captured during sessions. **One source of truth** instead of four out-of-sync files.
+
+### 7. Chat — browse prior AI conversations
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_chat.png" alt="C3 Chat" width="900">
+</p>
+
+C3 syncs and indexes your IDE's chat transcripts (currently Claude Code; others coming). Filter by source, search, click a row to view the full conversation. Useful for "wait, what did we decide about X last week?".
+
+### 8. Settings — feature flags + integrations
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/drknowhow/code-context-control/main/docs/screenshots/ui_settings.png" alt="C3 Settings" width="900">
+</p>
+
+Per-project knobs for everything: budget thresholds, feature flag mode, edit ledger, background agents, delegate routing, Codex/Gemini integrations, agent workflows, proxy mode, MCP servers, Claude Code permission tier, and more.
+
+---
+
+## The MCP tool suite
+
+C3 exposes 14 tools as a native MCP server. Your IDE calls them directly:
+
+| Tool | What it does |
+|---|---|
+| `c3_search` | TF-IDF / regex / semantic search ranked across the indexed repo |
+| `c3_compress` | AST-based file map (modes: `map`, `dense_map`, `smart`, `diff`, `bug_scan`, `ast`) |
+| `c3_read` | Surgical reads — by symbol name, regex, or line ranges |
+| `c3_edit` | Atomic patch with automatic ledger logging + content-addressable history |
+| `c3_validate` | Type / syntax check (pyright, tsc, ruff, etc. — auto-detected) |
+| `c3_filter` | Distill long terminal/log output via pattern + LLM summarization |
+| `c3_shell` | Run shell commands with structured returns + auto-filtered stdout |
+| `c3_status` | Project health, token budget, notifications, ghost-file detection |
+| `c3_memory` | Persistent fact store with categories, recall, and graph queries |
+| `c3_session` | Snapshot, restore, log decisions, compact session history |
+| `c3_impact` | Blast-radius analysis before edits to shared symbols |
+| `c3_delegate` | Offload heavy work to local Ollama / Codex / Gemini / etc. |
+| `c3_agent` | Multi-step agentic workflows (review, investigate, refactor) |
+| `c3_edits` | Edit-ledger queries + version diffs + restore points |
+
+Every tool is **read-only safe in plan mode** (except `c3_edit` and `c3_shell`).
+
+---
+
+## Tiered local AI (optional)
+
+C3 ships with optional Ollama integration so the primary model doesn't have to waste context on grunt work:
+
+| Tier | Model class | Used for | Latency target |
+|---|---|---|---|
+| **Nano** | `qwen2:0.5b` | Intent routing, classification | <100 ms |
+| **Micro** | `deepseek-r1:1.5b` | Last-turn Q&A, summarization | <1 s |
+| **Base** | `llama3.2:3b`+ | Code analysis, technical reasoning | <5 s |
+
+```text
+c3_delegate(task="summarize this 4k-line stacktrace", backend="ollama")
+c3_delegate(task="rate-limit refactor", backend="auto")    # picks the right tier
+```
+
+Ollama is **fully optional**. C3 works without it.
+
+---
+
+## Permissions (Claude Code)
+
+C3 manages `.claude/settings.local.json` for you, with three sensible tiers:
+
+| Tier | What it allows |
+|---|---|
+| `read-only` | Exploration only — no file writes, no git writes, no installs |
+| `standard` | Normal dev workflow — edit, build, test, local git **(recommended)** |
+| `permissive` | Full trust — everything except destructive ops |
+
+All tiers always allow C3 MCP tools and include a hard deny list (`rm -rf`, `sudo`, `git push --force`, etc.).
+
+```bash
+c3 permissions show
+c3 permissions standard
+```
+
+---
+
+## Benchmarks
+
+```bash
+c3 benchmark /path/to/project
+c3 bench aider                    # Aider Polyglot suite
+c3 bench swe                      # SWE-bench Lite
+```
+
+Real-world A/B tests: same task, with and without C3 mounted. Reports include token deltas, cost deltas, win rates, tool-usage analysis, and per-task breakdowns. See the **Benchmark Dashboard** under Settings → Background Agents in the Hub.
+
+---
+
+## Security & privacy
+
+- **Hub binds to `127.0.0.1` by default.** Setting `host` to a non-loopback interface in `~/.c3/hub_config.json` is opt-in and warned at startup. **Do not expose the Hub to a public network without auth/TLS in front of it.**
+- **No telemetry by default.** The OSS package collects nothing. Opt-in Sentry crash reporting requires the `[telemetry]` extra plus both `SENTRY_DSN` and `C3_TELEMETRY_OPT_IN=1`. Even when enabled, request bodies, local variables, and prompts are stripped before sending.
+- **API keys** for third-party model providers are read from environment variables and never persisted by C3.
+- See [`SECURITY.md`](SECURITY.md) for the full hardening guide and disclosure policy.
+
+---
+
+## License
+
+- **Current OSS license** — Apache License 2.0 ([`LICENSE`](LICENSE)). Free for any use, including commercial. Modify, fork, redistribute — all permitted under Apache-2.0 terms.
+- **Third-party deps** — see [`THIRD_PARTY_LICENSES.md`](THIRD_PARTY_LICENSES.md).
+
+The author may introduce a paid offering or relicense future major versions; no commitment either way. Releases already published under Apache-2.0 (including all 2.x versions) keep their Apache-2.0 grant — that grant is irrevocable. Background and FAQ in [`LICENSING.md`](LICENSING.md). No warranty or support obligation; see LICENSE Sections 7–8.
+
+---
+
+## Links
+
+- **PyPI:** https://pypi.org/project/code-context-control/
+- **Changelog:** [`CHANGELOG.md`](CHANGELOG.md)
+- **Security policy:** [`SECURITY.md`](SECURITY.md)
+- **Licensing FAQ:** [`LICENSING.md`](LICENSING.md)
+- **Issues:** https://github.com/drknowhow/code-context-control/issues

{code_context_control-2.28.2 → code_context_control-2.28.3}/cli/c3.py

@@ -85,7 +85,7 @@ console = Console() if HAS_RICH else None
 # Config
 CONFIG_DIR = ".c3"
 CONFIG_FILE = ".c3/config.json"
-__version__ = "2.28.2"
+__version__ = "2.28.3"
 
 
 def _command_deps() -> CommandDeps: