Skip to content

CodeNib 0.2.1

CodeNib 0.2.1 makes the source-linked CodeGraph a product path rather than a collection of indexing and MCP primitives. One command now prepares a repository and connects its graph to installed Codex and Claude Code clients:

python -m pip install --upgrade "codenib[graph,mcp]==0.2.1"
codenib codegraph init /absolute/path/to/repository

The path is local and model-free. It detects repository languages, installs the pinned package-managed graph providers those languages need, builds BM25 plus the symbol graph, and delegates MCP registration to each client CLI. The target Git checkout must start clean and is checked again after indexing and registration. The onboarding path never runs a project package manager or build-system preparation step.

Agent workflow

The configured full MCP surface includes explore_context for bounded, source-verified repository context and dependency_subgraph for caller impact, callee dependencies, and dependency neighborhoods. Definition, reference, route, regex, ranked BM25, manifest, and bounded source-read tools remain available for explicit follow-up.

Ask an agent to start with the graph rather than rediscovering the repository:

Use CodeNib's explore_context to locate and explain the implementation, then use dependency_subgraph to check the impact before editing.

Managed lifecycle

Initialization is idempotent. A private receipt below CODENIB_HOME records only registrations CodeNib created. Status verifies the live source identity, both required views, language toolchain, and native client configuration:

codenib codegraph status /absolute/path/to/repository
codenib codegraph status /absolute/path/to/repository --json

Safe uninstall delegates removal back to the clients and preserves the graph index for later reuse:

codenib codegraph uninstall /absolute/path/to/repository

CodeNib does not create .mcp.json, AGENTS.md, or CLAUDE.md. It refuses to overwrite an unmanaged name and refuses to remove a receipt-owned registration whose command has drifted unless the user explicitly passes --force.

Verification

The installed-wheel release gate now installs only the graph and MCP extras, provisions the pinned Python SCIP provider, and exercises the complete product path from outside the source checkout. It proves:

  • first-run and repeated initialization;
  • Codex and Claude Code native-command contracts through isolated client harnesses;
  • a clean target Git checkout;
  • source-verified explore_context output over MCP stdio;
  • a real caller-to-callee dependency_subgraph edge;
  • the browser Dependency Map and its source anchor; and
  • safe client uninstall with the reusable index retained.

The release workflow also continues the Python 3.10 through 3.14 install matrix, Wiki/MCP service smoke, upgrade smoke, sparse Ask, and graph/Dependency Map verification.

Compatibility and upgrade

The existing codenib index, codenib mcp, Wiki, artifact, and registry paths remain available. Existing compatible 0.2 manifests remain reusable; rerunning codegraph init adds any missing BM25 or symbol-graph view and records the client lifecycle without moving repository state.

The CodeGraph command needs the graph and mcp extras. Language-specific system or project prerequisites remain explicit, and --dry-run shows every managed install, index, and client action before it changes state.