openclaw - 💡(How to fix) Fix [Bug]: Cron agent runs regress after 2026.5.7 with no tool work and plugin export errors [1 pull requests]

Summary

After upgrading a local OpenClaw source install to 2026.5.7, scheduled cron/agent runs appear to regress in two ways:

1. some runs immediately produce a final answer without doing tool work;
2. another persistent cron/helper flow fails with plugin import/export errors involving bundled runtime dependencies.

Environment

• OpenClaw: 2026.5.7
• OS: macOS 26.3.1 arm64
• Install type: local source checkout
• Gateway: local loopback LaunchAgent
• Affected workflows: scheduled cron tasks that use an agent to summarize email triage

What happened

Three email cron workflows ran after the 2026.5.7 update:

P1 cron

The run immediately replied:

Sem P1 relevante no período.

There was no evidence in the session transcript that it called the configured Gmail tool before producing that final answer.

P2 cron

The run replied with a promise-style final answer:

Perfeito — vou rodar a triagem P2 das últimas 24h...

and then stopped. It did not actually perform the triage.

P3 persistent/helper cron

The helper path failed with runtime/plugin import errors. Representative errors:

ERR_PACKAGE_PATH_NOT_EXPORTED: No "exports" main defined in .../node_modules/@mariozechner/pi-ai/package.json
ERR_PACKAGE_PATH_NOT_EXPORTED: No "exports" main defined in .../node_modules/@mariozechner/pi-coding-agent/package.json

The logs showed many bundled plugins failing to load due to these package export errors, followed by model fallback/diagnostic failures.

The local Gmail CLI/tool itself was checked independently and was working/authenticated, so this does not appear to be a Google auth failure.

Expected behavior

Cron-triggered agent runs should either:

• execute the requested tool-backed workflow and produce a real summary; or
• fail with a clear error if tool/plugin loading is broken.

They should not produce a final answer that only promises future action, nor should helper flows break due to bundled dependency export issues after an update.

Actual behavior

• P1 produced a final answer with no visible tool work
• P2 produced a promise and stopped
• P3 failed in runtime/plugin loading with ERR_PACKAGE_PATH_NOT_EXPORTED

Why this matters

This makes scheduled automation unreliable after 2026.5.7: the system may appear to have completed cron work while it either did nothing or failed internally.

Notes

The source checkout reported OpenClaw 2026.5.7 and gateway health was otherwise OK. This may be related to runtime/plugin dependency packaging or a change in how scheduled agent turns decide whether to use tools before returning final answers.