Skip to main content
MonoGuard is the file-defense daemon and the DIFF layer’s only writer. It consumes watcher changes, records point-in-time checkpoints, and keeps file copies for content above the configured threshold. Production use should install it as a restart-on-crash OS service rather than relying on an unsupervised foreground process. Published contract: monoguard 0.2.1, OpenCLIs build 2026-07-12-192817. The executing binary, OpenCLIs registry, and public CDN metadata agree on this release.

Quick Start

Complete Command Reference

State and Recovery

The current configuration is ~/.monolex/monoguard.toml. Its [backup] section controls dir, keep_per_file, never_delete_base, extensions, exclude, and file_copy_threshold. Defaults are ~/monoguard-backups, ten versions per file, BASE retention, all extensions, common temporary-file exclusions, and a 102,400-byte (100 KiB) copy threshold. Do not use older ~/.config/monoguard/... paths.
There is no event backfill after a dead period. Replaying old watcher events against today’s files would fabricate wrong-dated diffs, so MonoGuard resumes forward from revival. status and service status must both be healthy before calling the DIFF layer live. service install prefers the stable signed ~/.openclis/bin/monoguard, registers ai.monolex.monoguard, enables run at load and restart-on-crash, and starts it with the start argument. On macOS the log is ~/Library/Logs/Monolex/monoguard.log; other platforms use the Monolex runtime log directory. During this audit the installed service and daemon reported the same PID, installed=true, running=true, and a one-second heartbeat age. That is a point-in-time runtime proof, not a guarantee for another machine.

Release Platforms

Relationships