You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Memory/wiki: preserve representation from both corpora in `corpus=all` searches while backfilling unused result capacity, so memory hits are not starved by numerically higher wiki integer scores. Fixes #77337. Thanks @hclsys.
`channels.zalouser.allowFrom` accepts user IDs or names. During setup, names are resolved to IDs using the plugin's in-process contact lookup.
84
+
`channels.zalouser.allowFrom` should use stable Zalo user IDs. During interactive setup, entered names can be resolved to IDs using the plugin's in-process contact lookup.
85
+
86
+
If a raw name remains in config, startup resolves it only when `channels.zalouser.dangerouslyAllowNameMatching: true` is enabled. Without that opt-in, runtime sender checks are ID-only and raw names are ignored for authorization.
85
87
86
88
Approve via:
87
89
@@ -93,13 +95,13 @@ Approve via:
93
95
- Default: `channels.zalouser.groupPolicy = "open"` (groups allowed). Use `channels.defaults.groupPolicy` to override the default when unset.
94
96
- Restrict to an allowlist with:
95
97
-`channels.zalouser.groupPolicy = "allowlist"`
96
-
-`channels.zalouser.groups` (keys should be stable group IDs; names are resolved to IDs on startup when possible)
98
+
-`channels.zalouser.groups` (keys should be stable group IDs; names are resolved to IDs on startup only when `channels.zalouser.dangerouslyAllowNameMatching: true` is enabled)
97
99
-`channels.zalouser.groupAllowFrom` (controls which senders in allowed groups can trigger the bot)
98
100
- Block all groups: `channels.zalouser.groupPolicy = "disabled"`.
99
101
- The configure wizard can prompt for group allowlists.
100
-
- On startup, OpenClaw resolves group/user names in allowlists to IDs and logs the mapping.
102
+
- On startup, OpenClaw resolves group/user names in allowlists to IDs and logs the mapping only when `channels.zalouser.dangerouslyAllowNameMatching: true` is enabled.
101
103
- Group allowlist matching is ID-only by default. Unresolved names are ignored for auth unless `channels.zalouser.dangerouslyAllowNameMatching: true` is enabled.
102
-
-`channels.zalouser.dangerouslyAllowNameMatching: true` is a break-glass compatibility mode that re-enables mutable group-name matching.
104
+
-`channels.zalouser.dangerouslyAllowNameMatching: true` is a break-glass compatibility mode that re-enables mutable startup name resolution and runtime group-name matching.
103
105
- If `groupAllowFrom` is unset, runtime falls back to `allowFrom` for group sender checks.
104
106
- Sender checks apply to both normal group messages and control commands (for example `/new`, `/reset`).
105
107
@@ -181,7 +183,7 @@ Accounts map to `zalouser` profiles in OpenClaw state. Example:
181
183
182
184
**Allowlist/group name didn't resolve:**
183
185
184
-
- Use numeric IDs in `allowFrom`/`groupAllowFrom`/`groups`, or exact friend/group names.
186
+
- Use numeric IDs in `allowFrom`/`groupAllowFrom` and stable group IDs in `groups`. If you intentionally need exact friend/group names, enable `channels.zalouser.dangerouslyAllowNameMatching: true`.
0 commit comments