openclaw - 💡(How to fix) Fix [Feature]: Agent identity persistence — SOUL.md / IDENTITY.md hot-reload without gateway restart [3 comments, 3 participants]

TL;DR

Implementing a file-watch mechanism or a manual reload trigger can help the agent pick up changes to SOUL.md and IDENTITY.md without requiring a full gateway restart.

Guidance

• Consider adding a file-watch mechanism to monitor changes to SOUL.md and IDENTITY.md and trigger a reload of the agent's context when changes are detected.
• Introduce a manual reload trigger, such as openclaw agent reload-identity, to allow users to manually reload the agent's identity files.
• Evaluate the trade-offs between a file-watch mechanism and a manual reload trigger, considering factors such as performance, complexity, and user experience.
• Investigate how to ensure a seamless transition of the agent's context after reloading the identity files, to maintain ongoing conversations.

Example

No code snippet is provided as the issue does not contain specific implementation details.

Notes

The solution may require careful consideration of edge cases, such as handling concurrent updates to the identity files or ensuring that the agent's context is updated correctly after a reload.

Recommendation

Apply a workaround by introducing a manual reload trigger, such as openclaw agent reload-identity, as it provides a simple and straightforward solution to address the issue, allowing users to manually reload the agent's identity files without requiring a full gateway restart.