docs(feishu): clarify oc_ group allowlist vs ou_ command allowFrom for /reset by lonfr · Pull Request #26835 · openclaw/openclaw

lonfr · 2026-02-25T19:59:14Z

Summary

Problem: Feishu docs/examples can be misread as using ou_* values for groupAllowFrom, and don’t clearly call out that group control commands (e.g. /reset, /new) require allowing the sender open_id via allowFrom (global or per-group).
Why it matters: Users may configure group allowlisting correctly (group accepted) but still see /reset//new “no-op” in groups and misdiagnose it as a regression.
What changed: Clarified oc_* (group chat_id) vs ou_* (user/bot open_id) and added a minimal per-group allowFrom example for control commands in docs/channels/feishu.md and docs/zh-CN/channels/feishu.md.
What did NOT change (scope boundary): No code or runtime behavior changes; docs only.

Change Type (select all)

✅ Docs

Scope (select all touched areas)

✅ Integrations

Linked Issue/PR

Related # 25683

User-visible / Behavior Changes

None

Security Impact (required)

New permissions/capabilities? (No)
Secrets/tokens handling changed? (No)
New/changed network calls? (No)
Command/tool execution surface changed? (No)
Data access scope changed? (No)
If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

OS: Ubuntu 22.04.5 LTS
Runtime/container: local gateway (systemd / CLI)
Model/provider: N/A (docs-only)
Integration/channel (if any): Feishu
Relevant config (redacted):
- channels.feishu.groupPolicy=allowlist
- channels.feishu.groupAllowFrom=["oc_..."]
- channels.feishu.groups.<oc_...>.allowFrom=["ou_..."]

Steps

Configure Feishu group allowlisting so the bot receives messages from a specific group (chat_id oc_*).
Send /reset @bot in the group with sender not in allowFrom.
Add sender open_id (ou_*) to allowFrom (global or per-group) and restart gateway.

Expected

/reset and /new trigger session reset/new in the group after sender is allowed.

Actual

Without sender ou_* in allowFrom, group messages are received/forwarded but control commands do not trigger reset/new.

Evidence

Docs change only; see updated examples in:

docs/channels/feishu.md
docs/zh-CN/channels/feishu.md

Observed behavior in gateway logs matched the docs clarification; no code changes included.

Human Verification (required)

What you personally verified (not just CI), and how:

Verified scenarios:
- Confirmed Feishu group /reset//new works after adding sender open_id to allowFrom.
Edge cases checked:
- Mentioned command forms like /reset @bot and /new hello @bot.
What you did not verify:
- No automated docs build checks beyond local review (docs-only).

Compatibility / Migration

Backward compatible? (Yes)
Config/env changes? (No)
Migration needed? (No)
If yes, exact upgrade steps: N/A

Failure Recovery (if this breaks)

How to disable/revert this change quickly:revert this PR (docs only).
Files/config to restore: docs/channels/feishu.md, docs/zh-CN/channels/feishu.md
Known bad symptoms reviewers should watch for:N/A (docs-only)

Risks and Mitigations

None

Greptile Summary

Clarifies Feishu group and user ID types (oc_* vs ou_*) and documents the sender-level allowFrom requirement for control commands in groups. The PR fixes a documentation ambiguity where users might incorrectly use ou_* user IDs in groupAllowFrom (which expects group oc_* IDs), and adds an example showing how to configure per-group allowFrom to authorize specific users for /reset and /new commands.

Key changes:

Renamed "Allow specific users in groups only" → "Allow specific groups only" with clarifying comment about oc_* format
Added new section explaining control command authorization requires sender open_id in per-group allowFrom
Applies to both English and Chinese documentation

Confidence Score: 5/5

Documentation-only PR with no code changes - safe to merge immediately
Perfect score (5/5) because: (1) changes are documentation-only with zero runtime impact, (2) technical accuracy verified against implementation in bot.ts and config-schema.ts, (3) addresses a real user confusion point about oc_* vs ou_* ID types, (4) examples are syntactically correct and consistent with existing patterns
No files require special attention - both documentation files contain equivalent changes in English and Chinese

_{Last reviewed commit: fa1b643}

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com>

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com> (cherry picked from commit 14c6345)

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com>

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com> (cherry picked from commit 6e64530)

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com>

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com> (cherry picked from commit 6e64530)

…r /reset (openclaw#26835) * docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom * docs(feishu): avoid direct edits to generated zh-CN docs --------- Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com>

openclaw-barnacle bot added docs Improvements or additions to documentation channel: feishu Channel integration: feishu size: XS labels Feb 25, 2026

lonfr changed the title docs(feishu): clarify oc_ group allowlist vs ou_ command allowFrom for /reset** docs(feishu): clarify oc_ group allowlist vs ou_ command allowFrom for /reset Feb 25, 2026

lonfr mentioned this pull request Feb 25, 2026

[Bug]: Group chat /reset and /new commands no longer trigger session reset (Regression) #25683

Closed

lonfr and others added 2 commits February 27, 2026 22:28

docs(feishu): clarify oc_* group allowlist vs ou_* command allowFrom

f3d4956

docs(feishu): avoid direct edits to generated zh-CN docs

0c8c437

Takhoffman force-pushed the docs/feishu-reset-allowfrom branch from fa1b643 to 0c8c437 Compare February 28, 2026 04:29

Takhoffman merged commit 6e64530 into openclaw:main Feb 28, 2026
20 of 21 checks passed

github-actions bot mentioned this pull request Feb 28, 2026

📡 Upstream Digest — 2026-02-28 04:49 UTC curtismercier/openclaw-mods#142

Open

github-actions bot mentioned this pull request Mar 1, 2026

cherry-pick: upstream docs commits (2026-03-01-0443) hughdidit/DAISy-Agency#141

Closed

6 tasks

alexey-pelykh mentioned this pull request Mar 10, 2026

Cherry-pick: Documentation updates remoteclaw/remoteclaw#684

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

docs(feishu): clarify oc_ group allowlist vs ou_ command allowFrom for /reset#26835

docs(feishu): clarify oc_ group allowlist vs ou_ command allowFrom for /reset#26835
Takhoffman merged 2 commits intoopenclaw:mainfrom
lonfr:docs/feishu-reset-allowfrom

lonfr commented Feb 25, 2026 •

edited by greptile-apps bot

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

lonfr commented Feb 25, 2026 • edited by greptile-apps bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Greptile Summary

Confidence Score: 5/5

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

lonfr commented Feb 25, 2026 •

edited by greptile-apps bot

Loading