ttime for VS Code — Your coding hours, captured automatically.

Time tracking is a chore. When it's done late (or not at all), billable hours get lost.

This extension tracks your coding activity in the background — automatic sessions, git context, historical stats, and a full in-editor review panel. Everything works locally, no account required.

If you connect a ttime account, your activity syncs to the ttime app where you can turn it into clean time records and track your revenue. But that's entirely optional.

Website: https://gettti.me App: https://gettti.me/app

Preview

What you get

• Automatic coding sessions: tracks your active editing time across files and groups it into sessions.
• Git context (optional): associates recent commits (hash/branch/message/stats) with sessions.
• Status bar indicator: quickly see whether you’re connected/authenticated.
• In-editor review: open the ttime panel to browse sessions day by day — navigate backwards through your history with prev/next controls.
• Historical statistics: a stats panel shows active days (GitHub-style heatmap), top projects, and language breakdown across all recorded history.
• Export & import: back up your local session data to a JSON file and restore it at any time — useful when switching machines or reinstalling VS Code.

Getting started

1. Install ttime from the VS Code Marketplace.
2. Open the Command Palette and run Open ttime.
3. Click Login (or run Login to ttime).
4. Complete the sign-in flow in your browser, then return to VS Code.

Tip: the ttime icon in the status bar reflects connection/auth state. Click it to open the panel.

Commands

• Open ttime (ttime-vscode.openApp): opens the ttime panel.
• Login to ttime (ttime-vscode.login): starts the browser-based login flow.

Requirements

• VS Code 1.109.0 or later
• A ttime account (sign-in happens via https://gettti.me)

Privacy & data collection

This extension is built to capture activity metadata, not code contents.

Stored locally (on your machine)

• A local file based database of captured sessions is stored in VS Code’s global extension storage
• Your auth token is stored and synced.

Uploaded to ttime (when authenticated)

When you’re signed in, the extension periodically uploads session summaries to https://gettti.me. Session payloads include:

• Workspace/project name (as shown by VS Code)
• File names + language IDs + per-file active time totals
• Session time ranges (local timestamps) and derived active seconds
• Git context (if available)

Not collected

• File contents, diffs, or selections
• Keystrokes

Network requests

• Online connectivity check: https://1.1.1.1/cdn-cgi/trace
• ttime backend health/settings/events: https://gettti.me/api/integrations/*
• Browser sign-in: https://gettti.me/api/integrations/authorize

If you want to stop all tracking, disable the extension in VS Code. The “Connected” toggle in the ttime panel stops backend checks/uploads; the extension may still record sessions locally while disconnected.

Troubleshooting

• Status bar shows “not authenticated”: run Login to ttime and finish the browser flow.
• “backend issues” / “disconnected”: open the ttime panel → Settings (top-right) → toggle “Connected” off/on to retry.
• Need logs: open View → Output and select ttime.

Known limitations

• The in-editor session list currently shows recent sessions (last ~24h).

Support

contact@gettti.me