meshcode 2.0.2__tar.gz → 2.0.3__tar.gz

{meshcode-2.0.2 → meshcode-2.0.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meshcode
-Version: 2.0.2
+Version: 2.0.3
 Summary: Real-time communication between AI agents — Supabase-backed CLI
 Author-email: MeshCode <hello@meshcode.io>
 License: MIT
@@ -153,7 +153,9 @@ meshcode revoke-member my-project <user> # kick a member instantly
 | `meshcode status` | `meshcode status` | Show the logged-in account and version. |
 | `meshcode send` (legacy) | `meshcode send my-project a:b '{"need":"..."}'` | Pre-1.5 manual message send (MCP tools are preferred). |
 | `meshcode read` (legacy) | `meshcode read my-project backend` | Pre-1.5 manual read. |
-| `meshcode --version` | `meshcode --version` | Print `meshcode 1.5.1`. |
+| `meshcode projects` | `meshcode projects` | List all your meshworks and their agents. |
+| `meshcode list` | `meshcode list` | Alias for `meshcode projects`. |
+| `meshcode --version` | `meshcode --version` | Print current version. |
 | `meshcode help` | `meshcode help` | Top-level help. Per-verb help: `meshcode <verb> --help`. |
 
 ---
@@ -251,10 +253,11 @@ pip install meshcode --upgrade
 ### Reconnect a single agent
 
 ```bash
-meshcode run <agent-name>
+meshcode setup my-project agent-name   # ensures workspace exists (safe to re-run)
+meshcode run agent-name                # opens your editor
 ```
 
-That's it. This reopens your editor with the agent's MCP server. The agent automatically:
+Since v2.0.2, `meshcode run` **auto-recovers** if the workspace was deleted — it queries the server, recreates the workspace, and launches. So `meshcode run agent-name` alone is usually enough. The agent automatically:
 1. Loads its persistent memories (`meshcode_recall()`)
 2. Checks who else is online (`meshcode_status()`)
 3. Picks up any open tasks (`meshcode_tasks()`)
@@ -326,21 +329,49 @@ If an agent is offline, the dashboard shows a **Reconnect** button on its card.
 
 ## Troubleshooting
 
-**1. `No credentials found. Run meshcode login first.`**
+**1. `no workspace found for agent 'X'`**
+Your local workspace was deleted or never created. Since v2.0.2, `meshcode run` auto-recovers by querying the server. If you're on an older version:
+```bash
+pip install meshcode --upgrade          # get v2.0.2+
+meshcode run agent-name                 # auto-recovers now
+```
+If auto-recovery fails (no API key stored), run setup manually:
+```bash
+meshcode setup my-project agent-name    # recreates ~/meshcode/my-project-agent-name/
+meshcode run agent-name
+```
+
+**2. `meshcode projects` shows no projects (but dashboard shows them)**
+Before v2.0.2, the `projects` command used an unauthenticated query blocked by row-level security. Upgrade:
+```bash
+pip install meshcode --upgrade
+meshcode projects                       # now uses your API key
+```
+
+**3. `No credentials found. Run meshcode login first.`**
 You haven't stored a key yet. Grab your `mc_xxx` from https://meshcode.io/onboarding and run:
 ```bash
 meshcode login mc_xxxxxxxxxxxx
 ```
 
-**2. `agent already running in another window`**
+**4. `agent already running in another window`**
 MeshCode prevents split-brain — the same agent name can't be live in two editor windows. Close the other window, or use a different agent name.
 
-**3. `scoped api key cannot access this project`**
+**5. `scoped api key cannot access this project`**
 You joined a meshwork via an invite, and you're now trying to use a different project. Scoped keys only work for the one mesh they were minted for. Run `meshcode members <correct-project>` to confirm which mesh you belong to.
 
-**4. `meshcode: command not found`**
+**6. `meshcode: command not found`**
 Either `pip install` didn't add to your PATH (check `which meshcode` and `python -m site --user-base`), or you have a stale pre-1.0.0 `~/bin/meshcode` shim shadowing the real binary — delete it.
 
+**7. `could not resolve project 'X': project not found`**
+Wrong project name. Since v2.0.2, `meshcode setup` will suggest your real projects when it can't find the one you typed. Check the exact name:
+```bash
+meshcode projects                       # lists all your meshworks
+```
+
+**8. Unknown command (e.g., `meshcode list`)**
+Since v2.0.2, the CLI suggests the closest match instead of dumping the full help text. Common aliases: `list` and `ls` both work for `projects`.
+
 **5. `MCP server failed to start` in the Claude Code `/mcp` panel**
 Run `claude --debug` to see the underlying error. Nine times out of ten it's a stale or missing key — run `meshcode login mc_xxx` again.
 

{meshcode-2.0.2 → meshcode-2.0.3}/README.md

@@ -128,7 +128,9 @@ meshcode revoke-member my-project <user> # kick a member instantly
 | `meshcode status` | `meshcode status` | Show the logged-in account and version. |
 | `meshcode send` (legacy) | `meshcode send my-project a:b '{"need":"..."}'` | Pre-1.5 manual message send (MCP tools are preferred). |
 | `meshcode read` (legacy) | `meshcode read my-project backend` | Pre-1.5 manual read. |
-| `meshcode --version` | `meshcode --version` | Print `meshcode 1.5.1`. |
+| `meshcode projects` | `meshcode projects` | List all your meshworks and their agents. |
+| `meshcode list` | `meshcode list` | Alias for `meshcode projects`. |
+| `meshcode --version` | `meshcode --version` | Print current version. |
 | `meshcode help` | `meshcode help` | Top-level help. Per-verb help: `meshcode <verb> --help`. |
 
 ---
@@ -226,10 +228,11 @@ pip install meshcode --upgrade
 ### Reconnect a single agent
 
 ```bash
-meshcode run <agent-name>
+meshcode setup my-project agent-name   # ensures workspace exists (safe to re-run)
+meshcode run agent-name                # opens your editor
 ```
 
-That's it. This reopens your editor with the agent's MCP server. The agent automatically:
+Since v2.0.2, `meshcode run` **auto-recovers** if the workspace was deleted — it queries the server, recreates the workspace, and launches. So `meshcode run agent-name` alone is usually enough. The agent automatically:
 1. Loads its persistent memories (`meshcode_recall()`)
 2. Checks who else is online (`meshcode_status()`)
 3. Picks up any open tasks (`meshcode_tasks()`)
@@ -301,21 +304,49 @@ If an agent is offline, the dashboard shows a **Reconnect** button on its card.
 
 ## Troubleshooting
 
-**1. `No credentials found. Run meshcode login first.`**
+**1. `no workspace found for agent 'X'`**
+Your local workspace was deleted or never created. Since v2.0.2, `meshcode run` auto-recovers by querying the server. If you're on an older version:
+```bash
+pip install meshcode --upgrade          # get v2.0.2+
+meshcode run agent-name                 # auto-recovers now
+```
+If auto-recovery fails (no API key stored), run setup manually:
+```bash
+meshcode setup my-project agent-name    # recreates ~/meshcode/my-project-agent-name/
+meshcode run agent-name
+```
+
+**2. `meshcode projects` shows no projects (but dashboard shows them)**
+Before v2.0.2, the `projects` command used an unauthenticated query blocked by row-level security. Upgrade:
+```bash
+pip install meshcode --upgrade
+meshcode projects                       # now uses your API key
+```
+
+**3. `No credentials found. Run meshcode login first.`**
 You haven't stored a key yet. Grab your `mc_xxx` from https://meshcode.io/onboarding and run:
 ```bash
 meshcode login mc_xxxxxxxxxxxx
 ```
 
-**2. `agent already running in another window`**
+**4. `agent already running in another window`**
 MeshCode prevents split-brain — the same agent name can't be live in two editor windows. Close the other window, or use a different agent name.
 
-**3. `scoped api key cannot access this project`**
+**5. `scoped api key cannot access this project`**
 You joined a meshwork via an invite, and you're now trying to use a different project. Scoped keys only work for the one mesh they were minted for. Run `meshcode members <correct-project>` to confirm which mesh you belong to.
 
-**4. `meshcode: command not found`**
+**6. `meshcode: command not found`**
 Either `pip install` didn't add to your PATH (check `which meshcode` and `python -m site --user-base`), or you have a stale pre-1.0.0 `~/bin/meshcode` shim shadowing the real binary — delete it.
 
+**7. `could not resolve project 'X': project not found`**
+Wrong project name. Since v2.0.2, `meshcode setup` will suggest your real projects when it can't find the one you typed. Check the exact name:
+```bash
+meshcode projects                       # lists all your meshworks
+```
+
+**8. Unknown command (e.g., `meshcode list`)**
+Since v2.0.2, the CLI suggests the closest match instead of dumping the full help text. Common aliases: `list` and `ls` both work for `projects`.
+
 **5. `MCP server failed to start` in the Claude Code `/mcp` panel**
 Run `claude --debug` to see the underlying error. Nine times out of ten it's a stale or missing key — run `meshcode login mc_xxx` again.
 

{meshcode-2.0.2 → meshcode-2.0.3}/meshcode/__init__.py

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

{meshcode-2.0.2 → meshcode-2.0.3}/meshcode/meshcode_mcp/realtime.py

@@ -13,6 +13,7 @@ import logging
 import ssl
 from collections import deque
 from typing import Any, Awaitable, Callable, Deque, Dict, Optional
+from urllib.parse import quote as url_quote
 
 try:
     import certifi
@@ -138,7 +139,7 @@ class RealtimeListener:
                                 "event": "INSERT",
                                 "schema": "meshcode",
                                 "table": "mc_messages",
-                                "filter": f"to_agent=eq.{self.agent_name}",
+                                "filter": f"to_agent=eq.{url_quote(self.agent_name, safe='')}",
                             }
                         ]
                     }

