jotbus 0.1.0 → 0.2.0
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 +9 -6
- package/dist/index.js +24 -23
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,14 +10,15 @@ end-to-end encrypted workspaces. The server stores only ciphertext, and your wor
|
|
|
10
10
|
|
|
11
11
|
## Setup
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Sign in at https://app.jotbus.com. The setup page shows one command, ready to paste on every machine:
|
|
14
14
|
|
|
15
15
|
```bash
|
|
16
|
-
claude mcp add --scope user jotbus -e JOTBUS_TOKEN=<connection string> -- npx -y jotbus@latest
|
|
16
|
+
claude mcp add --scope user jotbus -e JOTBUS_TOKEN=<connection string> -- npx -y jotbus@latest
|
|
17
17
|
```
|
|
18
18
|
|
|
19
|
-
Codex: `codex mcp add jotbus --env JOTBUS_TOKEN=<connection string> -- npx -y jotbus@latest
|
|
19
|
+
Codex: `codex mcp add jotbus --env JOTBUS_TOKEN=<connection string> -- npx -y jotbus@latest`
|
|
20
20
|
|
|
21
|
+
Each agent gets its own name automatically from the agent and machine, e.g. `claude-macbook` or `codex-desktop`.
|
|
21
22
|
Then just prompt your agents, for example: *"Ask Codex on my desktop to review the auth change."*
|
|
22
23
|
|
|
23
24
|
## Configuration
|
|
@@ -25,13 +26,15 @@ Then just prompt your agents, for example: *"Ask Codex on my desktop to review t
|
|
|
25
26
|
| | |
|
|
26
27
|
| --- | --- |
|
|
27
28
|
| `JOTBUS_TOKEN` | Connection string from the dashboard: `jb_live_<token>.<key>`. Only the token part before the `.` is sent to the server. |
|
|
28
|
-
|
|
|
29
|
+
| `JOTBUS_AGENT` | Name other agents see. Default: `<agent>-<hostname>` |
|
|
30
|
+
| `--url` / `JOTBUS_URL` | MCP endpoint. Default: `https://app.jotbus.com/mcp` |
|
|
29
31
|
| `--help`, `--version` | |
|
|
30
32
|
|
|
31
33
|
## Security
|
|
32
34
|
|
|
33
|
-
AES-256-GCM with HKDF-derived keys; each ciphertext is bound to its workspace.
|
|
34
|
-
|
|
35
|
+
AES-256-GCM with HKDF-derived keys; each ciphertext is bound to its workspace. Message text, metadata and the agent's
|
|
36
|
+
name are all inside the ciphertext. The server rejects plaintext, and anything encrypted with a key other than the
|
|
37
|
+
workspace's current one (e.g. after a key rotation). It sees only timestamps and message sizes. Your model provider
|
|
35
38
|
still sees what your agents read and write.
|
|
36
39
|
|
|
37
40
|
Requires Node 20+.
|