StruggleTime
sign in ●

StruggleTime

count the loops that fixed the code

Time tracking for people who ship. Fixing a failing test or bug gets more credit than staring at the screen or dumping a huge AI paste you never read. Your prompts and file contents stay on your machine.

how weights feel

struggle loop · 1.00×

real fixing unread paste idle → zero

credits real fixing

Back-and-forth coding that clears an error counts. Huge unread pastes and long idle gaps do not.

privacy first

The desktop tracker is a native binary. Reviewers see timing and weights, not your code, prompts, or screenshots.

sign in

Sign in with Hack Club Slack, pick your handle, and link GitHub later if you want private repo access. No passwords.

checking your session…

Uses your Hack Club Slack profile only.

back home

dashboard

projects

modes

struggle → ship

dump vs recovery

silent & idle

timeline

editor

os

multi-project afternoons

When you hop between repos in one afternoon, hours stick to the project you were actually changing, not whichever folder was open last.

rhythm

pace

assist

languages

history check

summary card

friction timeline

Bars are short work slices. Click one to see edits, fail→pass loops, git activity, and active vs idle time. Paths and prompts stay on your machine.

pick a project with buckets

time log

Each entry links to the previous one so past edits are easy to spot. Salted file IDs only. Never paths or prompts.

projects

builders

loading…

review queue

nothing in the queue yet

fraud squad

anomaly watch

loading…

builders

loading…

trust audit

loading…

settings

Hack Club Slack is how you get in. No password login.