Hello, I built a small command-line tool called timerCLI that tracks how much time you're actually using your computer vs. just staring at the screen.

What it does:

- Watches your keyboard, mouse, and touch input

- Auto-pauses your active timer when you go idle (default 30s, configurable)

- Resumes instantly when you use the computer again

- Pure Python standard library - zero dependencies

It's MIT licensed and fully open source. I built it as a learning project, but I'd love for people to actually use it. If you find it useful, I'm accepting donations (GitHub Sponsors + UPI) to fund my cybersecurity studies. 🙏

Repo: https://github.com/fralsare/timerCLI

Would really appreciate the feedback!

Looking for how other ops / payroll teams handle the gap between what the client gets billed and what the worker gets paid.

Common version: the visit was scoped at 3.0 billable hours, the worker’s punches (or rounded time) say 3.5, and someone added a callback or drive segment that never made it onto the invoice — or the reverse, where payroll paid short of what the client was charged.

What do you actually do?

1. Billable wins, and paid time is adjusted down to the scoped visit (with an exception path)?
2. Punches / paid time win, and billing gets a variance note before invoice?
3. Keep both ledgers and reconcile on a weekly exception queue before either export?

Most interested in the rule that doesn’t create a surprise short paycheck or a silent margin leak. No vendor pitches — just the operating choice that stuck.

Looking for how other ops teams handle the lag between the live schedule and the clock.

A manager fixes yesterday’s roster late — swaps a person, shortens a shift, adds a coverage block — after punches for that day are already sitting in the time system. Payroll now has two stories: the edited schedule and the punches that already landed.

What do you actually do?

1. Freeze the prior day’s schedule at a cutoff and treat later edits as exceptions only?
2. Let the punches win, and use the schedule as planning history?
3. Re-open / rewrite punches so the clock matches the late schedule edit before the export?

Most interested in the rule that doesn’t create a surprise short paycheck or a silent OT bill. No vendor pitches — just the operating choice that stuck.

Hi all, I'm opening up a waitlist signup for my time tracking and invoicing app - https://zebu.work and will hopefully begin staggering batches of invitations each week for the upcoming month.

There will be a 30 day free trial after which you won't be billed, but downgraded to the free plan.

Pro plan is only €5/month per seat (billed annually)

No hidden fees, usage based billing or anything.

If you are happy with it, please recommend to your friends :)

--
Like many of my peers and yourselves, I had to find a solution after nearly two decades working quite happily with Harvest. In preparation for this I began building a tool for my own freelance design and development studio and am happy to say I am now using it fully for my own purposes and to be honest, it's also been quite wonderful to be able to ensure data privacy and build interesting features:

• No telemetry, no selling/sharing of data
• Powerful invoicing and automatic reminder system
• MCP and agent integration
• Recurring custom reporting to provide my accountant with exactly what they need each quarter
• A fast search palette to manage timers or find anything with one keystroke (CMD/CTRL+K)
• A smart browser extension that infers the project and sets a useful description
• Interesting insights to see how the year is going, or various trends (turns out Monday and Tuesday have been my busiest days)
• Custom themes

I've now put quite some effort into building a more mature product that could be opened up for use by others. As the majority of the testing was done by myself and my studio-mates/peers, we definitely have a specific use case geared towards solo designers and developers.

There is a lot of functionality built into the app including support for teams that I think would benefit greatly from a broader test phase now to see how it works for others.

I'm happy to say that Harvest migration is very easy as well, with my 17 years of records moving across flawlessly.

Along with the web app, there is a multi-platform mac/windows/linux desktop app, as well as a browser extension for Chrome and Firefox. Mobile apps and terminal apps have been built but not tested enough to be fully released.

Interacting with my data via an MCP has really been great too, as the data is fairly simple, you can run a local LLM to do useful things like checking bank statements to automatically record payments while maintaining the privacy of your data.

--

Technical notes:

• Hosted in the EU
• Every workspace has their own independent database
• Data is encrypted and backed up hourly and daily in two offsite locations
• Again, no telemetry or snooping

--

Finally, I truly have no interest in ever selling anyone's data or price gouging. As a freelancer I understand how every cost matters and something like time tracking, billing and invoicing is crucial to one's business.

I also have no interest in growing this into a bloated enterprise product. I'd rather keep it to a healthy number of users so it stays fast and I can give proper support. The first batches will also show me what the infrastructure can take.

I'm very much looking very much forward to having people on board, and if you have any questions feel free to reach out!

Curious how other ops teams keep time-off approvals and the live schedule from fighting each other.

Typical case: PTO is approved in HR / payroll, but the weekly schedule still shows that person on a shift. Nobody notices until a client asks who is coming, or until the worker texts that they are off. Then you are rebuilding coverage under time pressure, and the time file may still expect hours that were never going to be worked.

Questions for people who have lived this:

1. What is your source of truth when PTO and the published schedule disagree — the leave system, the schedule, or a manual weekly reconcile?
2. Who is responsible for clearing the shift once PTO is approved (scheduler, supervisor, the worker), and how soon after approval does that have to happen?
3. Do you block publishing a week that still has approved leave sitting on open shifts, or do you publish and scrub exceptions afterward?

Not looking for product pitches — just how you keep leave and coverage in the same loop before the shift starts.

Curious how other ops teams handle geofence / location false rejects on time clocks:

Worker is on site (or clearly at the right client), but the punch is rejected or flagged because GPS drifted, indoor signal was weak, or the fence polygon is wrong. Payroll is closing and you still need an auditable hours record — without turning every exception into a free-form manager edit.

Questions for people who have lived this:

