Skip to main content
8.0 is rolling out, not yet on every machine. These pages describe 8.0 because that is the version being deployed. If your fleet is still on 7.6.7.1, the differences below are the ones that matter, and everything else on this site applies to both. Check the Versions page to see where your machines actually are.

​
Backend hostnames, with a fallback

The client now connects to cloud.reclaimtime.com, or to your organisation’s own hostname if you have a dedicated backend, and falls back automatically to the previous backend hostname if it cannot reach the first.
Both hostnames in the pair have to be allow-listed. Allowing only the new one removes the safety net that the fallback exists to provide, and allowing only the old one stops 8.0 clients on their primary route. See Domains and URLs to allow-list.
Earlier clients went to the previous hostname directly and had no fallback at all, so during a rollout both are in use across the fleet.

​
Longer allowances for fullscreen work

A session still closes after a short time without keyboard or mouse input. 8.0 gives fullscreen applications and fullscreen video a longer allowance, alongside the existing ones for meetings and video, because in both the person is engaged without touching anything. This makes training, presenting and long calls read as continuous work rather than as a run of short fragments separated by gaps. It does not add time that was not spent: the idle period is still deducted when the session closes. See How tracking works.

​
Group names are read from the group

The client now reads each group’s current name from the group itself when it signs in, rather than relying on a copy stored on the account. The practical effect is that renaming a group now reaches new activity as soon as machines next sign in. On earlier clients the stored copy could keep stamping the old name onto new rows until the account was edited, which is why a rename could look as though it had not taken effect. Rows already written keep the name they were written with, as before.

​
Upgrading

Machines on the channel update themselves. Nobody needs administrator rights for the update, because it runs through the elevated task that starts the client. Two things to do before the rollout reaches the fleet:
  1. Allow-list the new hostnames, alongside the existing ones. This is the only change that can stop 8.0 working, and its symptom is a client that will not sign in.
  2. Set Latest Version in Settings to the version you have published, once you have published it, so the Versions page reports against the right target.

​
Still not in this release

Unchanged from 7.6.7.1, and listed so nobody goes looking:
  • Meeting detection covers Microsoft Teams and Skype only. Time in a softphone or another conferencing tool is recorded as ordinary focused time in that application.
  • Idle time is measured but not reported. The client tracks it and the dashboard has nowhere to show it.
  • macOS and Linux. There is still no ReclaimTime build for either.
Checked against ReclaimTime client 8.0.0.9 and dashboard V3 on 5 September 2026.