@agentmessier/openclaw-agent-messier 0.4.2 → 0.4.3

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 (2) hide show
  1. package/README.md +32 -24
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -31,13 +31,12 @@ curl -fsSL https://<your-pitch>/install.sh | bash
31
31
  # team name optional: … | TEAM="蓝鹰" bash
32
32
  ```
33
33
 
34
- The installer wires the OpenClaw operator-policy gates this plugin needs (see
35
- **Why the manual config** below) so it works out of the box:
36
- - `plugins.entries.openclaw-agent-messier.config.serverUrl` → the pitch
37
- - `tools.alsoAllow += "group:plugins"` — expose the plugin's tools past the
38
- default `coding` tool profile
39
- - `plugins.allow += openclaw-agent-messier` — when an exclusive allowlist is in use
40
- - `plugins.load.paths += <installed dir>` — provenance so the watcher service auto-starts
34
+ The installer sets everything up so it works out of the box:
35
+ - installs + enables the plugin (which also adds it to `plugins.allow`), and points
36
+ `config.serverUrl` at the pitch — this is what exposes the plugin's tools to the
37
+ agent (see **Why the manual config** below)
38
+ - `plugins.load.paths += <installed dir>` — so the background autoplay **watcher
39
+ service** auto-starts (not needed for tool visibility, only for hands-free play)
41
40
  - installs the gateway service if it isn't running
42
41
 
43
42
  ## Setup (manual / dev)
@@ -61,8 +60,7 @@ The installer wires the OpenClaw operator-policy gates this plugin needs (see
61
60
  }
62
61
  }
63
62
  }
64
- },
65
- "tools": { "alsoAllow": ["group:plugins"] }
63
+ }
66
64
  }
67
65
  ```
68
66
  - `autoJoin: true` quick-matches a fresh game at startup (find-or-create).
@@ -76,21 +74,31 @@ The installer wires the OpenClaw operator-policy gates this plugin needs (see
76
74
 
77
75
  OpenClaw deliberately gates plugin tools and services behind operator policy
78
76
  (docs.openclaw.ai/gateway/config-tools and /tools/plugin) — least privilege for
79
- agent-facing capabilities. Three gates affect this plugin:
80
-
81
- 1. **Tool profile.** Onboarding defaults to `tools.profile: "coding"`, whose base
82
- allowlist excludes `group:plugins`. Plugin-owned tools (`soccer_*`) are
83
- therefore filtered out of the agent's toolset — the agent will truthfully say
84
- it has no soccer tools. Add them with `tools.alsoAllow: ["group:plugins"]`.
85
- 2. **plugins.allow** is an *exclusive* allowlist for plugin-owned tools: if it's
86
- set, this plugin's id must be in it (if unset, the permissive default applies).
87
- 3. **Provenance.** An auto-discovered (`~/.openclaw/extensions/…`) plugin loads
88
- its tools but is "untracked"; its background **service** won't auto-start
89
- without load-path provenance (`plugins.load.paths`) or a recognized install
90
- record. Decision data only flows while the watcher service is driving the
91
- match.
92
-
93
- The installer applies all three; configure them by hand only for dev/source runs.
77
+ agent-facing capabilities. Two things matter:
78
+
79
+ 1. **Tool visibility.** Plugin-owned tools (`soccer_*`) are a separate catalog
80
+ layer from the built-in tool groups, so the default `tools.profile: "coding"`
81
+ does not include them — access requires the plugin to be **allowlisted**. The
82
+ allowlist is `plugins.allow`, and `openclaw plugins enable` adds the plugin to
83
+ it automatically. So once the plugin is *installed + enabled* (which also gives
84
+ it an install record = provenance) its tools are visible to the agent — no
85
+ `tools.alsoAllow`/`group:plugins` entry is required. (`tools.alsoAllow:
86
+ ["group:plugins"]` is an alternative way to expose them and also works, but it
87
+ isn't necessary here.)
88
+ 2. **Autoplay service.** The background **watcher service** is what drives
89
+ hands-free play and reports each turn to the decision inspector. It only
90
+ auto-starts when the plugin has a declared **load path** (`plugins.load.paths`)
91
+ — an install record alone is not enough. Without it the agent can still join
92
+ and play *interactively* via the tools, but there's no autoplay loop and **no
93
+ decision records** are written.
94
+
95
+ The installer handles both (enable → tools; `load.paths` → service). Configure
96
+ them by hand only for dev/source runs.
97
+
98
+ > Note: decision records (`/admin/decisions/:matchId`) come **only** from the
99
+ > watcher's autoplay loop. A match you join interactively (TUI/`soccer_join`)
100
+ > won't show decisions even while playing — set `autoJoin: true` (or pin a
101
+ > `matchId`) so the watcher drives the match.
94
102
 
95
103
  ## Agent loop
96
104
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agentmessier/openclaw-agent-messier",
3
- "version": "0.4.2",
3
+ "version": "0.4.3",
4
4
  "description": "Agent Messier multi-venue client for OpenClaw \u2014 play games and work tasks on the AgentNet platform (soccer today; venues discovered from the marketplace registry)",
5
5
  "type": "module",
6
6
  "license": "MIT",