I’m using Cursor via Remote SSH on a Linux server with WakaTime extension 30.2.0.
The problem is that Cursor AI activity is not tracked correctly. When Cursor AI modifies files that I don’t currently have open, WakaTime often tracks nothing or only shows the activity as Unknown.
Example: I can work for around 6 hours by prompting Cursor AI, reviewing changes, and letting it edit code across the workspace, but WakaTime may only track 1–2 hours.
I previously created a fork that watched file changes directly and then tried to identify whether the change came from AI or from human input. That worked a bit better, but it was still not a clean solution.
Am I doing something wrong in my setup, or is this a known limitation/expected behavior with Cursor AI and Remote SSH?
I’m using Cursor via Remote SSH on a Linux server with WakaTime extension 30.2.0.
The problem is that Cursor AI activity is not tracked correctly. When Cursor AI modifies files that I don’t currently have open, WakaTime often tracks nothing or only shows the activity as Unknown.
Example: I can work for around 6 hours by prompting Cursor AI, reviewing changes, and letting it edit code across the workspace, but WakaTime may only track 1–2 hours.
I previously created a fork that watched file changes directly and then tried to identify whether the change came from AI or from human input. That worked a bit better, but it was still not a clean solution.
Am I doing something wrong in my setup, or is this a known limitation/expected behavior with Cursor AI and Remote SSH?