Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

GroupChatSchema.historyLimit in src/config/zod-schema.core.ts uses .positive() which rejects 0, while every other historyLimit schema in the codebase uses .min(0). Setting messages.groupChat.historyLimit: 0 causes a silent config reload failure — the Zod validation rejects the value, and the runtime falls back to the previously cached config with no prominent error.

Steps to reproduce

1. Set messages.groupChat.historyLimit: 0 in openclaw.json (intending to disable group chat history).
2. Trigger a config reload (or restart).
3. Observe that the config change is silently rejected — the runtime continues with the previous config value (default 50).

For comparison:

1. Set channels.whatsapp.historyLimit: 0 — this works correctly because the channel-level schema uses .min(0).

Expected behavior

messages.groupChat.historyLimit: 0 should be accepted, consistent with DmConfigSchema.historyLimit (line 374, same file) and all channel-level historyLimit schemas, which use .min(0) and accept 0 to mean "no history."

Actual behavior

Zod validation rejects 0 because .positive() requires > 0. The config reload fails silently — the runtime keeps using the previously cached config. There is no prominent error surfaced to the user.

OpenClaw version

2026.4.11

Operating system

Linux (Ubuntu)

Install method

pnpm dev (source checkout)

Model

N/A — config schema validation bug, not model-specific

Provider / routing chain

N/A — config schema validation bug, not provider-specific

Logs, screenshots, and evidence

The inconsistency in src/config/zod-schema.core.ts:

// Line 364-370: GroupChatSchema — uses .positive(), rejects 0
export const GroupChatSchema = z
  .object({
    mentionPatterns: z.array(z.string()).optional(),
    historyLimit: z.number().int().positive().optional(),  // <-- BUG: .positive() rejects 0
  })
  .strict()
  .optional();

// Line 372-376: DmConfigSchema — uses .min(0), accepts 0
export const DmConfigSchema = z
  .object({
    historyLimit: z.number().int().min(0).optional(),      // <-- correct
  })
  .strict();

All historyLimit occurrences in the file:

• Line 367: GroupChatSchema — .positive() (rejects 0) ← the only outlier
• Line 374: DmConfigSchema — .min(0) (accepts 0)
• Line 433: channel-level schema — .min(0) (accepts 0)

Impact and severity

• Affected: Any user trying to disable group chat history via messages.groupChat.historyLimit: 0 or per-agent groupChat.historyLimit: 0
• Severity: Medium — the config is silently ignored, which is confusing and hard to debug
• Frequency: 100% reproducible when setting the value to 0
• Consequence: Users cannot disable group chat history through the group chat config path, and the silent failure makes it hard to understand why the setting has no effect

Additional information

The fix is a one-line change: replace .positive() with .min(0) on line 367 of src/config/zod-schema.core.ts. Happy to open a PR if this is confirmed as unintentional.