TGDC Capture

TGDC Capture records expert work as it happens: a screenshot at every action, plus what the operating system’s accessibility layer reports about the element you acted on. What comes out is an ordered list of steps, the material training and evaluation data is built from.

Get the app

Both panels are filled from /app/latest.json, written by the release workflow.

On first launch

1. 01

   Read and accept the recording notice

   The app opens on the notice reproduced further down this page and will not record until it is accepted. The version accepted is written to disk with the acceptance.

2. 02

   Grant Screen Recording and Accessibility

   Both are blocking. Screen Recording produces the screenshot taken at each action; Accessibility reads which on-screen element you clicked and what it is called. Without both, a step is a bare coordinate with no picture behind it. The app asks macOS for them and links straight to the right pane in System Settings.

   Grant both, then quit and reopen TGDC Capture: a permission does not reach an app that is already running.

3. 03

   Choose where recordings are saved

   A folder on this computer, shown in full on the setup screen and changeable there. Every recording is written inside it.

What is recorded, and what is not

While a session runs, TGDC Capture takes a screenshot of your whole screen at each action. It records what you clicked or scrolled, which on-screen element that was as reported by the operating system’s accessibility layer, and which application and window was in front. For typing it records the number of characters only. This is not a setting, the keystrokes are not captured at all. No microphone is used, and no audio is recorded.

Nothing in the screenshots is blurred, blacked out or anonymised. Whatever is on your screen when you act is in the recording, exactly as it appeared. Close what should not be captured before you start.

Everything is written to the folder you chose, and nothing leaves this computer while you record. You can stop at any time. A finished recording opens in a player, and you submit it or discard it. Submitting uploads that one recording to TGDC, screenshots and step log as captured. Discarding deletes the folder.

Nobody checks a recording for you. Look through it before you submit. The app shows this same statement before your first recording.

Opening the download

On macOS

The macOS build is signed with an Apple Developer ID certificate and has been notarised by Apple, with the notarisation ticket stapled into the disk image. That is why there is no “unidentified developer” block and no right-click workaround: Gatekeeper can attribute the app and does not need the network to check it.

One dialog remains. Because the file was downloaded, macOS asks “TGDC Capture is an app downloaded from the Internet. Are you sure you want to open it?” and names the source. Open is a normal button there, and it appears once.

The signature is checkable without trusting this page. In Terminal, against the downloaded disk image:

spctl -a -vvv -t open --context context:primary-signature ~/Downloads/<file>.dmg
shasum -a 256 ~/Downloads/<file>.dmg

The first prints accepted and source=Notarized Developer ID. The second prints the SHA-256 to compare against the one above. If either disagrees, do not open the file.

On Windows

The Windows build is not code-signed, so Windows cannot say who wrote it. On first run, SmartScreen shows a blue “Windows protected your PC” panel with Publisher: Unknown publisher, and the only visible button is Don’t run. The run option is behind the More info link, which reveals Run anyway.

Clicking through that dialog means running a program Windows cannot attribute to anyone. The warning is correct. What you can check is the file: it came from this page over HTTPS, and its SHA-256 must match the one published above. Verify before you run it. In PowerShell, Get-FileHash .\<file> -Algorithm SHA256 prints the hash to compare.

Last updated · August 2026