codecortex 0.19.0__tar.gz → 0.20.0__tar.gz

{codecortex-0.19.0/src/codecortex.egg-info → codecortex-0.20.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codecortex
-Version: 0.19.0
+Version: 0.20.0
 Summary: Local-first, MCP-native code-intelligence server — graph, LSP, and semantic search behind one safe code.query tool for coding agents.
 Author: Shammai Hamilton
 License-Expression: MIT
@@ -61,7 +61,7 @@ Prefer plain text? `codeintel map` writes a **readable architecture overview** t
 
 **What `CODE_INTEL.md` is for.** It's a *static, committable* snapshot of a codebase's shape — meant to be read (by a person or an agent) **first**, instead of reconstructing structure by grepping. It covers the cases the live `code.query` tool doesn't:
 
-- **Agents & hosts that don't speak MCP.** Not every agent supports MCP, and the server isn't always running. `codeintel map` writes a plain file any agent can read; `codeintel map --inject` also drops a pointer into `CLAUDE.md` / `AGENTS.md`, so an agent picks up the codebase's structure automatically at the start of a session.
+- **Agents & hosts that don't speak MCP.** Not every agent supports MCP, and the server isn't always running. `codeintel map` writes a plain file any agent can read; `codeintel map --inject` also drops a short, tool-naming pointer block into `AGENTS.md` (the cross-tool surface read by Codex, Cursor, Zed, and others — created with your consent if it doesn't exist yet) plus a one-line `@AGENTS.md` import into `CLAUDE.md`, and writes the fuller [`USING_CODEINTEL.md`](USING_CODEINTEL.md) guide the block points to — so an agent knows to reach for `code.query` before it reaches for grep, not just that a `CODE_INTEL.md` exists.
 - **A committed, diffable overview.** It lives *in the repo* — reviewable in a PR, browsable on GitHub, available offline. Re-run `codeintel map` after `codeintel index` to refresh it.
 - **The load-bearing code at a glance.** Ranking symbols by caller count surfaces what most of the codebase depends on (the risky-to-change core) plus the entry points — the first things a newcomer, or an agent, should understand before touching anything.
 
@@ -78,6 +78,8 @@ Without structural tools, an agent dropped into unfamiliar code falls back on `g
 
 Net effect: fewer, sharper tool calls, less re-reading, and an agent that can see *structure* — callers, impact, call chains — that plain search can't.
 
+**The honest framing.** Agentic grep is still the backbone, and codeintel doesn't claim otherwise — Claude Code itself ships grep-only and that is a reasonable default for most of what an agent reads. The defensible claim is narrower: a structural index *where it pays*, degrading to grep the moment an engine is missing or not indexed, which is exactly what the safe-null contract above already does under the hood. Worth saying explicitly rather than leaving it implicit in a failure mode.
+
 ## What your agent can ask
 
 It's one call: `code.query(op, target, engine="auto")`. In `auto` mode (the default) codeintel picks the engine per operation:
@@ -279,7 +281,7 @@ Then it launches the exact command it registered and drives a real MCP handshake
 ```text
 v claude: registered at /Users/you/.claude.json
 
-v verified: codeintel 0.19.0 — 4 tools (code.query, code.status, code.doctor, code.map)
+v verified: codeintel 0.20.0 — 4 tools (code.query, code.status, code.doctor, code.map)
 ```
 
 If the command is not on `PATH`, or the server fails to start, install says so and exits non-zero
@@ -463,7 +465,22 @@ Config is **validated on load** — an out-of-range number, a misspelled enum, o
 
 Not sure what's installed? `codeintel doctor` reports exactly which backends are present, whether this repo is indexed, and the command to fix each gap.
 
-**The only network touch is first-run setup:** `fastembed` downloads the `BAAI/bge-small-en-v1.5` weights once (cached under `~/.cache`, fully offline thereafter); the optional backends also install on first use *if you opt in*. After that, **no code or data leaves your machine** — which is what makes `--engine all` safe to run on a private repo.
+**The only network touch is first-run setup:** `fastembed` downloads the `BAAI/bge-small-en-v1.5`
+weights once — cached under `fastembed`'s own default (`$TMPDIR/fastembed_cache`, **not**
+`~/.cache`; override with `FASTEMBED_CACHE_PATH` for a location that survives a `/tmp` cleanup),
+fully offline thereafter; the optional backends also install on first use *if you opt in*. After
+that, **no code or data leaves your machine** — which is what makes `--engine all` safe to run on
+a private repo. Behind a proxy or fully air-gapped, this download is the one step that can fail —
+see [Offline / air-gapped install](docs/install.md#offline--air-gapped-install) for a documented
+workaround.
+
+**What codeintel writes to disk.** `~/.codeintel/semantic.db` is a **single file shared across
+every repo you've ever indexed** with this machine's default embedding model (rows are
+partitioned internally by repo) — 239 MB was observed here after indexing a handful of repos.
+`codeintel reset <repo>` clears that repo's rows but does not shrink the file (SQLite doesn't
+reclaim space without a `VACUUM`); `codeintel reset --all` removes the file outright. Separately,
+the **LSP** engine's backend (serena) writes a `.serena/` directory *into each project you index*
+— add it to that project's `.gitignore` (codeintel's own repo does).
 
 ## For agents
 
@@ -584,6 +601,16 @@ engines safe-null and you get a fraction of the capability table above. `codeint
 installs what it can and `codeintel doctor` tells you exactly what is missing and how to fix it.
 Run `doctor` first if the tool seems quieter than the docs suggest.
 
+**The graph backend is the closest competitor, and it should be named as one.**
+`codebase-memory-mcp` already ships semantic vector search, hybrid LSP type resolution, impact
+analysis, and auto-registration with several agents on its own. A user who installs it alone gets
+most of this project's capability table with less setup. The marginal value of codeintel over its
+own backend is the unification, the safe-null contract, and the LSP merge — one call across three
+engines instead of three separate tools to learn, a never-raise contract enforced by
+fault-injection tests rather than convention, and answers that merge graph structure with exact
+LSP locations instead of picking one. That's real and defensible, and considerably narrower than
+"three engines" makes it sound.
+
 **Maintenance.** One maintainer, MIT licensed, issues and PRs welcome. There is no support
 guarantee — factor that into anything load-bearing.
 

{codecortex-0.19.0 → codecortex-0.20.0}/README.md

@@ -24,7 +24,7 @@ Prefer plain text? `codeintel map` writes a **readable architecture overview** t
 
 **What `CODE_INTEL.md` is for.** It's a *static, committable* snapshot of a codebase's shape — meant to be read (by a person or an agent) **first**, instead of reconstructing structure by grepping. It covers the cases the live `code.query` tool doesn't:
 
-- **Agents & hosts that don't speak MCP.** Not every agent supports MCP, and the server isn't always running. `codeintel map` writes a plain file any agent can read; `codeintel map --inject` also drops a pointer into `CLAUDE.md` / `AGENTS.md`, so an agent picks up the codebase's structure automatically at the start of a session.
+- **Agents & hosts that don't speak MCP.** Not every agent supports MCP, and the server isn't always running. `codeintel map` writes a plain file any agent can read; `codeintel map --inject` also drops a short, tool-naming pointer block into `AGENTS.md` (the cross-tool surface read by Codex, Cursor, Zed, and others — created with your consent if it doesn't exist yet) plus a one-line `@AGENTS.md` import into `CLAUDE.md`, and writes the fuller [`USING_CODEINTEL.md`](USING_CODEINTEL.md) guide the block points to — so an agent knows to reach for `code.query` before it reaches for grep, not just that a `CODE_INTEL.md` exists.
 - **A committed, diffable overview.** It lives *in the repo* — reviewable in a PR, browsable on GitHub, available offline. Re-run `codeintel map` after `codeintel index` to refresh it.
 - **The load-bearing code at a glance.** Ranking symbols by caller count surfaces what most of the codebase depends on (the risky-to-change core) plus the entry points — the first things a newcomer, or an agent, should understand before touching anything.
 
@@ -41,6 +41,8 @@ Without structural tools, an agent dropped into unfamiliar code falls back on `g
 
 Net effect: fewer, sharper tool calls, less re-reading, and an agent that can see *structure* — callers, impact, call chains — that plain search can't.
 
+**The honest framing.** Agentic grep is still the backbone, and codeintel doesn't claim otherwise — Claude Code itself ships grep-only and that is a reasonable default for most of what an agent reads. The defensible claim is narrower: a structural index *where it pays*, degrading to grep the moment an engine is missing or not indexed, which is exactly what the safe-null contract above already does under the hood. Worth saying explicitly rather than leaving it implicit in a failure mode.
+
 ## What your agent can ask
 
 It's one call: `code.query(op, target, engine="auto")`. In `auto` mode (the default) codeintel picks the engine per operation:
@@ -242,7 +244,7 @@ Then it launches the exact command it registered and drives a real MCP handshake
 ```text
 v claude: registered at /Users/you/.claude.json
 
-v verified: codeintel 0.19.0 — 4 tools (code.query, code.status, code.doctor, code.map)
+v verified: codeintel 0.20.0 — 4 tools (code.query, code.status, code.doctor, code.map)
 ```
 
 If the command is not on `PATH`, or the server fails to start, install says so and exits non-zero
@@ -426,7 +428,22 @@ Config is **validated on load** — an out-of-range number, a misspelled enum, o
 
 Not sure what's installed? `codeintel doctor` reports exactly which backends are present, whether this repo is indexed, and the command to fix each gap.
 
-**The only network touch is first-run setup:** `fastembed` downloads the `BAAI/bge-small-en-v1.5` weights once (cached under `~/.cache`, fully offline thereafter); the optional backends also install on first use *if you opt in*. After that, **no code or data leaves your machine** — which is what makes `--engine all` safe to run on a private repo.
+**The only network touch is first-run setup:** `fastembed` downloads the `BAAI/bge-small-en-v1.5`
+weights once — cached under `fastembed`'s own default (`$TMPDIR/fastembed_cache`, **not**
+`~/.cache`; override with `FASTEMBED_CACHE_PATH` for a location that survives a `/tmp` cleanup),
+fully offline thereafter; the optional backends also install on first use *if you opt in*. After
+that, **no code or data leaves your machine** — which is what makes `--engine all` safe to run on
+a private repo. Behind a proxy or fully air-gapped, this download is the one step that can fail —
+see [Offline / air-gapped install](docs/install.md#offline--air-gapped-install) for a documented
+workaround.
+
+**What codeintel writes to disk.** `~/.codeintel/semantic.db` is a **single file shared across
+every repo you've ever indexed** with this machine's default embedding model (rows are
+partitioned internally by repo) — 239 MB was observed here after indexing a handful of repos.
+`codeintel reset <repo>` clears that repo's rows but does not shrink the file (SQLite doesn't
+reclaim space without a `VACUUM`); `codeintel reset --all` removes the file outright. Separately,
+the **LSP** engine's backend (serena) writes a `.serena/` directory *into each project you index*
+— add it to that project's `.gitignore` (codeintel's own repo does).
 
 ## For agents
 
@@ -547,6 +564,16 @@ engines safe-null and you get a fraction of the capability table above. `codeint
 installs what it can and `codeintel doctor` tells you exactly what is missing and how to fix it.
 Run `doctor` first if the tool seems quieter than the docs suggest.
 
+**The graph backend is the closest competitor, and it should be named as one.**
+`codebase-memory-mcp` already ships semantic vector search, hybrid LSP type resolution, impact
+analysis, and auto-registration with several agents on its own. A user who installs it alone gets
+most of this project's capability table with less setup. The marginal value of codeintel over its
+own backend is the unification, the safe-null contract, and the LSP merge — one call across three
+engines instead of three separate tools to learn, a never-raise contract enforced by
+fault-injection tests rather than convention, and answers that merge graph structure with exact
+LSP locations instead of picking one. That's real and defensible, and considerably narrower than
+"three engines" makes it sound.
+
 **Maintenance.** One maintainer, MIT licensed, issues and PRs welcome. There is no support
 guarantee — factor that into anything load-bearing.
 

{codecortex-0.19.0 → codecortex-0.20.0/src/codecortex.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codecortex
-Version: 0.19.0
+Version: 0.20.0
 Summary: Local-first, MCP-native code-intelligence server — graph, LSP, and semantic search behind one safe code.query tool for coding agents.
 Author: Shammai Hamilton
 License-Expression: MIT
@@ -61,7 +61,7 @@ Prefer plain text? `codeintel map` writes a **readable architecture overview** t
 
 **What `CODE_INTEL.md` is for.** It's a *static, committable* snapshot of a codebase's shape — meant to be read (by a person or an agent) **first**, instead of reconstructing structure by grepping. It covers the cases the live `code.query` tool doesn't:
 
-- **Agents & hosts that don't speak MCP.** Not every agent supports MCP, and the server isn't always running. `codeintel map` writes a plain file any agent can read; `codeintel map --inject` also drops a pointer into `CLAUDE.md` / `AGENTS.md`, so an agent picks up the codebase's structure automatically at the start of a session.
+- **Agents & hosts that don't speak MCP.** Not every agent supports MCP, and the server isn't always running. `codeintel map` writes a plain file any agent can read; `codeintel map --inject` also drops a short, tool-naming pointer block into `AGENTS.md` (the cross-tool surface read by Codex, Cursor, Zed, and others — created with your consent if it doesn't exist yet) plus a one-line `@AGENTS.md` import into `CLAUDE.md`, and writes the fuller [`USING_CODEINTEL.md`](USING_CODEINTEL.md) guide the block points to — so an agent knows to reach for `code.query` before it reaches for grep, not just that a `CODE_INTEL.md` exists.
 - **A committed, diffable overview.** It lives *in the repo* — reviewable in a PR, browsable on GitHub, available offline. Re-run `codeintel map` after `codeintel index` to refresh it.
 - **The load-bearing code at a glance.** Ranking symbols by caller count surfaces what most of the codebase depends on (the risky-to-change core) plus the entry points — the first things a newcomer, or an agent, should understand before touching anything.
 
@@ -78,6 +78,8 @@ Without structural tools, an agent dropped into unfamiliar code falls back on `g
 
 Net effect: fewer, sharper tool calls, less re-reading, and an agent that can see *structure* — callers, impact, call chains — that plain search can't.
 
+**The honest framing.** Agentic grep is still the backbone, and codeintel doesn't claim otherwise — Claude Code itself ships grep-only and that is a reasonable default for most of what an agent reads. The defensible claim is narrower: a structural index *where it pays*, degrading to grep the moment an engine is missing or not indexed, which is exactly what the safe-null contract above already does under the hood. Worth saying explicitly rather than leaving it implicit in a failure mode.
+
 ## What your agent can ask
 
 It's one call: `code.query(op, target, engine="auto")`. In `auto` mode (the default) codeintel picks the engine per operation:
@@ -279,7 +281,7 @@ Then it launches the exact command it registered and drives a real MCP handshake
 ```text
 v claude: registered at /Users/you/.claude.json
 
-v verified: codeintel 0.19.0 — 4 tools (code.query, code.status, code.doctor, code.map)
+v verified: codeintel 0.20.0 — 4 tools (code.query, code.status, code.doctor, code.map)
 ```
 
 If the command is not on `PATH`, or the server fails to start, install says so and exits non-zero
@@ -463,7 +465,22 @@ Config is **validated on load** — an out-of-range number, a misspelled enum, o
 
 Not sure what's installed? `codeintel doctor` reports exactly which backends are present, whether this repo is indexed, and the command to fix each gap.
 
-**The only network touch is first-run setup:** `fastembed` downloads the `BAAI/bge-small-en-v1.5` weights once (cached under `~/.cache`, fully offline thereafter); the optional backends also install on first use *if you opt in*. After that, **no code or data leaves your machine** — which is what makes `--engine all` safe to run on a private repo.
+**The only network touch is first-run setup:** `fastembed` downloads the `BAAI/bge-small-en-v1.5`
+weights once — cached under `fastembed`'s own default (`$TMPDIR/fastembed_cache`, **not**
+`~/.cache`; override with `FASTEMBED_CACHE_PATH` for a location that survives a `/tmp` cleanup),
+fully offline thereafter; the optional backends also install on first use *if you opt in*. After
+that, **no code or data leaves your machine** — which is what makes `--engine all` safe to run on
+a private repo. Behind a proxy or fully air-gapped, this download is the one step that can fail —
+see [Offline / air-gapped install](docs/install.md#offline--air-gapped-install) for a documented
+workaround.
+
+**What codeintel writes to disk.** `~/.codeintel/semantic.db` is a **single file shared across
+every repo you've ever indexed** with this machine's default embedding model (rows are
+partitioned internally by repo) — 239 MB was observed here after indexing a handful of repos.
+`codeintel reset <repo>` clears that repo's rows but does not shrink the file (SQLite doesn't
+reclaim space without a `VACUUM`); `codeintel reset --all` removes the file outright. Separately,
+the **LSP** engine's backend (serena) writes a `.serena/` directory *into each project you index*
+— add it to that project's `.gitignore` (codeintel's own repo does).
 
 ## For agents
 
@@ -584,6 +601,16 @@ engines safe-null and you get a fraction of the capability table above. `codeint
 installs what it can and `codeintel doctor` tells you exactly what is missing and how to fix it.
 Run `doctor` first if the tool seems quieter than the docs suggest.
 
+**The graph backend is the closest competitor, and it should be named as one.**
+`codebase-memory-mcp` already ships semantic vector search, hybrid LSP type resolution, impact
+analysis, and auto-registration with several agents on its own. A user who installs it alone gets
+most of this project's capability table with less setup. The marginal value of codeintel over its
+own backend is the unification, the safe-null contract, and the LSP merge — one call across three
+engines instead of three separate tools to learn, a never-raise contract enforced by
+fault-injection tests rather than convention, and answers that merge graph structure with exact
+LSP locations instead of picking one. That's real and defensible, and considerably narrower than
+"three engines" makes it sound.
+
 **Maintenance.** One maintainer, MIT licensed, issues and PRs welcome. There is no support
 guarantee — factor that into anything load-bearing.
 

{codecortex-0.19.0 → codecortex-0.20.0}/src/codecortex.egg-info/SOURCES.txt

@@ -36,6 +36,7 @@ src/codeintel/policy.py
 src/codeintel/progress.py
 src/codeintel/provider.py
 src/codeintel/py.typed
+src/codeintel/query_ops.py
 src/codeintel/redact.py
 src/codeintel/reindexer.py
 src/codeintel/reset.py
@@ -77,6 +78,8 @@ tests/test_cache.py
 tests/test_chunking.py
 tests/test_cli_commands.py
 tests/test_cli_help.py
+tests/test_cli_install_dry_run.py
+tests/test_cli_install_offer_injection.py
 tests/test_cold_process.py
 tests/test_config.py
 tests/test_corpus.py
@@ -84,6 +87,7 @@ tests/test_docs_ci_claims.py
 tests/test_docs_deadcode_withdrawal.py
 tests/test_doctor.py
 tests/test_e2e.py
+tests/test_edge_confidence.py
 tests/test_engine_adoption.py
 tests/test_enterprise.py
 tests/test_gateway.py
@@ -101,6 +105,7 @@ tests/test_indexer_binary.py
 tests/test_installer.py
 tests/test_integration.py
 tests/test_loc_census.py
+tests/test_lsp_language_coverage.py
 tests/test_lsp_provider.py
 tests/test_lsp_real.py
 tests/test_mapper.py
@@ -108,6 +113,7 @@ tests/test_mcp_handshake.py
 tests/test_mcp_server.py
 tests/test_model_dimension.py
 tests/test_never_raise.py
+tests/test_null_reason_and_ripple.py
 tests/test_onboarding.py
 tests/test_rbac.py
 tests/test_redaction_boundary.py

codecortex-0.20.0/src/codeintel/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.20.0"