Mac screen time not counting keyboard activity? Fix it

Short answer: if TeenyScreeny stops during keyboard-only work, update to version 1.0.2 or later, confirm tracking is not paused, and run the two-minute typing test below. Do not grant Accessibility permission for this. The current app reads macOS's system idle clock, which reports time since any keyboard, mouse, or tablet input without Accessibility access.

teenyscreeny uses that elapsed-time value only to decide whether the Mac is active. It does not receive or store the keys you pressed. It also stops active state when the display sleeps, the screen locks, or another login session owns the console.

This article previously described an older permission-dependent keyboard monitor. That claim is no longer accurate for the current release. Version is now the first check.

Quick diagnosis table

How current keyboard detection works

TeenyScreeny 1.0.2 asks Core Graphics for the seconds since the last input event in the combined login session. It uses the “any input” event type, which Apple documents as keyboard, mouse, or tablet input. This system clock is the authoritative activity signal when it returns a valid value.

A local monitor for mouse movement, clicks, and scrolling remains as a defensive fallback. It does not replace the system clock for keyboard activity. Because TeenyScreeny reads elapsed time rather than the key event itself, the current path does not need Accessibility permission and cannot reveal what you typed.

The app then applies a separate session check. Display sleep, screen lock, and an inactive login session all force the user-active result to false even if the last input was recent. This prevents a wake or fast-user-switch edge case from continuing the counter.

The two-minute typing and lock test

1. Confirm TeenyScreeny is version 1.0.2 or later and tracking is not paused.
2. Use the default five-minute idle threshold or another value longer than this test.
3. Write down the current menu bar time.
4. Type in a text editor for two minutes without touching the mouse.
5. Confirm the menu bar time increased.
6. Lock the Mac for at least 30 seconds, then unlock it.
7. Confirm the locked interval did not count, then type again and confirm counting resumes.

Record the version, pause state, threshold, starting time, ending time, and lock result. That separates the input signal from the session-state gate. If typing still does not count, reopen the current release once and repeat the same test before changing any other setting.

Do not hide a failed test with a longer idle threshold

A longer idle threshold can make the total rise during a typing test even if the keyboard signal is not the reason. The Mac may simply remain inside the grace period created by an earlier mouse movement.

That is why the controlled test records a starting value, types longer than a visible counter interval, and checks lock behavior separately. Once keyboard input and lock state behave correctly, choose a threshold that matches your work. Long reading pauses may justify more time; strict interaction tracking may justify less.

For the full distinction between recent input and awake time, read Mac active screen time vs idle time.

When Apple Screen Time is the better tool

Apple Screen Time is still the better tool when you need app names, website reports, parental controls, Downtime, App Limits, or a formal report. It is built into macOS and uses a different model.

TeenyScreeny is for a narrower job: make active time visible while you work, without collecting a detailed app or website diary. That is why a mismatch between Apple Screen Time and TeenyScreeny is not automatically an error. They answer different questions.

The TeenyApps hub for this cluster is Mac menu bar app shows the wrong status? Verify it. The same evidence chain applies here: identify the source, confirm the target session, observe the readback, and test the result you care about.

Common questions

Why is my Mac screen time not counting keyboard activity?

Current TeenyScreeny 1.0.2 reads the Mac system idle clock for any keyboard, mouse, or tablet input, so keyboard counting does not need Accessibility permission. Update first, then check pause state, idle timeout, screen lock, and sleep with a controlled typing test.

Does TeenyScreeny record what I type?

No. TeenyScreeny reads elapsed time since the last input event. It does not receive or store the keys you pressed, app names, websites, screenshots, document titles, or project labels.

Does TeenyScreeny need Accessibility permission for keyboard activity?

No. In TeenyScreeny 1.0.2, the system idle clock supplies the time since any keyboard, mouse, or tablet input without Accessibility permission. A local mouse monitor remains only as a fallback.

Sources checked

• TeenyScreeny facts were checked against the TeenyScreeny homepage, the live 1.0.2 appcast, and local Swift source for the Core Graphics idle clock, mouse fallback, idle threshold, display sleep, screen lock, and login-session handling.
• Apple Developer: seconds since the last event type.
• Apple Support: Get started with Screen Time on your Mac.
• Apple Support: Track app and device usage in Screen Time on Mac.