golem-bridge 2.0.1 → 3.0.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 CHANGED
@@ -4,7 +4,8 @@
4
4
  running the Golem plugin.
5
5
 
6
6
  This repo holds the npm package (the AI side). The Studio plugin itself is
7
- distributed through the Roblox Creator Store, not from here.
7
+ distributed through the Roblox Creator Store; its source is published as
8
+ a file release on this repo's Releases page.
8
9
 
9
10
  ## How it connects
10
11
 
@@ -17,17 +18,25 @@ Connect to my Roblox Studio, Run: npx golem-bridge connect <channelId>
17
18
  The line is a session token: Studio mints a fresh channel on every start
18
19
  and wipes the old one.
19
20
 
20
- The user sends that line to their AI. It downloads this package, which
21
- checks Studio is alive, then stamps the channel into local copies of
22
- the two connection files under `./.golem/`:
21
+ Best flow: the user runs the line themselves, so the secret never enters
22
+ AI chat, then tells the AI it is connected. Or the user sends the line to
23
+ their AI and it runs it. Either way:
23
24
 
24
25
  ```sh
25
26
  npx golem-bridge connect <channelId>
26
- python3 ./.golem/golem-helper.py ping
27
27
  ```
28
28
 
29
- `ping` should return `"ok": true` plus the open place name. Then the agent
30
- reads `./.golem/golem-tools.md` for the full tool reference.
29
+ verifies Studio is alive, saves the 16-char channel to `./.golem/channel`,
30
+ and prints the tool manual. Nothing else is installed: every command runs
31
+ straight from this package:
32
+
33
+ ```sh
34
+ npx golem-bridge ping
35
+ npx golem-bridge tree --depth 3
36
+ ```
37
+
38
+ `ping` should return `"ok": true` plus the open place name. `manual`
39
+ reprints the reference any time (`help <tool>` explains one tool).
31
40
 
32
41
  After a Studio restart, relink with the new line:
33
42
 
@@ -43,9 +52,8 @@ npx golem-bridge disconnect
43
52
 
44
53
  ## Files
45
54
 
46
- - `cli.js` - source of the `golem-bridge` package
47
- - `golem-helper.py` - the Studio helper, stamped with the channel at connect
48
- - `golem-tools.md` - the agent manual
55
+ - `cli.js` - the whole package: session setup plus every Studio tool
56
+ - `golem-tools.md` - the agent manual (printed by `connect` and `manual`)
49
57
  - `package.json` - npm manifest
50
58
 
51
59
  ## Notes
@@ -53,8 +61,10 @@ npx golem-bridge disconnect
53
61
  - Relay: `https://roblox-golem-default-rtdb.firebaseio.com/`. The channel id
54
62
  is the secret. Studio mints a fresh one on every start and wipes the old
55
63
  channel, so a leaked line dies with the session.
56
- - `golem-helper.py` and `golem-tools.md` ship in this package. The relay carries
57
- small JSON commands and results only.
64
+ - Only `cli.js` and `golem-tools.md` ship in this package. The relay carries
65
+ small JSON commands and results only, and `connect` writes nothing but
66
+ the 16-char channel id.
67
+ - npm account `skellzy` and GitHub `nickils` are the same person.
58
68
 
59
69
  - Leaked a line mid-session? Settings > END SESSION AND ROTATE CHANNEL
60
70
  in the plugin kills it on the spot and issues a new one. (Every Studio
@@ -66,13 +76,9 @@ Trust model: whoever holds the channel ID can send commands to that Studio
66
76
  session and read the results. Treat the setup line like a password. It
67
77
  expires on every Studio restart.
68
78
 
69
- - `connect` verifies
70
- Studio is alive over HTTPS and stamps your channel ID into local copies.
71
- Read all three files here before running anything, or fetch with
72
- `--print` to inspect without writing.
73
- - `connect` asks before it writes: it lists the files first, then waits
74
- for y. Pass `--yes` to skip the question (scripts), `--print` to look
75
- without writing.
79
+ - `connect` verifies Studio is alive over HTTPS, saves the channel id,
80
+ and prints the manual. Read both files here before running anything, or
81
+ pass `--print` to verify without saving.
76
82
  - `connect` only accepts hex channel IDs, talks HTTPS to the relay only
77
83
  (never follows redirects), times out stalled requests, and caps response
78
84
  sizes. The only data it acts on is a small `ping` reply.