meshcode 2.11.106__tar.gz → 2.11.107__tar.gz

{meshcode-2.11.106 → meshcode-2.11.107}/PKG-INFO

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

{meshcode-2.11.106 → meshcode-2.11.107}/meshcode/__init__.py

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

{meshcode-2.11.106 → meshcode-2.11.107}/meshcode/meshcode_mcp/server.py

@@ -4030,14 +4030,36 @@ async def meshcode_wait(timeout_seconds: int = 20, include_acks: bool = False) -
     # legacy "no paraba hasta completar todos" cadence. Non-leader
     # agents only — leaders need to stay in wait to triage wildcard
     # tasks for the mesh.
-    if pending_tasks and not _is_leader_agent():
-        # Auto-start the highest priority claimed task so the agent
-        # sees it as in_progress and works it immediately. Samuel
-        # directive: "agents should claim and work right away one by one."
+    # DURABLE-NO-IDLE-SPIN (task 2adb1705): the task-pull short-circuit must
+    # only fire for tasks that still need STARTING (status 'open'). A task
+    # already in_progress by THIS agent means it has been started and is being
+    # worked — or is BLOCKED on an external gate (e.g. a missing credential).
+    # Re-emitting the pull every wait for an in_progress task is exactly the
+    # idle-spin that burned ~45min/148k tokens re-printing "holding". So we
+    # only short-circuit on _tasks_to_start; in_progress tasks fall through to
+    # the normal message-blocking wait (surfaced as a non-blocking reminder).
+    _tasks_to_start = [t for t in (pending_tasks or []) if t.get("status") == "open"]
+    _in_progress_mine = [t for t in (pending_tasks or []) if t.get("status") == "in_progress"]
+    # CHAT-DELIVERY-FIX (2026-06-04, Samuel "fix now"): message delivery MUST take
+    # priority over the task-pull short-circuit. Previously this block returned BEFORE
+    # PRODUCT RULE 2 (below), so any agent holding an OPEN task went DEAF to incoming
+    # messages — never read them, no blue check, the human's chat appeared broken
+    # ("te escribo y no sale palomita azul en nadie"). If there are unread messages,
+    # skip task_pull and fall through to PRODUCT RULE 2 so they get delivered + marked
+    # read first. Task-pull still fires normally when the inbox is empty.
+    _has_unread = False
+    try:
+        _has_unread = bool(be.count_pending(_PROJECT_ID, AGENT_NAME, api_key=_get_api_key()))
+    except Exception:
+        _has_unread = False
+    if _tasks_to_start and not _is_leader_agent() and not _has_unread:
+        # Auto-start the highest priority OPEN task so the agent sees it as
+        # in_progress and works it immediately. Samuel directive: "agents
+        # should claim and work right away one by one."
         _auto_started = None
         _PRIO_ORDER = {"urgent": 0, "high": 1, "normal": 2, "low": 3}
         _sorted_pending = sorted(
-            pending_tasks,
+            _tasks_to_start,
             key=lambda t: (_PRIO_ORDER.get(t.get("priority", "normal"), 2), t.get("id", "")),
         )
         for _pt in _sorted_pending: