compact-guardian

You can stop memory auto compaction failures by triggering a circuit-breaker that halts automatic compression for the affected session after three consecutive failures. The mechanism then notifies you via Telegram to intervene manually.

A memory compaction circuit-breaker is a safeguard that monitors automatic compression processes and trips after three consecutive failures. It stops further automated attempts in the affected gateway session and alerts the user through Telegram.

To reset the failure counter after manually fixing memory compression, you run the success command on the affected session. This clears the failure tracking, deactivates the circuit-breaker, and resumes normal automated workflows.

Yes, Telegram is required to receive notifications when the circuit-breaker triggers. The system sends an alert to notify you that automatic compression has been halted and a manual /compact intervention is required.

Yes, the guardian mechanism tracks per-session compression failures independently across gateway sessions. It exposes fail, guardian, success, and reset commands to increment, check, clear, and manage the failure counters for each specific session.

Automatic memory compression stops after three failures because the circuit-breaker mechanism is designed to prevent continuous error loops. By halting the process and requiring a manual /compact command, it ensures the underlying issue is resolved before automation resumes.