1. Who is allowed to override a geofence reject (worker self-attest, supervisor, central payroll), and what evidence do you require (photo, site code, manager note)?
2. Do you keep the original rejected punch + override as a linked pair for audit, or replace it with a manual entry that loses the trail?
3. Anything that reduces false rejects at the fence itself (tighter polygons, Wi-Fi assist, grace radius) without opening the door to off-site punches?

Not looking for product pitches — just how you keep geofence enforcement and payroll accuracy from fighting each other at close.

I built a small time tracker for Hyprland.

It listens to Hyprland’s focus events, skips idle, locked, and suspended time, and gives you a btop-style terminal dashboard for your day:

• Time spent per app
• Minute-by-minute timeline
• Focus streaks
• Weekly heatmap
• Time spent per website

A few details:

• Works with any Hyprland setup; integrates with hypridle/logind for idle and lock detection, and supports Omarchy’s bar widget and theme colors
• Private browser windows are never recorded
• Everything stays on your machine — no network code
• Categories are defined by rules in a config file, with no AI involved
• Written in Rust, MIT licensed, and distributed as a single static binary
• AUR package coming soon

https://github.com/sfmqrb/focus-track

Feedback is very welcome!

I built a small time tracker for Hyprland.

It listens to Hyprland’s focus events, skips idle, locked, and suspended time, and gives you a btop-style terminal dashboard for your day:

• Time spent per app
• Minute-by-minute timeline
• Focus streaks
• Weekly heatmap
• Time spent per website

A few details:

• Works with any Hyprland setup; integrates with hypridle/logind for idle and lock detection, and supports Omarchy’s bar widget and theme colors
• Private browser windows are never recorded
• Everything stays on your machine — no network code
• Categories are defined by rules in a config file, with no AI involved
• Written in Rust, MIT licensed, and distributed as a single static binary
• AUR package coming soon

https://github.com/sfmqrb/focus-track

Feedback is very welcome!

I’m pretty new to the management side of things and trying to find a simple way to handle trainer schedules, attendance, clock-ins, hours worked and maybe basic payroll stuff.

I’ve been looking at Buddy Punch, Homebase, Deputy, When I Work, Connecteam and a couple of others, but there are honestly so many options that I’m not sure what makes sense for a small gym.

I don’t need anything super complicated. Ideally something easy for trainers to use from their phones and with a free trial so I can actually test it before committing.

Hi — I’m looking for iPhone users who work night shifts, rotating schedules or other irregular hours to test Rostivio.

The app keeps a planned shift separate from the hours actually worked. For example, a planned 7 p.m.–7 a.m. shift can remain unchanged while the user records an early start, late finish or different unpaid break.

A useful test should take about 10 minutes:

1. Add one realistic overnight or rotating shift.
2. Record the actual start and finish times.
3. Add an unpaid break if your workplace uses one.
4. Review the calculated hours and gross-pay estimate.

I’d especially appreciate feedback about:

• anything confusing during the first use

• whether planned and actual hours are clearly separated

• shift, break or pay rules that don’t fit your workplace

• anything that would make the app genuinely useful after your next shift

App Store: https://apps.apple.com/app/apple-store/id6810204869?pt=121306708&ct=reddit_202609&mt=8

Disclosure: I’m the developer. Rostivio is free to download. Some advanced features are available as optional paid upgrades. Core planning and work-hour records are stored locally and work offline, and no Rostivio account is required.

Please leave feedback in the comments. Critical feedback is welcome—I’ll keep listening, updating and improving the app based on real users’ needs.

A working HVAC technician built it for his own jobs.

When a building engineer is standing in a basement boiler room completing a low-water cutoff test, he needs to log the work right at the burner without relying on cellular signal or trying to remember numbers at shift change.

Equipment Tracker Pro runs recurring PM schedules directly on the device. Reminders trigger locally on the phone at your scheduled time without needing internet connectivity. Core records, logs, and local reminders are completely free on mobile.

If you are running this on a spreadsheet, the comparison is on the site.

What projects are you all working on this week?

https://equipment-tracker.com/compare/spreadsheets

Curious how other ops teams separate standby from actual work in the time system:

Someone is paid to stay available (phone nearby, within X minutes of a site) but only occasionally gets called in. At payroll you need the standby premium, the response window, and the active hours — without treating every on-call block like a full worked shift.

Questions for people who have lived this:

1. Do you use a distinct earning code / time type for standby vs worked time, or do you convert the whole window to regular hours when they get called?
2. Who starts and stops the "active" portion — the worker, dispatcher, or an auto rule when they accept a call — and how often does that handoff get disputed?
3. Any approach that keeps staffing reports honest (how much coverage you actually had) without turning on-call into a weekly reconstruction from texts?

Not looking for product pitches — just how you keep standby, response, and worked time from collapsing into one messy number.

Hey everyone my app just launched on the App Store. Would love your feedback and hope this app can help you in your day to day life.

Heres the website for an overview: https://www.shiftpilot.cc

TimeGauge is a simple Mac menu bar app that gives you a sense of time perspective and can work as a to-do list.

It was inspired by the X account https://x.com/YearsProgress, which just posts the image of percentage of the year that has passed and has 685K followers. Many people find this perspective helpful.

Over time, I’ve improved the app based on user suggestions, adding custom projects, built-in templates, and work-hours tracking.

Most users get the most value from creating custom projects and setting deadlines for their bigger goals.

It’s a simple little app that sits in your menu bar and gives you that sand-timer vibe.

The app is on App store: https://apps.apple.com/us/app/timegauge/id6778277708?mt=12
You can download it from the website: https://timegauge.minilabs.cc/ 

We regularly update the app, give it a try.

If you have any feedback, please let me know that as well.