hivecode-mcp 0.14.5 → 0.14.6
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.
- package/README.md +5 -5
- package/docs/MCP.md +1 -1
- package/docs/SLACK_SETUP.md +18 -18
- package/hive-privacy.js +5 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -16,7 +16,7 @@ earlier point.
|
|
|
16
16
|
## How it works
|
|
17
17
|
|
|
18
18
|
1. Someone creates a **room** and gets a **join link**, like
|
|
19
|
-
`wss://
|
|
19
|
+
`wss://livecode-xoss.onrender.com|room-a1b2c3d4e5`
|
|
20
20
|
2. Everyone — people and agents — joins with that link.
|
|
21
21
|
3. Each agent works in **its own folder**. Hivecode keeps every folder identical, live.
|
|
22
22
|
4. An agent **claims** a file before editing it and **releases** it after. While someone
|
|
@@ -88,7 +88,7 @@ Then:
|
|
|
88
88
|
Customizations → MCP Servers → refresh. For Claude Code, start a new session.
|
|
89
89
|
2. **Paste this to your agent**, with the link you were sent and a name:
|
|
90
90
|
|
|
91
|
-
> Use your hive_join tool to join the Hivecode room `wss://
|
|
91
|
+
> Use your hive_join tool to join the Hivecode room `wss://livecode-xoss.onrender.com|room-a1b2c3d4e5`
|
|
92
92
|
> as **Alice-AI**. Then follow the rules it gives you.
|
|
93
93
|
|
|
94
94
|
The agent's files go in `~/hivecode/<room>/<name>`, a folder of its own. To use a particular
|
|
@@ -124,12 +124,12 @@ If it says **NOT JOINED** instead, see [Troubleshooting](#troubleshooting).
|
|
|
124
124
|
|
|
125
125
|
You don't need to install anything to watch and steer.
|
|
126
126
|
|
|
127
|
-
1. Open the Control Room: **https://
|
|
127
|
+
1. Open the Control Room: **https://livecode-xoss.onrender.com/control**
|
|
128
128
|
2. Paste the join link, type your name, and press **Enter room**.
|
|
129
129
|
|
|
130
130
|
To skip the pasting, put the link after a `#` in the address — the room is filled in and you
|
|
131
131
|
only type your name:
|
|
132
|
-
`https://
|
|
132
|
+
`https://livecode-xoss.onrender.com/control#wss://livecode-xoss.onrender.com|room-a1b2c3d4e5`
|
|
133
133
|
|
|
134
134
|
From there you can:
|
|
135
135
|
|
|
@@ -366,7 +366,7 @@ you prompt it: tell it to check the room.
|
|
|
366
366
|
| `setup` printed `FAILED` for an app | that app's config could not be written, or what was written does not start | the reason is on the same line, and the entry to add by hand is printed below it |
|
|
367
367
|
| `npx` stops with `ENOENT` and `AppData\Roaming\npm` (Windows) | that folder is missing, which happens on some fresh Node installs, and npm gives up before Hivecode starts | create it with `mkdir "$env:APPDATA\npm"` in PowerShell (`mkdir "%APPDATA%\npm"` in cmd), then run setup again |
|
|
368
368
|
| `'room-…' is not recognized` or `command not found: room-…` | a join link was pasted into a terminal without quotes | give the link to your agent instead; if you pass it to `setup`, quote it |
|
|
369
|
-
| `NOT JOINED` and the address `
|
|
369
|
+
| `NOT JOINED` and the address `hivecode-relay.onrender.com` | an old Hivecode version, still cached by `npx` | put `hivecode-mcp@latest` in your agent's config and restart it |
|
|
370
370
|
| `Q430` | the relay is out of sockets | try again shortly; clients on the older one-socket-per-file transport (the VS Code extension, the browser panel) can lower `HIVE_MAX_OPEN_FILES` |
|
|
371
371
|
| `Q438` | the relay holds as many open files as it is sized for | try again shortly, or ask whoever runs the relay to raise `HIVE_MAX_CHANNELS_TOTAL` |
|
|
372
372
|
| `Q431` | this room is full | fewer participants in one room, or ask whoever runs the relay to raise `HIVE_SEATS` |
|
package/docs/MCP.md
CHANGED
|
@@ -16,7 +16,7 @@ the runtime copy that `setup` installs:
|
|
|
16
16
|
"hivecode": {
|
|
17
17
|
"command": "node",
|
|
18
18
|
"args": ["<your home>/.hivecode/runtime/<version>/node_modules/hivecode-mcp/hive-mcp.js"],
|
|
19
|
-
"env": { "HIVE_RELAY": "wss://
|
|
19
|
+
"env": { "HIVE_RELAY": "wss://livecode-xoss.onrender.com" }
|
|
20
20
|
}
|
|
21
21
|
}
|
|
22
22
|
}
|
package/docs/SLACK_SETUP.md
CHANGED
|
@@ -110,24 +110,24 @@ Once `slack check` passes, you can also run `--dry-run` on `slack start` or `git
|
|
|
110
110
|
**macOS / Linux (bash, zsh):**
|
|
111
111
|
```bash
|
|
112
112
|
# 1. Verify token and channel membership first
|
|
113
|
-
SLACK_BOT_TOKEN=xoxb-… npx -y hivecode-mcp@latest slack start "wss://
|
|
113
|
+
SLACK_BOT_TOKEN=xoxb-… npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --dry-run
|
|
114
114
|
|
|
115
115
|
# 2. Start the live bridge
|
|
116
|
-
SLACK_BOT_TOKEN=xoxb-… npx -y hivecode-mcp@latest slack start "wss://
|
|
116
|
+
SLACK_BOT_TOKEN=xoxb-… npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789
|
|
117
117
|
```
|
|
118
118
|
|
|
119
119
|
**Windows (PowerShell):**
|
|
120
120
|
```powershell
|
|
121
121
|
$env:SLACK_BOT_TOKEN="xoxb-…"
|
|
122
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
123
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
122
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --dry-run
|
|
123
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789
|
|
124
124
|
```
|
|
125
125
|
|
|
126
126
|
**Windows (Command Prompt / `cmd.exe`):**
|
|
127
127
|
```cmd
|
|
128
128
|
set SLACK_BOT_TOKEN=xoxb-…
|
|
129
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
130
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
129
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --dry-run
|
|
130
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789
|
|
131
131
|
```
|
|
132
132
|
|
|
133
133
|
---
|
|
@@ -284,14 +284,14 @@ What to know about polling:
|
|
|
284
284
|
|
|
285
285
|
macOS / Linux (bash, zsh):
|
|
286
286
|
```bash
|
|
287
|
-
SLACK_BOT_TOKEN=xoxb-… SLACK_APP_TOKEN=xapp-… npx -y hivecode-mcp@latest slack agent "wss://
|
|
287
|
+
SLACK_BOT_TOKEN=xoxb-… SLACK_APP_TOKEN=xapp-… npx -y hivecode-mcp@latest slack agent "wss://livecode-xoss.onrender.com|room-abc123" --channel D0123456789 --allow U012ABCDEF
|
|
288
288
|
```
|
|
289
289
|
|
|
290
290
|
Windows (PowerShell):
|
|
291
291
|
```powershell
|
|
292
292
|
$env:SLACK_BOT_TOKEN="xoxb-…"
|
|
293
293
|
$env:SLACK_APP_TOKEN="xapp-…"
|
|
294
|
-
npx -y hivecode-mcp@latest slack agent "wss://
|
|
294
|
+
npx -y hivecode-mcp@latest slack agent "wss://livecode-xoss.onrender.com|room-abc123" --channel D0123456789 --allow U012ABCDEF
|
|
295
295
|
```
|
|
296
296
|
|
|
297
297
|
<details>
|
|
@@ -366,24 +366,24 @@ Paste the contents of [`slack-app-manifest-agent.json`](../slack-app-manifest-ag
|
|
|
366
366
|
|
|
367
367
|
**macOS / Linux (bash, zsh):**
|
|
368
368
|
```bash
|
|
369
|
-
SLACK_BOT_TOKEN=xoxb-… SLACK_APP_TOKEN=xapp-… npx -y hivecode-mcp@latest slack start "wss://
|
|
370
|
-
SLACK_BOT_TOKEN=xoxb-… SLACK_APP_TOKEN=xapp-… npx -y hivecode-mcp@latest slack start "wss://
|
|
369
|
+
SLACK_BOT_TOKEN=xoxb-… SLACK_APP_TOKEN=xapp-… npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF --dry-run
|
|
370
|
+
SLACK_BOT_TOKEN=xoxb-… SLACK_APP_TOKEN=xapp-… npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF
|
|
371
371
|
```
|
|
372
372
|
|
|
373
373
|
**Windows (PowerShell):**
|
|
374
374
|
```powershell
|
|
375
375
|
$env:SLACK_BOT_TOKEN="xoxb-…"
|
|
376
376
|
$env:SLACK_APP_TOKEN="xapp-…"
|
|
377
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
378
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
377
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF --dry-run
|
|
378
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF
|
|
379
379
|
```
|
|
380
380
|
|
|
381
381
|
**Windows (Command Prompt / `cmd.exe`):**
|
|
382
382
|
```cmd
|
|
383
383
|
set SLACK_BOT_TOKEN=xoxb-…
|
|
384
384
|
set SLACK_APP_TOKEN=xapp-…
|
|
385
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
386
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
385
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF --dry-run
|
|
386
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF
|
|
387
387
|
```
|
|
388
388
|
|
|
389
389
|
### Slackbot Remote MCP Server (`hive-mcp-http.js`)
|
|
@@ -400,14 +400,14 @@ If you connect Slackbot's remote MCP client over Streamable HTTP (`hive-mcp-http
|
|
|
400
400
|
|
|
401
401
|
**macOS / Linux (bash, zsh):**
|
|
402
402
|
```bash
|
|
403
|
-
SLACK_SIGNING_SECRET=… SLACK_BOT_TOKEN=xoxb-… npx -y hivecode-mcp@latest slack mcp-server "wss://
|
|
403
|
+
SLACK_SIGNING_SECRET=… SLACK_BOT_TOKEN=xoxb-… npx -y hivecode-mcp@latest slack mcp-server "wss://livecode-xoss.onrender.com|room-abc123" --port 8790 --allow U012ABCDEF
|
|
404
404
|
```
|
|
405
405
|
|
|
406
406
|
**Windows (PowerShell):**
|
|
407
407
|
```powershell
|
|
408
408
|
$env:SLACK_SIGNING_SECRET="…"
|
|
409
409
|
$env:SLACK_BOT_TOKEN="xoxb-…"
|
|
410
|
-
npx -y hivecode-mcp@latest slack mcp-server "wss://
|
|
410
|
+
npx -y hivecode-mcp@latest slack mcp-server "wss://livecode-xoss.onrender.com|room-abc123" --port 8790 --allow U012ABCDEF
|
|
411
411
|
```
|
|
412
412
|
|
|
413
413
|
**What a First-Time User Sees Step by Step (`hive-mcp-http.js`):**
|
|
@@ -447,8 +447,8 @@ Use these 5 steps to demonstrate either **GitHub-to-Slack issue threads** (`gith
|
|
|
447
447
|
```powershell
|
|
448
448
|
$env:SLACK_BOT_TOKEN="xoxb-…"
|
|
449
449
|
$env:SLACK_APP_TOKEN="xapp-…"
|
|
450
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
451
|
-
npx -y hivecode-mcp@latest slack start "wss://
|
|
450
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF --dry-run
|
|
451
|
+
npx -y hivecode-mcp@latest slack start "wss://livecode-xoss.onrender.com|room-abc123" --channel C0123456789 --allow U012ABCDEF
|
|
452
452
|
```
|
|
453
453
|
4. **Trigger a Thread**:
|
|
454
454
|
- **In Flow A**: Add the `hivecode` label to a GitHub issue. Watch Slack open a single thread (`#12 — Title`) for that issue and post run progress inside it.
|
package/hive-privacy.js
CHANGED
|
@@ -14,7 +14,7 @@
|
|
|
14
14
|
//
|
|
15
15
|
// 1. A VERDICT on every join, so "am I private?" is answered without being asked.
|
|
16
16
|
// Printing the URL is not a verdict. A person who has never run a relay cannot tell
|
|
17
|
-
// wss://
|
|
17
|
+
// wss://hivecode-relay.onrender.com from wss://relay.theircompany.com by looking.
|
|
18
18
|
//
|
|
19
19
|
// 2. A PIN that REFUSES. A verdict you have to read is a verdict that gets skimmed, and
|
|
20
20
|
// an agent does not read banners at all. HIVE_RELAY_PIN says "this machine may only
|
|
@@ -34,13 +34,15 @@
|
|
|
34
34
|
// sent that client to a dead host, or made this module call the live default "YOUR RELAY".
|
|
35
35
|
// Every client now imports it from here. The extension's JSON setting cannot import, so
|
|
36
36
|
// extension-privacy-parity-test pins it equal to this value instead.
|
|
37
|
-
export const PUBLIC_DEFAULT_RELAY = 'wss://
|
|
37
|
+
export const PUBLIC_DEFAULT_RELAY = 'wss://livecode-xoss.onrender.com'
|
|
38
38
|
|
|
39
|
+
// 10 Nov 2026: the hosted relay moved back to livecode-xoss (its first address, live again) when the
|
|
40
|
+
// hivecode-relay account ran out of hours for the month, so the two addresses below swapped places.
|
|
39
41
|
// Relays this project has run publicly and retired. A .hive.json written before a move still
|
|
40
42
|
// names the old one, and if that host ever answers again (a reactivated account, a squatter
|
|
41
43
|
// on the name) the verdict must still say PUBLIC -- not "YOUR RELAY", which is what any host
|
|
42
44
|
// outside this list is called.
|
|
43
|
-
export const RETIRED_PUBLIC_RELAYS = ['wss://
|
|
45
|
+
export const RETIRED_PUBLIC_RELAYS = ['wss://hivecode-relay.onrender.com']
|
|
44
46
|
|
|
45
47
|
/**
|
|
46
48
|
* The relay a client should actually dial for a URL it was handed.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "hivecode-mcp",
|
|
3
|
-
"version": "0.14.
|
|
3
|
+
"version": "0.14.6",
|
|
4
4
|
"description": "MCP server that lets any AI coding agent join a Hivecode room — humans and multiple AI agents edit one live codebase with folder-scoped permissions and approval gates.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|