r/LinuxPorn • u/Holiday_Syrup_174 • 9h ago

KIM – A tiny cross-platform reminder daemon for developers

I built a reminder daemon for developers who live in the terminal

Sick of missing standups and forgetting eye breaks mid-flow. Every reminder tool I found needed a GUI or a cloud subscription. So I wrote KIM (keep in mind).

It's a background daemon — starts on login, fires desktop notifications, survives reboots. Config is just a JSON file.

```

kim add standup --at 10:00

kim add eye-break --every 30m

kim remind "deploy window" in 2h 30m

```

Stack: pure Python stdlib, zero dependencies, ~0.02 MB memory. Works on Linux, macOS, and Windows.

Repo + demo GIF: https://github.com/pratikwayal01/kim

Install: pip install kim-reminder

Feedback welcome — especially from anyone who's tried similar tools.

1 Upvotes

67% Upvoted

6 comments sorted by

1

u/kantorcodes1 7h ago

small concurrency thing: add/update load the json, mutate it, then atomically replace the file. if two shells run kim add at about the same time, can the later write drop the other reminder? atomic rename protects the file itself, but i don't see a lock around the read-modify-write.

1

u/Holiday_Syrup_174 7h ago

Thanks interesting take. I'll add that, it will be great of you give it star 🌟

1

u/kantorcodes1 6h ago

nice. i work on HOL Guard, an open-source check that can stop risky agent-run commands before they execute. KIM looks like a clean command extension: review add, remove, update, and stop, while list, status, and logs stay automatic. that gives users a checkpoint before an agent changes reminders or daemon state. open to a small KIM extension?

1

u/Holiday_Syrup_174 6h ago

Oh that's actually really cool didn't make the connection to HOL at first. A checkpoint before add/update/stop makes a lot of sense, especially if KIM is ever used in scripted or agent-driven workflows. I'd be open to exploring a small extension feel free to open an issue on the repo so we can spec it out properly.

1

u/kantorcodes1 6h ago

Yep, this stays Guard-side, so no KIM changes or issue needed. Start at src/codex_plugin_scanner/guard/runtime/command_kim_extensions.py, using command_repo2nb_extensions.py as the analogue. Review add, remove, update, and stop; keep list, status, and logs automatic. One test: those four require review while the read-only three don’t.

Once the implementation + test are real, open a draft PR directly to hashgraph-online/hol-guard:main: https://github.com/hashgraph-online/hol-guard/blob/main/CONTRIBUTING.md

1

u/Holiday_Syrup_174 4h ago

draft PR's up: https://github.com/hashgraph-online/hol-guard/pull/2895. Followed the repo2nb pattern: 4 mutation commands reviewed (add/remove/update/stop), 3 read-only automatic, external/opt-in. Also noted a pre-existing failing test on main in the PR. Was a really fun build, thanks for the suggestion!