No company behind it
No investors, no sales team, no growth targets. Just a tool I rely on every working day.
About
A passion project, built by one developer.
Hi, I'm Brajan. Cat Tracker isn't a company or a startup. It's a side project I build in my own time to fix an annoyance from my day job — and to find out how far I can push AI-assisted software development with a model running on my own machine.
— Brajan, builder of Cat Tracker
The itch
Logging time shouldn't take time.
At work I log my hours against Jira tickets. Every day meant hunting for the ticket key, switching tabs, starting a timer, forgetting to stop it, and patching up the gaps on Friday. None of it is hard. All of it is friction.
So I built the tool I wanted: press ⌘K, type a few letters of a ticket, hit ↵, and get back to work.
Before
- Open Jira
- Find ticket
- Copy key
- Open Clockify
- Pick project
- Start timer
With Cat Tracker
- ⌘K
- type
- ↵
- Timer running.
The experiment
How far can a local model go?
Cat Tracker is also my playground for learning AI software development. The code is written by Qwen, an open-weight model running locally on my own hardware, and I try to push it as far as it will go on a real, working app — auth, encryption, third-party integrations, teams and exports included.
Every feature idea or bug fix goes through the same loop: Claude turns it into a plan using my own Overseer skill, Qwen implements that plan, Claude reviews the result, and then I review and test it myself before it ships. Some changes land on the first pass; some take a few rounds.
~/cat-tracker · dev loop
1. Idea
A feature idea or a bug fix
2. Plan
Claude + my Overseer skill write the plan
3. Build
Qwen implements the plan, locally
4. AI review
Claude reviews the diff
5. Human review
I review and test it by hand
6. Ship
Merge, deploy, use it the next morning
repeat until it purrs
What that means for you
Small, honest, and used every day.
Expect rough edges
It's built in spare time with AI doing most of the typing, so bugs happen. I fix them as I run into them.
Your keys stay yours
API keys are encrypted with your PIN and kept on your device by default. How security works →
Shaped by real use
Features get built when a real need shows up at work, not to fill a roadmap.
- 1
- developer
- 1
- local model (Qwen)
- 100+
- commits so far
- 2026
- started in July
Built with
- Qwen (local)
- Claude (planning & review)
- Nuxt 4
- Vue 3
- TypeScript
- Tailwind CSS
- Pinia
- Firebase
- anime.js
- Web Crypto (AES-GCM)
- Jira Cloud API
- Clockify API
Built for my own timesheets. Free for yours.
If logging time bugs you as much as it bugged me, give it a try.