For Remote Teams

Consistent time tracking across every timezone.

ClockMe auto-tracks AI coding sessions regardless of where your team works. No manual timer discipline required. Free for individuals, Pro team plan coming soon.

Start tracking freeView integrations

The problem with time tracking for remote teams

✗

Manual tracking fails across timezones

A developer in Lisbon starts their day before your standup. They forget to start the timer — again. By the time anyone notices, two weeks of hours are missing and the sprint report is wrong.

✗

No visibility into who is working on what

Your team is spread across four timezones. You have no real-time view of which projects are getting hours, which clients are close to budget, and whether the sprint is on track.

✗

Inconsistent tracking leads to billing disputes

One developer tracks every 15 minutes meticulously. Another rounds to the nearest hour at end of day. The client sees wildly different granularity and starts asking questions.

How ClockMe solves it

Built for the way remote teams actually work.

Unique

Auto-start via AI tool hooks

The Claude Code SessionStart hook fires the moment a session opens — no manual timer action needed. For remote teams, this means consistent tracking regardless of whether team members remember to start the clock.

Project-level dashboard

See total hours per project at a glance. Budget burn, daily breakdown, and team totals all in one view. Timezone doesn't matter — ClockMe stores everything in UTC.

Budget alerts prevent scope creep

Set hour budgets per project. ClockMe notifies you at 25/50/75/100% — whether that notification fires at 9am in New York or 2pm in Berlin. Clients get flagged before the overrun, not after.

Works with every AI coding tool

Claude Code, Cursor, Windsurf, GitHub Copilot, and Gemini CLI all support the same MCP endpoint. Your remote team can use different tools and still land in the same ClockMe account.

Works with your AI tools

One API key. One MCP endpoint. Every AI coding tool you already use.

Claude CodeHook-based auto-start — consistent across every team memberSetup guide →CursorComposer MCP — timer control from the editorSetup guide →WindsurfCascade MCP — works over any networkSetup guide →GitHub CopilotVS Code 1.102+ agent modeSetup guide →Gemini CLISSH-compatible — tracks time on remote dev machinesSetup guide →

All integrations use the same API key. Manage everything from one dashboard. Use the Setup Wizard →

Questions from remote teams

Does ClockMe handle multiple timezones correctly?

Yes. ClockMe stores all timestamps in UTC and converts to each user's local timezone on display. There is no timezone configuration required — entries are always accurate regardless of where the user is.

What happens if a developer forgets to stop their timer at end of day?

ClockMe's idle detection detects inactivity and prompts the user when they return. The user can keep all time, discard the idle period, or stop the timer at a specific time. This prevents runaway entries caused by overnight forgetting.

Can managers see the team's time in real time?

Shared team workspaces with manager visibility are part of ClockMe Pro, coming soon. Currently, each developer has their own individual account. The Pro plan will support project-level visibility across all team members.

Is there a way to enforce tracking standards across the team?

The most effective enforcement is the MCP hook — when every developer adds the SessionStart hook to their Claude Code config, tracking happens automatically. No policy enforcement needed.

Ready to stop losing hours?

Free for individuals. Takes 5 minutes to connect your first AI tool.

Start tracking free