framewatch 0.6.0

Event-driven, change-triggered window capture that emits timestamped screenshots + metadata for AI agents.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32

# framewatch — distribution / integration entry point

This folder is the **entry point for another project or agent** to use framewatch.

| File | What it is |
|---|---|
| `framewatch.exe` | The release binary (built with `cli` + `wgc` + `gui` + `record`). *Not committed to git; produced by the build below.* |
| `framewatch.json` | **Machine-readable manifest** — where the binary is, every command, every flag, and the full output schema. Parse this. |
| `../.agents/skills/framewatch/` | **Codex skill** — native workflow discovery for capture, inspection, and recording tasks. |
| `sample-session/` | A real example of what one capture produces (`timeline.jsonl`, `session.json`, `frames/*.png`, `README_FOR_AGENT.md`). |

Full human/agent guide: [`../docs/AGENT_INTEGRATION.md`](../docs/AGENT_INTEGRATION.md).

## TL;DR

```sh
# discover windows
dist\framewatch.exe windows

# capture one window (blocks; Ctrl+C to stop)
dist\framewatch.exe watch --title "Visual Studio Code" --out ./.framewatch

# then read:  ./.framewatch/<session_id>/timeline.jsonl   (+ session.json, frames/)
# open images only for events with kind == "settled" or "busy_end"
```

## (Re)building the binary

```sh
cargo build --release --features "cli wgc gui record"
# then copy target/release/framewatch.exe -> dist/framewatch.exe
```