New

Agent time sets itself up in one page, and needs nothing from you day to day

Enabling agent time now opens a setup checklist, nothing is recorded until there is a default agent rate, and agent time from connected repositories becomes time entries at the end of each day unless an admin turns that off.

Enabling Agent time under Settings → Add-ons now takes you to Settings → Agent time → Setup, a checklist that says what is done and what is left:

  • A default agent rate, which is required. You set it right there. Until a workspace has a rate for all its work, agent time records nothing, and each developer's agent says it is not set up yet, instead of collecting time that could never be accepted. A rate for one client, one project or one agent does not count as the default. Time from before the rate was set is not sent later.
  • Repositories: how many are connected, with a button to connect more.
  • Accept automatically, now on by default. Agent time from a connected repository becomes a time entry once the day has ended, without anybody accepting it. People can still reduce or delete such an entry, and deleting one puts its time back in their pending list. A workspace where an admin had turned it off keeps it off. Time mapped by a .timetrakkr.json file in a repository is still never accepted automatically.
  • Roll out to your team: the install command for each agent, and how to make the plugin required for everyone, once the plugins are published.

The plugins are not published yet. Until they are, the rollout step says so rather than showing a command that would not work, and developers load a plugin from a local copy as before.

The assistant can answer "is agent time set up?" too.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free