meshcode 2.11.27__tar.gz → 2.11.28__tar.gz

{meshcode-2.11.27 → meshcode-2.11.28}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meshcode
-Version: 2.11.27
+Version: 2.11.28
 Summary: Real-time communication between AI agents — Supabase-backed CLI
 Author-email: MeshCode <hello@meshcode.io>
 License: MIT

{meshcode-2.11.27 → meshcode-2.11.28}/meshcode/__init__.py

@@ -1,5 +1,5 @@
 """MeshCode — Real-time communication between AI agents."""
-__version__ = "2.11.27"
+__version__ = "2.11.28"
 
 # Exception hierarchy — eagerly imported (lightweight, no deps)
 from meshcode.exceptions import (  # noqa: F401

{meshcode-2.11.27 → meshcode-2.11.28}/meshcode/meshcode_mcp/server.py

@@ -6104,6 +6104,18 @@ def _auto_update() -> None:
         # legitimate upgrade check. Per task 8d5eed7a.
         os.environ.pop("MESHCODE_UPDATED", None)
         return
+    # MCP-serve guard: this function runs synchronously at the top of
+    # run_server(), BEFORE FastMCP starts serving JSON-RPC. A blocking
+    # `pip install --upgrade` (timeout 60s) here easily blows Claude
+    # Code's MCP handshake window (~5s) — tools never register and the
+    # agent boots into "MCP tools not available". The CLI-side
+    # self_update.py (spawned by `meshcode go` before execv into the
+    # editor) already handles user-facing upgrades; in MCP serve context
+    # we should never block the handshake to chase a newer version.
+    # Detected via the MESHCODE_MCP_SERVE=1 sentinel set in __main__.py.
+    if os.environ.get("MESHCODE_MCP_SERVE") == "1":
+        log.debug("[meshcode] Auto-update skipped in MCP serve subprocess (CLI handles upgrades)")
+        return
 
     # Time-gate (task c0e7de87, 2026-05-19): the PyPI HEAD GET below has a 3s
     # timeout (line ~5430) and pip-install another 60s. Hammering PyPI on

{meshcode-2.11.27 → meshcode-2.11.28}/meshcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meshcode
-Version: 2.11.27
+Version: 2.11.28
 Summary: Real-time communication between AI agents — Supabase-backed CLI
 Author-email: MeshCode <hello@meshcode.io>
 License: MIT

{meshcode-2.11.27 → meshcode-2.11.28}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "meshcode"
-version = "2.11.27"
+version = "2.11.28"
 description = "Real-time communication between AI agents — Supabase-backed CLI"
 readme = "README.md"
 license = {text = "MIT"}

{meshcode-2.11.27 → meshcode-2.11.28}/tests/test_auto_update_hardening.py

@@ -37,12 +37,18 @@ def _check_boot_version_drift_inline():
 
 
 def _auto_update_inline_skeleton():
-    """Subset of _auto_update covering the env-var gates only."""
+    """Subset of _auto_update covering the env-var gates only.
+
+    Order matters: the MCP-serve gate must fire BEFORE any network /
+    pip work so the MCP handshake window is never blocked.
+    """
     if os.environ.get("MESHCODE_AUTO_UPDATE", "1").lower() in ("0", "false", "no"):
         return "disabled"
     if os.environ.get("MESHCODE_UPDATED") == "1":
         os.environ.pop("MESHCODE_UPDATED", None)
         return "post_exec_skip"
+    if os.environ.get("MESHCODE_MCP_SERVE") == "1":
+        return "mcp_serve_skip"
     return "would_check_pypi"
 
 
@@ -114,6 +120,57 @@ def test_auto_update_disabled_case_variants(monkeypatch):
         assert _auto_update_inline_skeleton() == "disabled", f"value {val!r} failed"
 
 
+# ---------------------------------------------------------------------------
+# 3b. MCP-serve gate (added 2026-05-20 / 2.11.28)
+#
+# Symptom: right after publishing 2.11.27, commander agents booted with
+# "MCP meshcode tools are not available" — first-turn deferred-tools list
+# missing all meshcode_* tools. RC: _auto_update runs synchronously at the
+# top of run_server() and does a blocking `pip install --upgrade` (60s
+# timeout). When PyPI advertises a newer version, the install easily
+# exceeds Claude Code's ~5s MCP handshake window and tools never register.
+# Fix: skip _auto_update entirely when MESHCODE_MCP_SERVE=1; the CLI's
+# self_update.py handles user-facing upgrades before execv.
+# ---------------------------------------------------------------------------
+
+def test_mcp_serve_sentinel_skips_update(monkeypatch):
+    monkeypatch.setenv("MESHCODE_MCP_SERVE", "1")
+    monkeypatch.delenv("MESHCODE_AUTO_UPDATE", raising=False)
+    monkeypatch.delenv("MESHCODE_UPDATED", raising=False)
+    assert _auto_update_inline_skeleton() == "mcp_serve_skip"
+
+
+def test_mcp_serve_gate_runs_before_pypi(monkeypatch):
+    """MCP-serve gate must short-circuit before any 'would_check_pypi'
+    branch fires — otherwise the gate is moot because the slow path
+    runs anyway."""
+    monkeypatch.setenv("MESHCODE_MCP_SERVE", "1")
+    monkeypatch.delenv("MESHCODE_AUTO_UPDATE", raising=False)
+    monkeypatch.delenv("MESHCODE_UPDATED", raising=False)
+    assert _auto_update_inline_skeleton() != "would_check_pypi"
+
+
+def test_disabled_still_wins_over_mcp_serve(monkeypatch):
+    """Explicit MESHCODE_AUTO_UPDATE=0 must remain the highest-priority
+    opt-out — useful for CI / debugging where the user wants to be
+    100% certain no pip side-effects fire."""
+    monkeypatch.setenv("MESHCODE_AUTO_UPDATE", "0")
+    monkeypatch.setenv("MESHCODE_MCP_SERVE", "1")
+    monkeypatch.delenv("MESHCODE_UPDATED", raising=False)
+    assert _auto_update_inline_skeleton() == "disabled"
+
+
+def test_post_exec_sentinel_still_wins_over_mcp_serve(monkeypatch):
+    """If we just re-execed after an upgrade, the UPDATED sentinel
+    must still take precedence so it gets cleared (otherwise it
+    persists into subprocess children)."""
+    monkeypatch.setenv("MESHCODE_UPDATED", "1")
+    monkeypatch.setenv("MESHCODE_MCP_SERVE", "1")
+    monkeypatch.delenv("MESHCODE_AUTO_UPDATE", raising=False)
+    assert _auto_update_inline_skeleton() == "post_exec_skip"
+    assert "MESHCODE_UPDATED" not in os.environ
+
+
 # ---------------------------------------------------------------------------
 # 4. PyPI/pip behaviour matrix (mocked — covers the cells that don't need
 #    a live relaunch). Uses an inlined version of the post-gate _auto_update