openclaw - 💡(How to fix) Fix Feature Request: Allow cron jobs to route to subagent persistent sessions [1 participants]

Summary

Currently, cron jobs only support sessionTarget: main or sessionTarget: isolated. There is no way to route a cron job to an existing subagent persistent session (created via sessions_spawn with thread: true).

Use Case

In a multi-agent setup, we have specialized sub-agents (e.g., a fandom news collector) with their own AGENTS.md rules, personality (SOUL.md), and persistent session history. We want cron jobs to directly wake up these sub-agents to perform their tasks, rather than:

1. Option A: Cron → isolated session → sessions_send to subagent (adds latency, double context load)
2. Option B: Cron → isolated session doing the work directly (works but loses sub-agent personality/rules from AGENTS.md/SOUL.md)

Proposed Solution

Add a new sessionTarget option, e.g. sessionTarget: subagent, that accepts a sessionKey pointing to an existing subagent persistent session. The cron job would then execute within that sub-agent session context, respecting its SOUL.md, AGENTS.md, and conversation history.

Alternatively, allow sessionTarget: isolated to optionally inherit a sub-agent workspace config (SOUL.md, AGENTS.md) without routing to its session.

Current Behavior

Using --session-key with sessionTarget: isolated sets the key but the session still runs as isolated (new session each time), ignoring the sub-agent existing session. The sessionKey only affects UI grouping, not actual routing.

Environment

• OpenClaw 2026.4.15
• subagent sessions created via sessions_spawn with thread: true, mode: session