[FEAT] Add Wakatime integration for local coding time tracking

[Priyanshu-byte-coder]

Problem Statement

GitHub commit data only captures when code is pushed, not when it's written. A developer spending 6 hours coding without committing appears idle on DevTrack. Wakatime tracks actual editor time and provides a far more accurate picture of daily coding activity.

Proposed Solution

• Add optional Wakatime API key to user Settings
• New "Coding Time" widget showing: today's hours, 7-day chart, most used language, most worked-on project
• Data source: Wakatime API /api/v1/users/current/summaries
• Store API key encrypted in Supabase users table (new column wakatime_api_key_encrypted)

Alternatives Considered

• ActivityWatch (self-hosted): More private but requires user self-hosting — too much friction
• GitHub event timestamps only: Already done, misses unreleased work

Acceptance Criteria

• Settings page: Wakatime API key input with validation (test API call on save)
• Key stored encrypted in DB
• New CodingTimeCard component showing 7-day bar chart
• New /api/metrics/coding-time route proxying Wakatime API
• Widget hidden if no Wakatime key configured

Additional Context

Wakatime has a free tier (7-day history). API docs: https://wakatime.com/developers

[mallya-m]

Hi @Priyanshu-byte-coder!

I have 5 merged PRs here (#303, #411, #586, #602, #306) and would love to take this advanced issue.

My approach:

• Add wakatime_api_key_encrypted column to users table via Supabase migration
• Store key encrypted using the existing src/lib/crypto.ts pattern already in the codebase
• Add Wakatime API key input to Settings page with validation on save
• New /api/metrics/coding-time route proxying Wakatime /api/v1/users/current/summaries
• New CodingTimeCard component with 7-day bar chart using recharts (already in the project)
• Widget hidden when no key configured

Can you assign this to me? github.com/mallya-m

[tmdeveloper007]

Proposed Implementation Plan

Here is a detailed, technically solid, step-by-step approach to solve this issue:

1. Add wakatime_api_key_encrypted column to the users schema via Supabase migrations, and add an API key input field in settings.
2. Encrypt keys using the project's crypto utility src/lib/crypto.ts before writing them to the database.
3. Add /api/metrics/coding-time dynamic route proxying Wakatime summaries, and create a beautiful CodingTimeCard card using Recharts on the dashboard, hiding it if no Wakatime credentials are configured.

I would love to work on this issue and implement the proposed solution. Could you please assign this issue to me? Thank you!

[VIDYANKSHINI]

I would like to work on this issue under GSSoC 2026.

I am interested in implementing the Wakatime integration feature to provide more accurate coding activity tracking beyond GitHub commit history. This would help users visualize real development time, language usage, and project activity directly within DevTrack.

Planned scope:

• Add Wakatime API key configuration in Settings

• Validate API key with a test API request before saving

• Store the API key securely in encrypted form

• Create a new CodingTimeCard widget showing:

  • Today’s coding hours
  • 7-day activity chart
  • Most used language
  • Most worked-on project

• Implement /api/metrics/coding-time as a proxy route for Wakatime API data

• Hide the widget when no Wakatime key is configured

• Ensure responsive UI and graceful error handling for invalid/expired keys

• Keep the implementation focused without unrelated UI or backend changes

Please assign this issue to me if it is still available.

[github-actions]

Assigned to @VIDYANKSHINI! You have 7 days to open a PR. No PR after 7 days = auto-unassigned so others can pick it up. Good luck!

[github-actions]

✅ Closed as completed!

If DevTrack has been useful, a ⭐ star on the repo helps the project grow and reach more developers.