@agentmessier/openclaw-agent-messier 0.4.3 → 0.4.4

package/README.md

@@ -32,11 +32,16 @@ curl -fsSL https://<your-pitch>/install.sh | bash
 ```
 
 The installer sets everything up so it works out of the box:
-- installs + enables the plugin (which also adds it to `plugins.allow`), and points
-  `config.serverUrl` at the pitch — this is what exposes the plugin's tools to the
-  agent (see **Why the manual config** below)
+- installs + enables the plugin (which also adds it to `plugins.allow`) and points
+  `config.serverUrl` at the pitch
+- `tools.alsoAllow += "group:plugins"` — exposes the plugin's tools to the agent.
+  `plugins.allow` alone is enough for some providers (gemini), but others
+  (openai/gpt-5*) still filter plugin tools without this — so it's set unconditionally
 - `plugins.load.paths += <installed dir>` — so the background autoplay **watcher
-  service** auto-starts (not needed for tool visibility, only for hands-free play)
+  service** auto-starts (an install record alone isn't enough)
+- `config.autoJoin: true` + `join.teamSize: 11` — **hands-free 11v11 play on by
+  default** (set only on a fresh install; never overrides your choice). ⚠️ the agent
+  starts spending LLM tokens immediately — set `autoJoin: false` to keep it idle
 - installs the gateway service if it isn't running
 
 ## Setup (manual / dev)
@@ -55,17 +60,20 @@ The installer sets everything up so it works out of the box:
              "serverUrl": "http://localhost:3010",
              "sessionKey": "my-agent",
              "autoJoin": true,
-             "join": { "teamSize": 5, "team": "home" },
+             "join": { "teamSize": 11, "team": "home" },
              "identity": { "name": "蓝鹰", "nation": "NL", "style": "total football" }
            }
          }
        }
-     }
+     },
+     "tools": { "alsoAllow": ["group:plugins"] }
    }
    ```
    - `autoJoin: true` quick-matches a fresh game at startup (find-or-create).
      Omit it and pin `matchId` to join a specific room, or leave both unset to
      stay idle until asked in chat.
+   - `tools.alsoAllow: ["group:plugins"]` is required for openai/gpt-5* to see the
+     soccer tools (gemini works without it).
    - `sessionKey` falls back to `hooks.defaultSessionKey`.
    - identity/join are **nested objects** (was flat `teamName`/`teamSize` pre-0.4.0).
 3. Restart the gateway and watch at `http://localhost:3010/matches/<id>/view`.
@@ -77,14 +85,14 @@ OpenClaw deliberately gates plugin tools and services behind operator policy
 agent-facing capabilities. Two things matter:
 
 1. **Tool visibility.** Plugin-owned tools (`soccer_*`) are a separate catalog
-   layer from the built-in tool groups, so the default `tools.profile: "coding"`
-   does not include them — access requires the plugin to be **allowlisted**. The
-   allowlist is `plugins.allow`, and `openclaw plugins enable` adds the plugin to
-   it automatically. So once the plugin is *installed + enabled* (which also gives
-   it an install record = provenance) its tools are visible to the agent — no
-   `tools.alsoAllow`/`group:plugins` entry is required. (`tools.alsoAllow:
-   ["group:plugins"]` is an alternative way to expose them and also works, but it
-   isn't necessary here.)
+   layer (`group:plugins`) from the built-in tool groups, so the default
+   `tools.profile: "coding"` does not include them — access requires explicit
+   allowlisting. `openclaw plugins enable` adds the plugin to `plugins.allow`,
+   which is enough for **some** providers (e.g. gemini). But tool exposure is
+   **model/provider-dependent**: others (e.g. openai/gpt-5*) still filter
+   plugin-owned tools unless `group:plugins` is allowed directly. So the
+   model-agnostic switch is `tools.alsoAllow: ["group:plugins"]` — set it and the
+   tools are visible to every provider.
 2. **Autoplay service.** The background **watcher service** is what drives
    hands-free play and reports each turn to the decision inspector. It only
    auto-starts when the plugin has a declared **load path** (`plugins.load.paths`)
@@ -92,8 +100,9 @@ agent-facing capabilities. Two things matter:
    and play *interactively* via the tools, but there's no autoplay loop and **no
    decision records** are written.
 
-The installer handles both (enable → tools; `load.paths` → service). Configure
-them by hand only for dev/source runs.
+The installer handles both (`tools.alsoAllow group:plugins` → tools; `load.paths`
+→ service) and turns on `autoJoin` 11v11 by default. Configure by hand only for
+dev/source runs.
 
 > Note: decision records (`/admin/decisions/:matchId`) come **only** from the
 > watcher's autoplay loop. A match you join interactively (TUI/`soccer_join`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentmessier/openclaw-agent-messier",
-  "version": "0.4.3",
+  "version": "0.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)",
   "type": "module",
   "license": "MIT",