{meshcode-2.0.2 → meshcode-2.0.3}/meshcode/meshcode_mcp/server.py

@@ -44,18 +44,23 @@ def _try_auto_wake(from_agent: str, preview: str) -> None:
     """
     if _IN_WAIT or not _AUTO_WAKE:
         return
-    import subprocess, platform
-    nudge = f"You have a new mesh message from {from_agent}: {preview[:60]}. Check your inbox with meshcode_check()."
+    import subprocess, platform, re
+    # Sanitize inputs: strip everything except alphanumeric, spaces, basic punctuation
+    safe_agent = re.sub(r'[^a-zA-Z0-9_\- ]', '', from_agent)[:50]
+    safe_preview = re.sub(r'[^a-zA-Z0-9_\-.,!? ]', '', preview)[:60]
+    nudge = f"New mesh message from {safe_agent}: {safe_preview}. Check inbox with meshcode_check()."
     system = platform.system()
     try:
         if system == "Darwin":
-            # Find which terminal app is running this process
+            # Use xdotool-style approach: pass nudge as argument, not interpolated script
             parent_app = os.environ.get("TERM_PROGRAM", "Terminal")
             app_name = "iTerm" if "iTerm" in parent_app else "Terminal"
+            # Escape for AppleScript string: replace backslash and double-quote
+            as_safe = nudge.replace("\\", "\\\\").replace('"', '\\"')
             script = f'''
             tell application "{app_name}"
                 tell application "System Events"
-                    keystroke "{nudge}"
+                    keystroke "{as_safe}"
                     keystroke return
                 end tell
             end tell
@@ -64,15 +69,17 @@ def _try_auto_wake(from_agent: str, preview: str) -> None:
                              stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
             log.info(f"auto-wake: injected nudge via {app_name} AppleScript")
         elif system == "Windows":
+            # Sanitize for SendKeys: strip braces and special SendKeys metacharacters
+            sk_safe = nudge.replace("{", "").replace("}", "").replace("+", "").replace("^", "").replace("%", "").replace("~", "")
             ps_script = f'''
             Add-Type -AssemblyName System.Windows.Forms
-            [System.Windows.Forms.SendKeys]::SendWait("{nudge}{{ENTER}}")
+            [System.Windows.Forms.SendKeys]::SendWait("{sk_safe}{{ENTER}}")
             '''
             subprocess.Popen(["powershell", "-Command", ps_script],
                              stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
             log.info("auto-wake: injected nudge via PowerShell SendKeys")
         else:
-            # Linux — best-effort with xdotool
+            # Linux — xdotool takes args directly, not shell-interpolated (safe)
             subprocess.Popen(["xdotool", "type", "--clearmodifiers", nudge + "\n"],
                              stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
             log.info("auto-wake: injected nudge via xdotool")
@@ -1258,6 +1265,9 @@ def _sync_to_obsidian(key: str, value: Any) -> None:
     Writes markdown notes with YAML frontmatter to MeshCode/<agent>/ folder.
     Failures are logged but never block the main memory write.
     """
