← Back to Blog

Your hours, already counted: a timesheet and standup from your coding activity

November 9, 2026 · 4 min read

It's Friday afternoon and the timesheet is due. Which tickets did you touch on Tuesday? How long did that incident really take? You piece it together from your calendar, your branch names and a vague memory, then round everything to the nearest hour and hope.

You already left the evidence behind. Ticket IDs are in your branch names, your commit messages and the prompts you gave your coding agents, and every one of those has a timestamp. L2Cache's Worklog turns that into a list of what you worked on and an approximate weekly timesheet, built entirely on your Mac.

Step 1: L2Cache learns your ticket format

There's no built-in list of ticket systems. Teams use ABC-123, INC0012345, #1234, CR_2024_118 and plenty more. So L2Cache looks through your own branch names, commits and agent sessions for IDs that keep coming back, and shows you the formats it found.

You choose which to track, and nothing is tracked until you confirm. If nothing recurring turns up yet, paste one of your ticket IDs and it works out the pattern. Formats that appear later are suggested, never added silently. Until you set up formats, time is grouped by project.

Step 2: every ticket and branch you worked on

Each ticket gets its own entry: the projects, branches, agent sessions and commits that mention it, and roughly how much time went into it.

Not every piece of work has a ticket. A feature branch without one becomes a work item of its own. If its commits mention a ticket, L2Cache offers Link to …?; otherwise Assign to Ticket… lets you attach it yourself. Long-lived branches such as main, or any branch active for more than 30 days, count as time on the project rather than a work item.

Step 3: an approximate timesheet

The Timesheet tab shows hours per ticket per day for the week. The hours come from activity L2Cache already has: commits and branch switches, agent sessions, and terminal commands.

How the hours are estimated

• Each piece of activity counts for the time until the next one.
• A gap of more than 15 minutes counts as idle, so a long lunch doesn't become billable. The activity before the gap gets 5 minutes.
• A terminal command with no branch of its own goes to the branch of the nearest activity in the same project.
• Totals are rounded to the nearest quarter hour.

These are estimates, and the timesheet says so: cells read Estimated from your activity. Thinking, reading docs and meetings leave no trace on your Mac, so treat the numbers as a strong first draft rather than a stopwatch.

Correcting it

• Click a cell to change the hours. Your number is marked Corrected by you and kept separately, so recalculating never overwrites it.
• Click a day to see what happened that day, so you can check a number before you trust it.
• Add Row for time that left no trace: a meeting, a support call.
• When a week ends, its hours are saved, so they don't drift as older history is cleared. Recalculate rebuilds them if you want.

Getting it into your timesheet tool

Copy as Table pastes straight into a spreadsheet, Copy as Text gives you plain lines, and Export CSV… saves a file for tools that import one. Copy Weekly Recap gives you a short summary of the week.

Standups that write themselves

The same activity answers "what did you do yesterday?". L2Cache's Today page has a standup in the Yesterday / Today / Blockers shape, built from your sessions and Git history and ready to paste. It works with AI turned off. With AI on, your chosen provider rewrites it, and may only use the facts it's given, so it can't invent work. Each project also has Copy project standup for the last two days of commits and what's still open.

The Weekly Brief button on Today opens a short summary of your week, built from the same facts: written by your AI provider when AI is on, or from a template when it's off. For something you can edit and share, the weekly recap lists the week's milestones. Keep or drop items, reword them, mask project names if you're sharing outside the team, and copy it for Slack or as Markdown.

Your Day: what your agents actually did

Commits only cover what you committed. The Your Day card on Today fills the gap with what your coding agents did, grouped by feature. With L2Cache's hooks connected, Claude Code and Codex end each turn that edited files with a one-line summary: the feature, what changed, the next step. L2Cache checks each summary against the file changes it recorded, so an agent's claim is never shown as fact. Edits that haven't been pushed are marked not pushed. Work no agent summarised still appears, as Unsummarised activity built from the raw edits.

Work summaries come from Claude Code and Codex today. Sessions from other agents still count towards the timesheet and the project timeline.

All local

Worklog uses only what's already on your Mac: your Git repositories, your coding-agent sessions, your terminal history and your clips. It doesn't connect to Jira, ServiceNow or anything else, and nothing is sent anywhere. Worklog is part of Developer Pro, which the free trial includes.

For the project side of the same history, commits, sessions and test runs on one timeline, see Project Story. For a feel of how it fits into a working day, see a day in the life of a Mac developer.

The short version

• L2Cache learns your ticket ID format from your own branches, commits and agent sessions, and tracks nothing until you confirm.
• Hours are estimated from activity, with gaps over 15 minutes treated as idle, and rounded to a quarter hour.
• Correct any cell, add rows for meetings, then copy as a table, as text or as CSV.
• The standup, weekly recap and Your Day card come from the same local activity.