RescueTime vs Timeneye
Side-by-side trajectory, velocity, and editorial themes.
RescueTime's feed is all blog essays — no product signal to read
The crawled feed for RescueTime is its marketing blog, not a product changelog. Every entry is an opinion essay on work culture — busyness, meeting cost, hybrid teams, freelancing, time-blocking — with no reference to the RescueTime time-tracking product's features, releases, or fixes. There is no shipping activity to interpret here.
Nothing about the product's direction can be inferred from these posts; they reflect a content-marketing cadence, not engineering output. To produce meaningful commentary the signal source needs to be repointed from blog.rescuetime.com to an actual release or changelog feed.
Insufficient data: this feed carries no product releases, so no next product move can be predicted from it.
Timeneye, now Lucen Track, adds MCP access and rounds out time tracking
Timeneye rebranded to Lucen Track and is filling the gaps of a serious time-tracking tool: custom fields across every object, global non-billable phases and tags, time-off tracking with approvals, and an Outlook add-in. The standout is an MCP server that lets AI assistants read and write time entries directly.
The product is maturing from timesheets toward a configurable work-and-billing record while opening an AI-interop surface. The MCP server bets that users will manage time through assistants like Claude and Cursor rather than only the app UI, alongside steadier depth work in billability and custom fields.
Expect the AI/MCP surface to deepen with more actions and reporting exposed to assistants, plus continued billing-side depth as the non-billable and custom-field work points toward richer invoicing. The rebrand hints at more products consolidating under the Lucen umbrella.
See more alternatives to RescueTime →
See more alternatives to Timeneye →