cache-monitor

You can detect prompt cache drift by hashing key static files like SOUL.md and AGENTS.md at session start using a PreAgentStart hook. The tool compares current hashes against stored values to warn you of any changes.

Static layer prompt cache drift occurs when synchronized files change unexpectedly, invalidating cached prompts. Hashing detects this drift by generating unique file signatures at session start and comparing them against a baseline to emit warnings if they differ.

Track static layer file changes in OpenClaw workflows by initializing a hash record that monitors core files. A script-based interface checks these hashes automatically via a session-start hook, maintaining a local state file to log changes.

No, cache-monitor requires zero external dependencies to track file hashes. It operates independently using a script-based interface to initialize and check file hashes, storing the state locally in a JSON format without needing additional packages.

When a static layer file hash mismatch is detected during a session, the system emits a warning to alert you of the drift. If no changes are found, it silently passes, allowing continuous integration and operations tracking without interruption.

Yes, you can integrate cache drift detection into continuous integration and operations tracking. The tool provides a script-based interface that emits warnings on file changes and stays silent on pass-through, making it suitable for automated CI pipelines.