meshcode 1.1.0__tar.gz → 1.2.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (24) hide show
  1. {meshcode-1.1.0 → meshcode-1.2.0}/PKG-INFO +38 -17
  2. {meshcode-1.1.0 → meshcode-1.2.0}/README.md +36 -16
  3. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/comms_v4.py +740 -64
  4. meshcode-1.2.0/meshcode/launcher.py +353 -0
  5. meshcode-1.2.0/meshcode/launcher_install.py +414 -0
  6. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/backend.py +8 -8
  7. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/server.py +36 -2
  8. meshcode-1.2.0/meshcode/protocol_v2.py +129 -0
  9. meshcode-1.2.0/meshcode/setup_clients.py +144 -0
  10. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode.egg-info/PKG-INFO +38 -17
  11. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode.egg-info/SOURCES.txt +4 -0
  12. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode.egg-info/requires.txt +1 -0
  13. {meshcode-1.1.0 → meshcode-1.2.0}/pyproject.toml +2 -1
  14. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/__init__.py +0 -0
  15. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/cli.py +0 -0
  16. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/__init__.py +0 -0
  17. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/__main__.py +0 -0
  18. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/realtime.py +0 -0
  19. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/test_backend.py +0 -0
  20. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode/meshcode_mcp/test_realtime.py +0 -0
  21. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode.egg-info/dependency_links.txt +0 -0
  22. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode.egg-info/entry_points.txt +0 -0
  23. {meshcode-1.1.0 → meshcode-1.2.0}/meshcode.egg-info/top_level.txt +0 -0
  24. {meshcode-1.1.0 → meshcode-1.2.0}/setup.cfg +0 -0
{meshcode-1.1.0 → meshcode-1.2.0}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: meshcode
3
- Version: 1.1.0
3
+ Version: 1.2.0
4
4
  Summary: Real-time communication between AI agents — Supabase-backed CLI
5
5
  Author-email: MeshCode <hello@meshcode.io>
6
6
  License: MIT
@@ -20,6 +20,7 @@ Requires-Python: >=3.9
20
20
  Description-Content-Type: text/markdown
21
21
  Requires-Dist: mcp[cli]>=1.0.0
22
22
  Requires-Dist: websockets>=12.0
23
+ Requires-Dist: realtime>=2.0.0
23
24
 
24
25
  # MeshCode
25
26
 
@@ -30,38 +31,58 @@ MeshCode lets multiple AI agents (Claude Code, Codex, or any LLM) communicate, c
30
31
  ## Install
31
32
 
32
33
  ```bash
33
- pip install meshcode
34
+ pip install -U meshcode
34
35
  ```
35
36
 
36
- Or clone and run directly:
37
+ Requires Python 3.9+. Works on macOS, Linux, and Windows.
38
+
39
+ ## Quickstart (3 commands)
40
+
41
+ MeshCode is the mesh between your AI agents — it never runs an agent for you. You bring your own editor (Claude Code, Cursor, Cline, or Claude Desktop) and the meshcode MCP server connects automatically.
37
42
 
38
43
  ```bash
39
- git clone https://github.com/rf2f7f7sg4-dev/meshcode.git
40
- cd meshcode
41
- python3 comms_v4.py --help
44
+ # 1. Authenticate (one-time, get your API key from meshcode.io after sign-in)
45
+ meshcode login mc_xxxxxxxxxxxxxxxxxxxxxxxx
46
+
47
+ # 2. Register an agent in your editor's MCP config
48
+ meshcode setup claude-code my-project backend
49
+
50
+ # 3. Open Claude Code — that's it. The MCP server boots automatically.
51
+ # Inside the editor, run /mcp to verify the server is connected.
42
52
  ```
43
53
 
44
- ## Quickstart
54
+ Supported clients (`<client>` arg):
45
55
 
46
- ### 1. Connect an agent to a meshwork
56
+ | Client | Slug | Config file written |
57
+ |-----------------|-------------------|---------------------|
58
+ | Claude Code | `claude-code` | `~/.claude.json` |
59
+ | Cursor | `cursor` | `~/.cursor/mcp.json` |
60
+ | Cline (VS Code) | `cline` | `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json` (Mac) |
61
+ | Claude Desktop | `claude-desktop` | `~/Library/Application Support/Claude/claude_desktop_config.json` (Mac) |
47
62
 
48
- ```bash
49
- # One-command setup for Claude Code (installs PostToolUse hook automatically)
50
- meshcode connect my-project backend "Backend Engineer" claude
63
+ After running `meshcode setup`, restart your editor and verify with the editor's MCP listing (e.g. `/mcp` in Claude Code).
51
64
 
52
- # Or for OpenAI Codex
53
- meshcode connect my-project backend "Backend Engineer" codex
65
+ The MCP server exposes these tools to your agent:
54
66
 
55
- # Default hook target is "claude" if omitted:
56
- meshcode connect my-project backend "Backend Engineer"
57
- ```
67
+ - `meshcode_send(to, payload)` — send a message to another agent
68
+ - `meshcode_check()` — poll for new messages (buffered from Supabase Realtime)
69
+ - `meshcode_read()` — drain inbox (marks messages read, ACKs senders)
70
+ - `meshcode_status()` — get the meshwork board (all agents + status)
71
+ - `meshcode_set_status(status, task)` — update your status
72
+ - `meshcode_broadcast(payload)` — message every agent in the meshwork
73
+ - `meshcode_register(role)` — re-register if disconnected
58
74
 
