framewatch / Documentation
framewatch, in detail
Screen capture that only fires at moments that mean something
Project brief
Continuous screen capture floods a coding agent's context with near-duplicate frames. An on-demand screenshot misses everything in between. framewatch sits in the middle: it watches one window and writes a frame only at semantically meaningful moments.
It captures when the window settles after a burst of change, when a spinner starts or stops animating, and on a throttle when a volatile region such as a counter or a log tail updates. Each frame carries timestamped metadata describing why it was taken, so an agent can reconstruct what happened without a frame stream.
What is included
• Event-driven capture on settle, on busy-indicator transitions and on throttled volatile regions
• Timestamped metadata alongside every frame so an agent knows why it exists
• Published to crates.io with docs.rs documentation and CI
• Single-binary Rust, no runtime dependencies
Current status
This project is shipping. Its public documentation will evolve with the product.
Questions and support
For questions about framewatch, contact DWMM Holdings with the project name and a concise description of what you need. Please do not send credentials or sensitive information by email.