+    from datetime import datetime
+    from urllib.request import Request, urlopen
+    from urllib.error import URLError
     try:
         import importlib
         prefs_mod = importlib.import_module("meshcode.preferences")
@@ -1265,10 +1275,6 @@ def _sync_to_obsidian(key: str, value: Any) -> None:
         if not config:
             return
 
-        from datetime import datetime
-        from urllib.request import Request, urlopen
-        from urllib.error import URLError
-
         # Build markdown note with YAML frontmatter
         timestamp = datetime.utcnow().strftime("%Y-%m-%dT%H:%M:%SZ")
         if isinstance(value, (dict, list)):

{meshcode-2.0.2 → meshcode-2.0.3}/meshcode.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: meshcode
-Version: 2.0.2
+Version: 2.0.3
 Summary: Real-time communication between AI agents — Supabase-backed CLI
 Author-email: MeshCode <hello@meshcode.io>
 License: MIT
@@ -153,7 +153,9 @@ meshcode revoke-member my-project <user> # kick a member instantly
 | `meshcode status` | `meshcode status` | Show the logged-in account and version. |
 | `meshcode send` (legacy) | `meshcode send my-project a:b '{"need":"..."}'` | Pre-1.5 manual message send (MCP tools are preferred). |
 | `meshcode read` (legacy) | `meshcode read my-project backend` | Pre-1.5 manual read. |
