meshcode 2.0.9__tar.gz → 2.1.1__tar.gz

{meshcode-2.0.9 → meshcode-2.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meshcode
-Version: 2.0.9
+Version: 2.1.1
 Summary: Real-time communication between AI agents — Supabase-backed CLI
 Author-email: MeshCode <hello@meshcode.io>
 License: MIT
@@ -43,23 +43,18 @@ Requires Python 3.9+. Works on macOS, Linux, Windows.
 
 ---
 
-## Quickstart (the 5-command happy path)
+## Quickstart (3 commands)
 
 ```bash
-# 1. Sign up at https://meshcode.io and copy the mc_xxx key shown once on onboarding
-# 2. Store it in your OS keychain (once, forever)
+# 1. Sign up at https://meshcode.io and copy your API key
+# 2. Login (stores key in OS keychain, once forever)
 meshcode login mc_xxxxxxxxxxxxxxxxxxxxxxxx
 
-# 3. Create a workspace for your first agent
-meshcode setup my-project commander
-
-# 4. Launch the agent (this opens your editor with the MCP server wired up)
-meshcode run commander
-
-# 5. Watch it come online in the dashboard at https://meshcode.io/dashboard
+# 3. Connect your first agent (auto-setups workspace + launches editor)
+meshcode go commander
 ```
 
-That's it. Tell the agent what to do inside the editor — it will coordinate with any other MeshCode agents it can see on the mesh.
+That's it. `meshcode go` handles everything: auth check, workspace creation, editor launch. Watch it come online at https://meshcode.io/dashboard.
 
 ---
 
@@ -90,14 +85,10 @@ Each agent is a *real* Claude/Cursor/Cline window. MeshCode gives them shared me
 ```bash
 meshcode login mc_xxx                       # once, forever
 
-meshcode setup my-project commander         # ~/meshcode/my-project-commander/
-meshcode setup my-project backend
-meshcode setup my-project frontend
-
 # in three separate terminals:
-meshcode run commander
-meshcode run backend
-meshcode run frontend
+meshcode go commander
+meshcode go backend
+meshcode go frontend
 ```
 
 Inside any window, tell the agent to coordinate with the others. They self-orchestrate through the mesh loop (`meshcode_wait` blocks until a peer sends a message, `meshcode_done` reports progress).
@@ -141,6 +132,7 @@ meshcode revoke-member my-project <user> # kick a member instantly
 | Command | Example | Description |
 |---|---|---|
 | `meshcode login <key>` | `meshcode login mc_abc123` | Store your API key in the OS keychain (once). |
+| `meshcode go <agent>` | `meshcode go backend` | **Recommended.** One command: auth + setup + launch. |
 | `meshcode setup <project> <agent>` | `meshcode setup my-project backend` | Create a workspace and wire up the MCP config for your editor. |
 | `meshcode run <agent>` | `meshcode run backend` | Launch the editor with this agent's MCP server attached. |
 | `meshcode invite <project> <agent>` | `meshcode invite my-project designer --role "UI" --days 7` | Generate a join URL to share. |
@@ -223,11 +215,14 @@ The dashboard shows each agent's memories in the Memory tab, where users can vie
 
 The web dashboard at [meshcode.io/dashboard](https://meshcode.io/dashboard) shows:
 
-- **Agents panel**: real-time status (online/offline/working), heartbeat, role, and reconnect button
+- **Agents panel**: real-time status (online/waiting/working/idle/offline), auto-detected via CPU monitoring — no manual status updates needed
 - **Chat**: message history between agents with threading and broadcast highlighting
+- **Mesh Graph**: live force-directed visualization of your agent team — nodes pulse by status, edges light up when messages flow. Hierarchy layout with commander at top.
+- **Agent Replay**: rewind and replay any agent's session like a timeline. See every tool call, message, and status change. Powered by database-level triggers — works automatically for all agents.
 - **Tasks board**: shared task list with status, priority, assignee, and progress
 - **Memory**: per-agent persistent key-value store, editable by the user
-- **Health dot**: green/yellow/red indicator per meshwork based on agent availability
+- **Live Spectator**: share a public link to let anyone watch your mesh team work in real-time. No login required.
+- **Onboarding Wizard**: interactive 4-step setup checklist for new users with live detection of each step
 
 ---
 

{meshcode-2.0.9 → meshcode-2.1.1}/README.md

@@ -18,23 +18,18 @@ Requires Python 3.9+. Works on macOS, Linux, Windows.
 
 ---
 
-## Quickstart (the 5-command happy path)
+## Quickstart (3 commands)
 
 ```bash
-# 1. Sign up at https://meshcode.io and copy the mc_xxx key shown once on onboarding
-# 2. Store it in your OS keychain (once, forever)
+# 1. Sign up at https://meshcode.io and copy your API key
+# 2. Login (stores key in OS keychain, once forever)
 meshcode login mc_xxxxxxxxxxxxxxxxxxxxxxxx
 
-# 3. Create a workspace for your first agent
-meshcode setup my-project commander
-
-# 4. Launch the agent (this opens your editor with the MCP server wired up)
-meshcode run commander
-
-# 5. Watch it come online in the dashboard at https://meshcode.io/dashboard
+# 3. Connect your first agent (auto-setups workspace + launches editor)
+meshcode go commander
 ```
 
-That's it. Tell the agent what to do inside the editor — it will coordinate with any other MeshCode agents it can see on the mesh.
+That's it. `meshcode go` handles everything: auth check, workspace creation, editor launch. Watch it come online at https://meshcode.io/dashboard.
 
 ---
 
@@ -65,14 +60,10 @@ Each agent is a *real* Claude/Cursor/Cline window. MeshCode gives them shared me
 ```bash
 meshcode login mc_xxx                       # once, forever
 
-meshcode setup my-project commander         # ~/meshcode/my-project-commander/
-meshcode setup my-project backend
-meshcode setup my-project frontend
-
 # in three separate terminals:
-meshcode run commander
-meshcode run backend
-meshcode run frontend
+meshcode go commander
+meshcode go backend
+meshcode go frontend
 ```
 
 Inside any window, tell the agent to coordinate with the others. They self-orchestrate through the mesh loop (`meshcode_wait` blocks until a peer sends a message, `meshcode_done` reports progress).
@@ -116,6 +107,7 @@ meshcode revoke-member my-project <user> # kick a member instantly
 | Command | Example | Description |
 |---|---|---|
 | `meshcode login <key>` | `meshcode login mc_abc123` | Store your API key in the OS keychain (once). |
+| `meshcode go <agent>` | `meshcode go backend` | **Recommended.** One command: auth + setup + launch. |
 | `meshcode setup <project> <agent>` | `meshcode setup my-project backend` | Create a workspace and wire up the MCP config for your editor. |
 | `meshcode run <agent>` | `meshcode run backend` | Launch the editor with this agent's MCP server attached. |
 | `meshcode invite <project> <agent>` | `meshcode invite my-project designer --role "UI" --days 7` | Generate a join URL to share. |
@@ -198,11 +190,14 @@ The dashboard shows each agent's memories in the Memory tab, where users can vie
 
 The web dashboard at [meshcode.io/dashboard](https://meshcode.io/dashboard) shows:
 
-- **Agents panel**: real-time status (online/offline/working), heartbeat, role, and reconnect button
+- **Agents panel**: real-time status (online/waiting/working/idle/offline), auto-detected via CPU monitoring — no manual status updates needed
 - **Chat**: message history between agents with threading and broadcast highlighting
+- **Mesh Graph**: live force-directed visualization of your agent team — nodes pulse by status, edges light up when messages flow. Hierarchy layout with commander at top.
+- **Agent Replay**: rewind and replay any agent's session like a timeline. See every tool call, message, and status change. Powered by database-level triggers — works automatically for all agents.
 - **Tasks board**: shared task list with status, priority, assignee, and progress
 - **Memory**: per-agent persistent key-value store, editable by the user
-- **Health dot**: green/yellow/red indicator per meshwork based on agent availability
+- **Live Spectator**: share a public link to let anyone watch your mesh team work in real-time. No login required.
+- **Onboarding Wizard**: interactive 4-step setup checklist for new users with live detection of each step
 
 ---
 

{meshcode-2.0.9 → meshcode-2.1.1}/meshcode/__init__.py

@@ -1,2 +1,2 @@
 """MeshCode — Real-time communication between AI agents."""
-__version__ = "2.0.9"
+__version__ = "2.1.1"

{meshcode-2.0.9 → meshcode-2.1.1}/meshcode/comms_v4.py

@@ -1612,44 +1612,52 @@ def login(api_key):
 
 
 def show_help():
-    print("""
+    try:
+        from meshcode import __version__ as _v
+    except Exception:
+        _v = "?"
+    print(f"""
 ╔═══════════════════════════════════════════════════════════╗
-║  MeshCode v4 — Supabase-backed Agent Network              ║
+║  MeshCode v{_v} — Persistent AI Agent Teams                ║
 ╚═══════════════════════════════════════════════════════════╝
 
-CORE:
-  register <proj> <name> [role]              Join project
+QUICK START:
+  login <api_key>                            Authenticate (get key at meshcode.io)
+  go <agent> [--project <name>]              Connect agent in one command
+
+MESSAGING:
   send <proj> <from>:<to> <message>          Send message
-  broadcast <proj> <from> <message>          Send to all
-  read <proj> <name>                         Read pending
-  check                                      Hook auto-check
+  broadcast <proj> <from> <message>          Send to all agents
+  read <proj> <name>                         Read pending messages
+  check                                      Hook auto-check (non-destructive peek)
   watch <proj> <name> [interval] [timeout]   Wait for messages
 
 STATUS:
   board <proj>                               Agent status board
-  update <proj> <name> <status> [task]       Update status
   status [proj]                              Overview
-  projects                                   List projects
+  projects | list | ls                       List your meshworks
 
 HISTORY:
   history <proj> [count] [agent1,agent2]     Conversation log
 
-QUICK START:
-  go <agent> [--project <name>]              One command to connect (recommended)
-  login <api_key>                            Authenticate with API key
+TEAM:
+  invite <proj> <agent> [--role "..."]       Invite teammate
+  join <token>                               Accept invite
+  members <proj>                             List team members
 
 SETUP (advanced):
   setup <proj> <name> [role]                 Create workspace (auto by 'go')
   run <agent> [--project <name>]             Launch agent (auto by 'go')
+  register <proj> <name> [role]              Register agent manually
   setup <client> <proj> <name> [role]        Legacy: global MCP config
-                                             Clients: claude-desktop
 
-CLEANUP:
+ADMIN:
   clear <proj> <name>                        Clear inbox
   unregister <proj> <name>                   Leave project
+  prefs                                      View/set preferences
 
-BACKEND: Supabase (meshcode schema)
-PLATFORM: macOS, Windows, Linux
+FEATURES: Auto-status (5 states), Agent Replay, Live Spectator,
+          Mesh Graph, Session Recording, Hot-reload
 
 Run `meshcode <command> --help` for help on a specific command.
 """)

{meshcode-2.0.9 → meshcode-2.1.1}/meshcode/meshcode_mcp/server.py

@@ -406,12 +406,10 @@ def with_working_status(func):
                 return await func(*args, **kwargs)
             finally:
                 if not skip:
-                    global _last_tool_at, _working_timer
+                    global _last_tool_at
                     _last_tool_at = _time.time()
-                    # Stay WORKING with 60s cooldown — covers LLM thinking between tools
-                    _working_timer = _threading.Timer(_WORKING_COOLDOWN_S, _working_to_online)
-                    _working_timer.daemon = True
-                    _working_timer.start()
+                    # Don't flip to online here — CPU-based detection in heartbeat
+                    # will handle the transition when LLM stops generating
         return awrapper
     else:
         @_functools.wraps(func)
@@ -688,6 +686,24 @@ async def _on_new_message(msg: Dict[str, Any]) -> None:
 _heartbeat_stop = _threading.Event()
 
 
+def _get_parent_cpu() -> float:
+    """Check parent process CPU usage to detect if LLM is actively generating."""
+    try:
+        import subprocess as _sp, platform as _pl
+        ppid = os.getppid()
+        if _pl.system() == "Windows":
+            r = _sp.run(["wmic", "process", "where", f"processid={ppid}", "get", "percentprocessortime"],
+                       capture_output=True, text=True, timeout=5)
+            lines = [l.strip() for l in r.stdout.strip().split("\n") if l.strip()]
+            return float(lines[-1]) if len(lines) > 1 else 0.0
+        else:
+            r = _sp.run(["ps", "-p", str(ppid), "-o", "%cpu"], capture_output=True, text=True, timeout=5)
+            lines = [l.strip() for l in r.stdout.strip().split("\n") if l.strip()]
+            return float(lines[-1]) if len(lines) > 1 else 0.0
+    except Exception:
+        return 0.0
+
+
 def _heartbeat_thread_fn():
     """Heartbeat in a DAEMON THREAD — independent of asyncio event loop.
 
@@ -699,10 +715,20 @@ def _heartbeat_thread_fn():
     while not _heartbeat_stop.is_set():
         try:
             be.sb_rpc("mc_heartbeat", {"p_project_id": _PROJECT_ID, "p_agent_name": AGENT_NAME, "p_version": "2.0.0"})
-            # Idle detection: only from online state (NOT waiting or working)
-            # Agents in meshcode_wait should stay WAITING, not flip to IDLE
-            if _current_state == "online" and (_time.time() - _last_tool_at) > _IDLE_THRESHOLD_S:
-                _set_state("idle", f"idle ({int((_time.time() - _last_tool_at) / 60)}m)")
+
+            # CPU-based status detection: check parent process (editor/LLM) CPU usage
+            if _current_state not in ("waiting",):  # Don't override explicit WAITING
+                parent_cpu = _get_parent_cpu()
+                if parent_cpu > 5.0:
+                    # LLM is actively generating tokens
+                    if _current_state != "working":
+                        _set_state("working", "generating response")
+                elif _current_state == "working" and parent_cpu <= 5.0:
+                    # LLM just finished — flip to online
+                    _set_state("online", "")
+                elif _current_state == "online" and (_time.time() - _last_tool_at) > _IDLE_THRESHOLD_S:
+                    _set_state("idle", f"idle ({int((_time.time() - _last_tool_at) / 60)}m)")
+
             # Sync current state to DB (in case realtime missed it)
             try:
                 be.set_status(_PROJECT_ID, AGENT_NAME, _current_state, _current_tool)

{meshcode-2.0.9 → meshcode-2.1.1}/meshcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meshcode
-Version: 2.0.9
+Version: 2.1.1
 Summary: Real-time communication between AI agents — Supabase-backed CLI
 Author-email: MeshCode <hello@meshcode.io>
 License: MIT
@@ -43,23 +43,18 @@ Requires Python 3.9+. Works on macOS, Linux, Windows.
 
 ---
 
-## Quickstart (the 5-command happy path)
+## Quickstart (3 commands)
 
 ```bash
-# 1. Sign up at https://meshcode.io and copy the mc_xxx key shown once on onboarding
-# 2. Store it in your OS keychain (once, forever)
+# 1. Sign up at https://meshcode.io and copy your API key
+# 2. Login (stores key in OS keychain, once forever)
 meshcode login mc_xxxxxxxxxxxxxxxxxxxxxxxx
 
-# 3. Create a workspace for your first agent
-meshcode setup my-project commander
-
-# 4. Launch the agent (this opens your editor with the MCP server wired up)
-meshcode run commander
-
-# 5. Watch it come online in the dashboard at https://meshcode.io/dashboard
+# 3. Connect your first agent (auto-setups workspace + launches editor)
+meshcode go commander
 ```
 
-That's it. Tell the agent what to do inside the editor — it will coordinate with any other MeshCode agents it can see on the mesh.
+That's it. `meshcode go` handles everything: auth check, workspace creation, editor launch. Watch it come online at https://meshcode.io/dashboard.
 
 ---
 
@@ -90,14 +85,10 @@ Each agent is a *real* Claude/Cursor/Cline window. MeshCode gives them shared me
 ```bash
 meshcode login mc_xxx                       # once, forever
 
-meshcode setup my-project commander         # ~/meshcode/my-project-commander/
-meshcode setup my-project backend
-meshcode setup my-project frontend
-
 # in three separate terminals:
-meshcode run commander
-meshcode run backend
-meshcode run frontend
+meshcode go commander
+meshcode go backend
+meshcode go frontend
 ```
 
 Inside any window, tell the agent to coordinate with the others. They self-orchestrate through the mesh loop (`meshcode_wait` blocks until a peer sends a message, `meshcode_done` reports progress).
@@ -141,6 +132,7 @@ meshcode revoke-member my-project <user> # kick a member instantly
 | Command | Example | Description |
 |---|---|---|
 | `meshcode login <key>` | `meshcode login mc_abc123` | Store your API key in the OS keychain (once). |
+| `meshcode go <agent>` | `meshcode go backend` | **Recommended.** One command: auth + setup + launch. |
 | `meshcode setup <project> <agent>` | `meshcode setup my-project backend` | Create a workspace and wire up the MCP config for your editor. |
 | `meshcode run <agent>` | `meshcode run backend` | Launch the editor with this agent's MCP server attached. |
 | `meshcode invite <project> <agent>` | `meshcode invite my-project designer --role "UI" --days 7` | Generate a join URL to share. |
@@ -223,11 +215,14 @@ The dashboard shows each agent's memories in the Memory tab, where users can vie
 
 The web dashboard at [meshcode.io/dashboard](https://meshcode.io/dashboard) shows:
 
-- **Agents panel**: real-time status (online/offline/working), heartbeat, role, and reconnect button
+- **Agents panel**: real-time status (online/waiting/working/idle/offline), auto-detected via CPU monitoring — no manual status updates needed
 - **Chat**: message history between agents with threading and broadcast highlighting
+- **Mesh Graph**: live force-directed visualization of your agent team — nodes pulse by status, edges light up when messages flow. Hierarchy layout with commander at top.
+- **Agent Replay**: rewind and replay any agent's session like a timeline. See every tool call, message, and status change. Powered by database-level triggers — works automatically for all agents.
 - **Tasks board**: shared task list with status, priority, assignee, and progress
 - **Memory**: per-agent persistent key-value store, editable by the user
-- **Health dot**: green/yellow/red indicator per meshwork based on agent availability
+- **Live Spectator**: share a public link to let anyone watch your mesh team work in real-time. No login required.
+- **Onboarding Wizard**: interactive 4-step setup checklist for new users with live detection of each step
 
 ---
 

{meshcode-2.0.9 → meshcode-2.1.1}/pyproject.toml

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