Skip to content

fix(mcp): first tool call hung on Windows while numpy loaded (2.149.1) #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
drknowhow merged 1 commit into from
Sep 24, 2026
Merged

fix(mcp): first tool call hung on Windows while numpy loaded (2.149.1) #203

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,19 @@ All notable changes to Code Context Control (C3) are documented here.
The format is loosely based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [2.149.1] - 2026-09-24

### Fixed — the first tool call could hang forever on Windows

When a project's embedding index was being built, the `c3-initial-index`
thread loaded numpy's native module (through chromadb) while the server was
starting its other threads. On Windows that deadlocked both, and the first
tool call, or the first `c3_session save`, never answered. The server now
imports numpy on the main thread before any background thread starts (about
75 ms at startup; skipped when numpy is not installed).
`tests/test_codex_mcp_transport.py` went from 0 of 10 passes to 10 of 10 on
the machine that showed it.

## [2.149.0] - 2026-09-24

### Added — the hub launches YOUR agent, not a command named `claude`
Expand Down
2 changes: 1 addition & 1 deletion cli/c3.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@
# Config
CONFIG_DIR = ".c3"
CONFIG_FILE = ".c3/config.json"
__version__ = "2.149.0"
__version__ = "2.149.1"

# The PreToolUse matcher for native subagent calls (installer and hub migration).
AGENT_MATCHER = "Agent|Task"
Expand Down
8 changes: 8 additions & 0 deletions cli/mcp_server.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,6 +192,14 @@ def _notify_mcp_ready(svc) -> None:
async def lifespan(server):
"""Initialize all services, auto-start session, start file watcher."""
project = PROJECT_PATH
# numpy's native module must load before any background thread exists: on
# Windows, loading it from c3-initial-index (via chromadb) while this
# process starts other threads deadlocks both, and the first tool call
# never answers. Absent numpy, nothing here needs it.
try:
import numpy # noqa: F401, PLC0415
except ImportError:
pass
services = build_runtime(project, ide_name=_IDE_NAME)
if getattr(services, "time_tracker", None) is not None:
try:
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"

[project]
name = "code-context-control"
version = "2.149.0"
version = "2.149.1"
description = "Local MCP code-intelligence for AI coding tools: surgical search/read/edit, agent-config version history, path-level access + masking guards, and a multi-project hub."
readme = "README.md"
requires-python = ">=3.10"
Expand Down
Loading