59
- ### 2. Or register manually
75
+ ## Legacy CLI (advanced)
76
+
77
+ The pre-MCP CLI verbs (`register`, `send`, `read`, `watch`, `board`) still work for scripting and direct shell use:
60
78
 
61
79
  ```bash
62
80
  meshcode register my-project backend "Backend Engineer"
81
+ meshcode send my-project backend:frontend '{"done":"API ready"}'
63
82
  ```
64
83
 
84
+ `meshcode connect` is now an alias for `meshcode setup claude-code` and is kept for backwards compatibility.
85
+
65
86
  ### 3. Send messages
66
87
 
67
88
  ```bash
{meshcode-1.1.0 → meshcode-1.2.0}/README.md RENAMED
@@ -7,38 +7,58 @@ MeshCode lets multiple AI agents (Claude Code, Codex, or any LLM) communicate, c
7
7
  ## Install
8
8
 
9
9
  ```bash
10
- pip install meshcode
10
+ pip install -U meshcode
11
11
  ```
12
12
 
13
- Or clone and run directly:
13
+ Requires Python 3.9+. Works on macOS, Linux, and Windows.
14
+
15
+ ## Quickstart (3 commands)
16
+
17
+ MeshCode is the mesh between your AI agents — it never runs an agent for you. You bring your own editor (Claude Code, Cursor, Cline, or Claude Desktop) and the meshcode MCP server connects automatically.
14
18
 
15
19
  ```bash
16
- git clone https://github.com/rf2f7f7sg4-dev/meshcode.git
17
- cd meshcode
18
- python3 comms_v4.py --help
20
+ # 1. Authenticate (one-time, get your API key from meshcode.io after sign-in)
21
+ meshcode login mc_xxxxxxxxxxxxxxxxxxxxxxxx
22
+
23
+ # 2. Register an agent in your editor's MCP config
24
+ meshcode setup claude-code my-project backend
25
+
26
+ # 3. Open Claude Code — that's it. The MCP server boots automatically.
27
+ # Inside the editor, run /mcp to verify the server is connected.
19
28
  ```
20
29
 
21
- ## Quickstart
30
+ Supported clients (`<client>` arg):
22
31
 
23
- ### 1. Connect an agent to a meshwork
32
+ | Client | Slug | Config file written |
33
+ |-----------------|-------------------|---------------------|
34
+ | Claude Code | `claude-code` | `~/.claude.json` |
35
+ | Cursor | `cursor` | `~/.cursor/mcp.json` |
36
+ | Cline (VS Code) | `cline` | `~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json` (Mac) |
37
+ | Claude Desktop | `claude-desktop` | `~/Library/Application Support/Claude/claude_desktop_config.json` (Mac) |
24
38
 
25
- ```bash
26
- # One-command setup for Claude Code (installs PostToolUse hook automatically)
27
- meshcode connect my-project backend "Backend Engineer" claude
39
+ After running `meshcode setup`, restart your editor and verify with the editor's MCP listing (e.g. `/mcp` in Claude Code).
28
40
 
29
- # Or for OpenAI Codex
30
- meshcode connect my-project backend "Backend Engineer" codex
41
+ The MCP server exposes these tools to your agent:
31
42
 
32
- # Default hook target is "claude" if omitted:
33
- meshcode connect my-project backend "Backend Engineer"
34
- ```
43
+ - `meshcode_send(to, payload)` — send a message to another agent
44
+ - `meshcode_check()` — poll for new messages (buffered from Supabase Realtime)
45
+ - `meshcode_read()` — drain inbox (marks messages read, ACKs senders)
46
+ - `meshcode_status()` — get the meshwork board (all agents + status)
47
+ - `meshcode_set_status(status, task)` — update your status
48
+ - `meshcode_broadcast(payload)` — message every agent in the meshwork
49
+ - `meshcode_register(role)` — re-register if disconnected
35
50
 
36
- ### 2. Or register manually
51
+ ## Legacy CLI (advanced)
52
+
53
+ The pre-MCP CLI verbs (`register`, `send`, `read`, `watch`, `board`) still work for scripting and direct shell use:
37
54
 
38
55
  ```bash
39
56
  meshcode register my-project backend "Backend Engineer"
57
+ meshcode send my-project backend:frontend '{"done":"API ready"}'
40
58
  ```
41
59
 
60
+ `meshcode connect` is now an alias for `meshcode setup claude-code` and is kept for backwards compatibility.
61
+
42
62
  ### 3. Send messages
43
63
 
44
64
  ```bash