openclaw - 💡(How to fix) Fix ACP task maintenance accepts stale session-store rows as valid backing sessions [1 comments, 2 participants]

TL;DR

Strengthening the backing-session detection in ACP maintenance to require ACP identity, non-terminal state, and runtime liveness check is likely to fix the issue.

Guidance

• Review the task-registry.ts file to ensure it correctly handles the loading of task-registry-control.runtime artifacts, especially in dev/linked installs.
• Modify the ACP task maintenance logic to verify the existence of a valid backing session based on ACP-owned session markers and non-terminal states before assuming a live session exists.
• Consider adding a runtime liveness check to confirm the session is still active, as ideally suggested in the expected behavior.
• Ensure that task-registry-control.runtime is included in the build artifacts to enable successful cancellation of tasks using openclaw tasks cancel <id>.

Example

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

Notes

The provided guidance assumes that the issue lies within the ACP task maintenance logic and the handling of task-registry-control.runtime artifacts. Further investigation into the specific implementation details may be necessary to provide a complete solution.

Recommendation

Apply the workaround by strengthening the backing-session detection in ACP maintenance, as this directly addresses the observed behavior and aligns with the expected behavior described in the issue.