Timesheet Telemetry

How It Works

Every time you run cc switch, CC logs the event with a timestamp. From these logs, it computes how long you spent on each project.

No manual input. No timers to start and stop. Just switch projects naturally and CC tracks it.

Viewing Today's Log

cc time

  Today — Thursday, Mar 26

  09:12 → 10:45   [1h 33m]   acme / acme_memberships2
  10:45 → 12:00   [1h 15m]   globex / globex_v18
  12:00 → 14:30   [2h 30m]   acme / acme_approvals       ⚑
  14:30 → now     [1h 12m]   initech / initech_trips

  Total: 6h 30m

The ⚑ flag marks sessions where you were on a project for longer than your configured threshold (default: 60 minutes). This is a nudge — it doesn't mean the time is wrong, just that you may want to review it before submitting a timesheet.

Punching Out

When you stop coding for the day (or take a long break), punch out so CC doesn't count idle time:

cc time --stop

This creates a stop entry. The last project's session ends at the punch-out time.

Specific Date

cc time -d 2026-03-25

Clearing Flags

Once you've reviewed flagged sessions:

cc time --clear-flags

Configuration

Setting	Default	Description
timesheet_flag_threshold	60	Minutes before a session is flagged
timesheet_flag_prompt	true	Prompt to review when a flagged session is detected on switch

Configure via cc config.

The Flag Prompt

If timesheet_flag_prompt is enabled, switching away from a project after a long session shows a quick inline summary and asks if you want to continue:

  ⏱  2h 30m on acme / acme_approvals  [flagged]

  Today so far:
    09:12 → 10:45  [1h 33m]  acme / acme_memberships2
    10:45 → now    [2h 30m]  acme / acme_approvals  ⚑

Continue switching? [Y/n]