Shipping · Installed software
framewatch
A recorder that stays quiet until something worth keeping happens.
Anyone whose screen recording is 99% nothing and 1% the thing they needed.
- Built on
- Rust + Windows API
- Runs locally
- On hardware you already own
- History
- 42 commits, in the open record
What it is
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.
Capabilities
What it actually does.
Anyone whose screen recording is 99% nothing and 1% the thing they needed.
Event-driven capture on settle
Event-driven capture on settle, on busy-indicator transitions and on throttled volatile regions
Timestamped metadata alongside
Timestamped metadata alongside every frame so an agent knows why it exists
Published to crates.io
Published to crates.io with docs.rs documentation and CI
Single-binary Rust
Single-binary Rust, no runtime dependencies
How it works
3 moves, end to end.
Install it
framewatch runs on your machine. There is no account to make and no service to depend on.
Point it at your work
It reads what you already have, in the formats you already keep it in.
Keep the result
Output stays where you put it. Nothing is uploaded to make the feature work.
Specification
Made of, and made when.
Read from the repository at build time rather than typed onto a marketing page.
- State
- Shipping
- Discipline
- Developer tooling
- Shape
- Installed software
- Started
- Jun 2026
- Last change
- Aug 2026
- Commits
- 42
- Rust
- Windows API
- crates.io
- Rust 100%
Next
Install framewatch
Published to crates.io. Pick the capture backend for your platform — the detection engine is the same on all three.
cargo install framewatch --features wgc
cargo install framewatch --features macos
cargo install framewatch --features linux-x11
cargo add framewatch --no-default-features
Add gui for the window picker, or record for narrated capture. macOS asks for Screen Recording permission on first run; Wayland is not supported yet.
Questions, or something it does not do yet? Email dmoore@dwmmholdings.com