Thinking of a new paradigm for recording

It'd be really great if the user doesn't have to juggle between the terminal and the browser. The only way to do that is to have the screenshot taking action happen in the browser. Two options:
1. Assign a keyboard shortcut. Could introduce a fast screen flash to indicate screen capturing.
2. Automatically take screenshot at each relevant event. Stuff like key entering could get a delay before capturing screenshot.

Both open doors to the possibility of removing the distinction between live replay and ordinary chained replay, since without the windows switching delay the whole testing can be replayed live without too much useless time gaps. Reducing the remaining time gaps can be done by Huxley itself when relevant, i.e. between keystrokes.

The issue names no files, tests, or entry points. Start by tracing the existing screenshot-taking flow between the terminal and browser, then compare the keyboard-shortcut and event-triggered approaches. Done would require an agreed design for browser capture, timing delays, and the relationship between live and chained replay.

Written by the indexing model from the issue text.