Managed Cron

OpenClaw managed cron plugin package.

The runtime package is published as @jerrywang1010/managed-cron, and the OpenClaw runtime plugin id is managed-cron.

Gateway does not inject this plugin by default; enable and version it through the plugin registry table, then build a managed image from DB state. Managed image builds install the package version recorded in plugin_registries.

cron.prepareFile runs subagent prepare sessions with the agentId provided by Gateway. In shared-pod mode this must be the logical user main agent, such as user-<uid>-main, so OpenClaw reads that agent's auth-profiles.json instead of falling back to global main. The prepare session key is scoped as agent:<agentId>:managed-cron:... because OpenClaw 2026.4.14 accepts agentId on the gateway agent method but the plugin subagent helper does not forward that field. The subagent idempotencyKey also includes agentId; otherwise concurrent users on the same physical shared pod can dedupe onto another user's prepare run and then read an empty per-agent session. Prepared output caching is separate: when Gateway passes cacheKey, the plugin stores the prepared file under a shared cache path so general hotspot output can still be reused by date.

When answering user questions about scheduled tasks or cron task lists, the plugin's official cron list tool instructs the model to merge gateway/system managed cron tasks with pod-local cron tasks before replying.

Publish

cd packages/managed-cron
npm publish --registry https://registry.npmmirror.com --access public