Skip to content

docs: document local ActivityWatch time-tracking setup - #24

Open
kubantjan wants to merge 1 commit into
masterfrom
update-clockify-skill
Open

docs: document local ActivityWatch time-tracking setup#24
kubantjan wants to merge 1 commit into
masterfrom
update-clockify-skill

Conversation

@kubantjan

Copy link
Copy Markdown
Member

Adds TIME_TRACKING.md documenting the local ActivityWatch setup used to reconstruct daily activity (apps, URLs, code files, idle time) into Clockify entries — complementing the calendar-based clockify-day skill.

Covers:

  • Why ActivityWatch over screenshots/ManicTime (GDPR + cost)
  • Architecture & data sources (window / afk / vscode / web watchers)
  • Install, start/stop/confirm, local dashboard
  • Retention purge (aw-purge.py + daily LaunchAgent, 30-day default)
  • Day-reconstruction flow for Clockify
  • Rosetta 2 end-of-life caveat (Intel-only build; fine until ~macOS 28)
  • Uninstall steps

Also links the doc from README.md.

🤖 Generated with Claude Code

Add TIME_TRACKING.md describing the local ActivityWatch setup used to
reconstruct daily activity (apps, URLs, code files, idle) into Clockify
entries, complementing the calendar-based clockify-day skill. Covers
architecture, install, start/stop, retention purge, the day-reconstruction
flow, and the Rosetta 2 end-of-life caveat. Link it from the README.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant