Sapience on client VDI, how are productive hours calculated, and how does it handle automated activity?

Hi everyone,

My client recently installed Sapience on our VDI, and I’m trying to understand how its activity tracking and productive-hour calculations work.

The frustrating part is that even when I complete my assigned development work ahead of schedule, I’m still expected to remain logged into the VDI for the rest of the working day. It seems productive hours are being measured separately from the actual work completed.

I tried a basic mouse jiggler, but it doesn’t seem to help. I’m also curious about automated keystrokes and similar approaches, although I suspect these may not work reliably and could potentially be flagged.

A few questions for anyone familiar with Sapience, especially in a managed VDI environment:

What signals does Sapience use to calculate productive hours, keyboard and mouse activity, active applications, application usage duration, or something else?

Does it monitor activity only inside the VDI, or can it also observe the host machine?

Can it distinguish genuine user interaction from mouse-jiggler movements or automated keystrokes?

Are there risks that automated input could be detected or recorded as suspicious activity?

How does it account for legitimate development tasks such as reading code, debugging, reviewing pull requests, and analysing logs when there may be long periods without interaction?

If assigned work is completed early, are there official settings or policies that allow productive hours to reflect actual work rather than continuous interaction?

I’m not looking to compromise the client environment.

I’d like to understand how the software works, what it considers productive activity, and what legitimate options are available when the assigned work is already complete.

Would appreciate insights from anyone who has experience with Sapience and VDI deployments.

Thanks.