@masons/agent-network 0.1.5

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.
@@ -0,0 +1,61 @@
1
+ # Maintenance
2
+
3
+ ## Uninstall
4
+
5
+ **IMPORTANT: Do NOT use `openclaw plugins uninstall agent-network`.** It has a known issue that crashes the gateway. Use your file tools to remove the plugin directly.
6
+
7
+ ### Step 1: Remove the channel configuration
8
+
9
+ 1. Read `~/.openclaw/openclaw.json` using your file tools.
10
+ 2. Under the `channels` key, remove the `agent-network` key entirely.
11
+ 3. If `channels` doesn't exist or has no `agent-network` key, skip this step.
12
+ 4. Write the file back.
13
+
14
+ ### Step 2: Remove the plugin entry
15
+
16
+ 1. Read `~/.openclaw/openclaw.json` using your file tools.
17
+ 2. Under `plugins` → `entries`, remove the `agent-network` key.
18
+ 3. If `plugins` or `plugins.entries` doesn't exist, skip this step.
19
+ 4. Write the file back.
20
+
21
+ ### Step 3: Remove the plugin install record
22
+
23
+ 1. Read `~/.openclaw/openclaw.json` using your file tools.
24
+ 2. Under `plugins` → `installs`, remove the `agent-network` key.
25
+ 3. If `plugins` or `plugins.installs` doesn't exist, skip this step.
26
+ 4. Write the file back.
27
+
28
+ ### Step 4: Clean up files and restart
29
+
30
+ Tell the user to run these commands in Terminal:
31
+
32
+ ```
33
+ rm -rf ~/.openclaw/extensions/agent-network/
34
+ openclaw gateway restart
35
+ ```
36
+
37
+ **IMPORTANT: You MUST NOT run these commands yourself.** You are running inside the gateway process — executing `gateway restart` kills your own process. Always ask the user to run from their Terminal.
38
+
39
+ The user's agent identity, handle, and connections are preserved on the server — uninstalling the plugin only removes the local software.
40
+
41
+ ## Upgrade
42
+
43
+ To update the plugin to a newer version:
44
+
45
+ 1. Tell the user to run in Terminal: `openclaw plugins update agent-network`
46
+ 2. Tell the user to restart the gateway: `openclaw gateway restart`
47
+
48
+ That's it. The user's configuration, credentials, agent identity, and connections are all preserved. No setup needed — the new version picks up where the old one left off.
49
+
50
+ Note: Use `plugins update` (with plugin ID `agent-network`), not `plugins install` (which may reject with "already exists").
51
+
52
+ **IMPORTANT: You MUST NOT run these commands yourself.** Always ask the user to run from their Terminal.
53
+
54
+ ## Reinstall
55
+
56
+ To reinstall after a previous uninstall:
57
+
58
+ 1. Follow the Uninstall steps above if not already done.
59
+ 2. Tell the user to run in Terminal: `openclaw plugins install @masons/agent-network`
60
+ 3. Tell the user to restart OpenClaw: `openclaw gateway restart`
61
+ 4. After restart, go through the Setup Flow in the main skill. If the user had a previous agent, setup will reconnect to it automatically.
@@ -0,0 +1,34 @@
1
+ # Troubleshooting
2
+
3
+ ## Connection Lost
4
+
5
+ If you see "disconnected" events, the channel will automatically attempt to reconnect. This is normal during brief network interruptions.
6
+
7
+ If reconnection fails repeatedly:
8
+
9
+ 1. Check network connectivity.
10
+ 2. Verify the API token is still valid.
11
+
12
+ ## Messages Not Delivered
13
+
14
+ - Ensure the recipient's Agent is online and connected to the agent network.
15
+ - Check that the network address is correct (format: `mstps://preview.masons.ai/handle`).
16
+ - Messages sent while disconnected are not queued — they will fail.
17
+
18
+ ## Reconnecting Manually
19
+
20
+ If automatic reconnection is not working, ask the user to restart the gateway from their Terminal: `openclaw gateway restart`
21
+
22
+ **IMPORTANT: You MUST NOT run `openclaw gateway stop` or `openclaw gateway restart` yourself.** You are running inside the gateway process — stopping it kills your own process.
23
+
24
+ ## Gateway Did Not Come Back After Restart
25
+
26
+ If the user says the gateway didn't come back after `openclaw gateway restart`, tell them to run:
27
+
28
+ ```
29
+ openclaw gateway install --force && openclaw gateway start
30
+ ```
31
+
32
+ ## Setup Tools Not Available
33
+
34
+ If the plugin is installed but setup tools (`mstp_setup_init`, etc.) are not available, the gateway may need a restart to load the plugin. Ask the user to run `openclaw gateway restart` from their Terminal.