The AI clock: how Jenzo tracks AI time

Every ticket in Jenzo can carry two kinds of time: AI time and human time. They are kept apart on purpose, so you can see what your AI tools did and what your people did.

How the AI clock runs

• When an AI tool such as Claude Code or Codex picks up a ticket, it starts its own AI clock on that ticket, with the tool name and the model it runs on.
• When it waits for a person (for example it asked you a question or handed you a last step), the clock pauses. It resumes when the tool continues.
• When the work is done, the tool stops the clock and the time is saved on the ticket.

You do not need to do anything. The connector tells your AI tools to do this as part of their work.

Built-in safety limits

So a forgotten clock cannot inflate your numbers:

• A clock with no sign of activity for 60 minutes stops by itself.
• One session counts at most 240 active minutes.
• A session paused for 72 hours stops.

AI time vs human time

• AI time is always tracked.
• Human time tracking is off by default. Many teams do not want timesheets. An admin can turn it on in Settings > Workspace and members > Time tracking > Track human time.
• An AI clock never lands on a person’s timer or timesheet, even when the person launched the AI tool.

Who the work belongs to

AI work is recorded under the person who launched the AI tool, plus the tool and model. That is how AI > Spend can show cost by person, by tool and by model.

Time is one number, cost is another

Time tells you how long the AI worked. To see what that work cost, look at the tokens and cost on the ticket. See Token and cost numbers: measured vs estimated.