Klokrs — Tab Time Tracker for Engineers

Know exactly where your time goes

Chrome Extensions

Productivity

Task Management

Analytics

YouTube

What inspired me to build Klokrs It started with a stupid problem that nobody talks about. Every single day at 6 PM, I'd close my laptop and have no idea what I actually did that day. I'd feel exhausted. I'd feel like I shipped something. But when I tried to actually tell someone what I built, I couldn't. I'd say "I worked on the dashboard" but how many hours? I don't know. I'd spent time on meetings, Slack, code reviews, actual coding. But there was this black hole in the middle of the day where 3 hours just... disappeared. So I did what every engineer does. I started logging my time manually. I'd set timers. I'd write things down. I'd use time tracking apps that required me to hit a button every time I switched tasks. It lasted a week. Maybe two. The friction was too high. Every timer I forgot to start was a gap in the data. Every interruption made me lose track of whether the timer was running. And at the end of the day, I had numbers, but they felt fake because I'd manipulated them so much trying to remember what I was doing. The problem is bigger than me Then I asked the DevWeekends community (20,000+ engineers trying to get better at their craft) a simple question: "How many of you want to know exactly where your work time goes?" The response was overwhelming. Almost everyone raised their hand. But here's what was interesting: When I asked them what they were doing about it, nobody had a good answer. Some were using time trackers. Some had given up. Most were just... guessing. Living with the discomfort of not knowing. And I realized something. This isn't about laziness. This isn't about poor discipline. It's about the fact that the tools that exist require you to do extra work. They ask you to change your behavior. They ask you to be perfect at remembering to log things. That's not how humans work. Every engineer I talked to had the same confession: "I think I code for 6 hours a day, but I have no idea if that's true." How my approach evolved I started thinking differently about the problem. What if I didn't ask engineers to log their time at all? What if the computer just... watched? Not invasively. Not creepily. Just: "Which tab are you on right now?" The browser already knows. Your operating system already knows. I'm not collecting anything new. I'm just being honest about what's already happening. So I built a silent extension. Install it once. Forget about it. Go about your day exactly like you normally would. It runs in the background. It sees which tab is active. It logs how long you spend there. When you walk away, it notices you're idle and stops the timer automatically (no false numbers). That's it. No manual logging. No behavior change required. No friction. What I learned building this The hardest part wasn't the code. It was deciding what problem I was actually solving. Was I building a productivity app to make you work harder? (No, that's not it.) Was I building something to monitor you? (Hell no.) Was I building another tool in a crowded productivity space? (Not what I wanted.) What I was actually doing: I was building a mirror. A way to see the truth about where your time actually goes, without judgment. And that reframing changed everything about how I designed it. Because once you see the truth, you don't need me to tell you what to do about it. You'll figure it out. You might realize you waste 2 hours on Twitter. Or you might realize you spend more time in Slack than in actual coding. Or you might discover that your "deep work" block is actually 6 interruptions separated by 15 minutes of actual focus. The data does the talking. Why I'm sharing this I'm not building Klokrs to get rich. (It's free. I'm giving away the core product forever.) I'm not building it to prove something. (I already had a job.) I'm building it because I know the feeling of finishing a day and having no idea where it went. And I know that feeling compounds. Day after day of not knowing becomes weeks of not knowing becomes a year where you can't answer "what did I actually accomplish?" That's a painful way to live. Twenty thousand engineers in our community told me they feel that same pain. So I solved it for myself. Then I built it so everyone else could solve it too.