openclaw - 💡(How to fix) Fix Cron isolated sessions have no access to main session history for non-default agents [1 participants]

• Error: sessionTarget "main" is only valid for the default agent

TL;DR

To fix the issue, consider modifying the cron job to read raw transcript files from the agent's session directory as a temporary workaround.

Guidance

• Investigate the feasibility of reading raw transcript files (.jsonl) from the agent's session directory to access conversation history.
• Explore alternative approaches to proactively write memory during conversations, reducing reliance on cron jobs.
• Verify the --session isolated behavior for non-default agents to ensure it's not a configuration issue.
• Check the OpenClaw documentation for any updates or planned changes to session management and cron job functionality.

Example

No code example is provided due to the lack of specific implementation details in the issue.

Notes

The provided workaround may not be ideal, and a more robust solution might require changes to the OpenClaw software or its configuration. The feasibility of reading raw transcript files depends on the specific requirements and constraints of the project.

Recommendation

Apply the workaround of reading raw transcript files from the agent's session directory, as it seems to be the most viable temporary solution given the current limitations of the --session isolated mode for non-default agents.