Watson

Limitations

• The built-in sync command previously targeted TailorDev's hosted Crick backend, which has shut down; multi-machine synchronization now requires manual file sync, cloud storage mounts, or custom Git automation.
• Watson enforces a single-active-timer model, so engineers context-switching between concurrent tasks or background jobs cannot record overlapping frames without stopping and restarting sessions.
• Local JSON storage lacks file locking and conflict resolution, risking overwritten records if concurrent commands run or if files sync across active workstations.
• No graphic dashboard or invoice generation is included, requiring users to format terminal logs or write custom parsing scripts for non-technical stakeholders.

Who should use it

• Terminal-bound developers who want to track project hours and task tags without breaking concentration to open browser-based trackers.
• DevOps engineers who require a scriptable, local time logger that feeds clean JSON into client timesheet reports or custom billing scripts.
• Freelancers and technical contractors who prioritize data privacy and prefer storing time logs in local plain-text files under version control.

FAQ

How does Watson differ from cloud-based trackers like Toggl Track? Watson runs locally in the terminal without remote servers, subscriptions, or mandatory web accounts, storing all sessions in local JSON files. Cloud trackers like Toggl Track provide hosted dashboards, team billing controls, and client invoicing at the cost of local terminal integration.

Can Watson synchronize time frames across multiple computers? Watson has no official hosted sync service following the retirement of the Crick backend. Users synchronize records across machines by placing configuration folders in a private Git repository, symlinking files to cloud storage, or running rsync.

Where are Watson time logs stored on disk? On Linux and macOS, Watson saves frame data inside user configuration directories under ~/.config/watson/frames. Windows installations place the JSON storage file within local application data folders under AppData/Local/TailorDev/Watson.

Verdict

Watson is an ideal fit for developers who want friction-free terminal time tracking without background telemetry or monthly subscription bills, though teams requiring client-facing invoices and centralized timesheet approvals should look elsewhere. Its permissive MIT terms permit unrestricted embedding into proprietary engineering toolchains, and steady maintenance under the Jazzband collective ensures the utility remains reliable across modern Python environments.