openclaw - 💡(How to fix) Fix bug(cron): isolated runs reuse CLI session — cliSessionIds not cleared on forceNew [1 comments, 1 participants]

TL;DR

Clearing the cliSessionIds property when forceNew: true should resolve the issue of accumulated turns in isolated cron runs.

Guidance

• The likely cause is the preservation of cliSessionIds from the previous session entry, which prevents the CLI runtime from starting a fresh session.
• To verify the fix, check that getCliSessionId() returns a new CLI session ID for each isolated cron run, and that the conversation history does not grow indefinitely.
• To mitigate the issue, ensure that cliSessionIds is cleared when isNewSession is true, as shown in the expected behavior code snippet.
• Review the session.ts file to confirm that the cliSessionIds property is properly cleared when forceNew: true.

Example

...(isNewSession && {
  lastChannel: undefined,
  lastTo: undefined,
  lastAccountId: undefined,
  lastThreadId: undefined,
  deliveryContext: undefined,
  cliSessionIds: undefined,      // ← clear cliSessionIds
}),

Notes

This fix assumes that clearing cliSessionIds is sufficient to start a fresh CLI session. If additional steps are required, further investigation may be needed.

Recommendation

Apply the workaround by clearing cliSessionIds when isNewSession is true, as this directly addresses the root cause of the issue and ensures that isolated cron runs start with a fresh session.