Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix reminder-guard appends false "did not schedule a reminder" disclaimer when reminder is written via plugin tool [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70666•Fetched 2026-04-24 05:54:57
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
fstraszfstrasz
Participants
fstraszfstrasz

When an agent uses a registered plugin tool to schedule a reminder, the runtime reminder-guard appends the following disclaimer to the agent reply:

"Note: I did not schedule a reminder in this turn, so this will not trigger automatically."

The disclaimer is false. The reminder IS scheduled and fires correctly. The guard checks successfulCronAdds === 0 but has no awareness of plugin-tool writes as a valid reminder primitive.

Root Cause

The guard fires when:

  • Agent reply matches reminder-intent patterns (I'll ping, I'll remind, I'll follow up, etc.)
  • successfulCronAdds === 0 (no OpenClaw cron was added in the turn)
  • No OpenClaw cron session covers the target

The guard does not inspect whether a registered plugin tool was invoked that produced a scheduled event. No config toggle found after grepping installed runtime for reminderGuard, UNSCHEDULED_REMINDER, and adjacent flags.

Code Example

Set! I'll ping you at 7:56 AM.
Note: I did not schedule a reminder in this turn, so this will not trigger automatically.
RAW_BUFFERClick to expand / collapse

Summary

When an agent uses a registered plugin tool to schedule a reminder, the runtime reminder-guard appends the following disclaimer to the agent reply:

"Note: I did not schedule a reminder in this turn, so this will not trigger automatically."

The disclaimer is false. The reminder IS scheduled and fires correctly. The guard checks successfulCronAdds === 0 but has no awareness of plugin-tool writes as a valid reminder primitive.

Environment

  • OpenClaw: 2026.4.22 (confirmed present across 2026.4.15-2026.4.22)
  • Host: macOS (Mac mini)
  • Plugin: custom blackboard_write AgentTool registered via api.registerTool()
  • Channel: Telegram (interactive DMs)

Reproduction

Agent receives: "remind me in 5 minutes to get some fresh dandy blend."

Agent reply delivered to user (Telegram):

Set! I'll ping you at 7:56 AM.
Note: I did not schedule a reminder in this turn, so this will not trigger automatically.

The reminder was written to a SQLite event store via blackboard_write and fired correctly at the scheduled time. The disclaimer was factually wrong.

Root cause

The guard fires when:

  • Agent reply matches reminder-intent patterns (I'll ping, I'll remind, I'll follow up, etc.)
  • successfulCronAdds === 0 (no OpenClaw cron was added in the turn)
  • No OpenClaw cron session covers the target

The guard does not inspect whether a registered plugin tool was invoked that produced a scheduled event. No config toggle found after grepping installed runtime for reminderGuard, UNSCHEDULED_REMINDER, and adjacent flags.

Expected behavior

The reminder-guard should recognize that a registered plugin tool invocation producing a scheduled event is a valid scheduling action, equivalent to successfulCronAdds > 0 for the purpose of the guard check.

Ask

  1. Expose a way for plugin tools to signal to the runtime that a scheduled event was created (e.g. a return value flag, API call, or counter increment) so the reminder-guard can suppress the disclaimer.
  2. Alternatively, provide a per-agent config flag to disable the reminder-guard for agents using plugin-managed scheduling.

Any plugin author implementing a reminder primitive outside OpenClaw cron will encounter this. The disclaimer directly contradicts the agent confirmation, eroding user trust.

extent analysis

TL;DR

The reminder-guard disclaimer can be suppressed by exposing a way for plugin tools to signal scheduled event creation or by adding a per-agent config flag to disable the reminder-guard.

Guidance

  • Investigate adding a return value flag or API call to the blackboard_write AgentTool to indicate that a scheduled event was created.
  • Consider introducing a counter increment to track scheduled events created by plugin tools, allowing the reminder-guard to recognize these events.
  • Evaluate the feasibility of adding a per-agent config flag to disable the reminder-guard for agents using plugin-managed scheduling.
  • Review the OpenClaw API documentation to determine if there are existing mechanisms for plugin tools to communicate with the runtime about scheduled events.

Example

// Example of a potential return value flag
const scheduledEventCreated = true;
api.registerTool('blackboard_write', (args) => {
  // ...
  return { scheduledEventCreated };
});

Notes

The solution will depend on the specific implementation details of the OpenClaw API and the blackboard_write AgentTool. Further investigation is needed to determine the best approach.

Recommendation

Apply a workaround by introducing a return value flag or API call to signal scheduled event creation, as this approach is more targeted and less likely to introduce unintended consequences.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The reminder-guard should recognize that a registered plugin tool invocation producing a scheduled event is a valid scheduling action, equivalent to successfulCronAdds > 0 for the purpose of the guard check.

#api#agent setup#task chaining#parallel task#integration issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix reminder-guard appends false "did not schedule a reminder" disclaimer when reminder is written via plugin tool [1 participants]