Overview
StruggleTime tracks productive struggle: the loops where something breaks, you dig in, and it works again. Steady back-and-forth coding and fixing errors get more credit than large instant code drops you never ran, or long stretches away from the keyboard.
What gets credit
| Pattern | Weight (v0.4.0-alpha) |
|---|---|
| Struggle / fail→fix→pass | 1.00x |
| AI write + dwell + follow-up | 0.85x |
| Human edits, never run | 0.70x |
| Unverified multi-file dump | 0.20x |
| Quiet follow-up after real work | 0.70 → 0 over ~5–12 minutes |
| Idle after the active span | Gradual decay (no hard 240s cliff) |
How trust works
- Passive file & git tracking: the desktop tracker watches saved file changes and git activity in your project folder. It does not screenshot your screen or read file contents.
- Scrambled file IDs: paths are mixed with a secret salt (
sha256(salt:path)) before anything is sent, so raw paths and source never leave your machine. - Tamper-evident history: each sealed time slice stores
prev_hashof the previous entry. Quiet edits to past history are easy to spot in review. - Shared scoring rules: daemon and server both use
st-corewith the sameFORMULA_VERSION.
Privacy
struggletime daemon is a native binary. Wire payloads are allowlisted metadata (~25–50 KB) with scrambled file IDs. See Privacy.
Pages
Installation
Clone, install tracker, link a project
Getting started
Clone, check, run server + daemon
CLI and tray
struggletime and the menu bar
Daemon
1s loop, editor labels, adapters, silent decay
Integrations
Every editor/agent adapter, hooks, GitHub, Slack
Privacy
What leaves your machine—and what never does
Web app
Dashboard, builders, roles
API
Batch ingest, chain, review
Troubleshooting
Daemon, sync, and fetch fixes