-| `meshcode --version` | `meshcode --version` | Print `meshcode 1.5.1`. |
+| `meshcode projects` | `meshcode projects` | List all your meshworks and their agents. |
+| `meshcode list` | `meshcode list` | Alias for `meshcode projects`. |
+| `meshcode --version` | `meshcode --version` | Print current version. |
 | `meshcode help` | `meshcode help` | Top-level help. Per-verb help: `meshcode <verb> --help`. |
 
 ---
@@ -251,10 +253,11 @@ pip install meshcode --upgrade
 ### Reconnect a single agent
 
 ```bash
-meshcode run <agent-name>
+meshcode setup my-project agent-name   # ensures workspace exists (safe to re-run)
+meshcode run agent-name                # opens your editor
 ```
 
-That's it. This reopens your editor with the agent's MCP server. The agent automatically:
+Since v2.0.2, `meshcode run` **auto-recovers** if the workspace was deleted — it queries the server, recreates the workspace, and launches. So `meshcode run agent-name` alone is usually enough. The agent automatically:
 1. Loads its persistent memories (`meshcode_recall()`)
 2. Checks who else is online (`meshcode_status()`)
 3. Picks up any open tasks (`meshcode_tasks()`)
@@ -326,21 +329,49 @@ If an agent is offline, the dashboard shows a **Reconnect** button on its card.
 
 ## Troubleshooting
 
-**1. `No credentials found. Run meshcode login first.`**
+**1. `no workspace found for agent 'X'`**
+Your local workspace was deleted or never created. Since v2.0.2, `meshcode run` auto-recovers by querying the server. If you're on an older version:
+```bash
+pip install meshcode --upgrade          # get v2.0.2+
+meshcode run agent-name                 # auto-recovers now
+```
+If auto-recovery fails (no API key stored), run setup manually:
+```bash
+meshcode setup my-project agent-name    # recreates ~/meshcode/my-project-agent-name/
+meshcode run agent-name
+```
+
+**2. `meshcode projects` shows no projects (but dashboard shows them)**
+Before v2.0.2, the `projects` command used an unauthenticated query blocked by row-level security. Upgrade:
+```bash
+pip install meshcode --upgrade
+meshcode projects                       # now uses your API key
+```
+
+**3. `No credentials found. Run meshcode login first.`**
 You haven't stored a key yet. Grab your `mc_xxx` from https://meshcode.io/onboarding and run:
 ```bash
 meshcode login mc_xxxxxxxxxxxx
 ```
 
-**2. `agent already running in another window`**
+**4. `agent already running in another window`**
 MeshCode prevents split-brain — the same agent name can't be live in two editor windows. Close the other window, or use a different agent name.
 
-**3. `scoped api key cannot access this project`**
+**5. `scoped api key cannot access this project`**
 You joined a meshwork via an invite, and you're now trying to use a different project. Scoped keys only work for the one mesh they were minted for. Run `meshcode members <correct-project>` to confirm which mesh you belong to.
 
-**4. `meshcode: command not found`**
+**6. `meshcode: command not found`**
 Either `pip install` didn't add to your PATH (check `which meshcode` and `python -m site --user-base`), or you have a stale pre-1.0.0 `~/bin/meshcode` shim shadowing the real binary — delete it.
 
+**7. `could not resolve project 'X': project not found`**
+Wrong project name. Since v2.0.2, `meshcode setup` will suggest your real projects when it can't find the one you typed. Check the exact name:
+```bash
+meshcode projects                       # lists all your meshworks
+```
+
+**8. Unknown command (e.g., `meshcode list`)**
+Since v2.0.2, the CLI suggests the closest match instead of dumping the full help text. Common aliases: `list` and `ls` both work for `projects`.
+
 **5. `MCP server failed to start` in the Claude Code `/mcp` panel**
 Run `claude --debug` to see the underlying error. Nine times out of ten it's a stale or missing key — run `meshcode login mc_xxx` again.
 

{meshcode-2.0.2 → meshcode-2.0.3}/pyproject.toml

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