You are browsing as a guest. Sign up (or log in) to start making projects!

2h 47m 22s logged

Hello everyone 🤍

I hope you’re all doing great!

Just a little development update on KeyGlow.

Over the past few days I’ve been working on polishing the project instead of constantly adding new features. My goal from the very beginning has been to make KeyGlow feel like a real, reliable CLI tool rather than just another weekend prototype.

For anyone who hasn’t seen it before, KeyGlow is a privacy-first keyboard usage analyzer. It generates keyboard usage statistics and a simple heatmap while never storing what you type. No typed text, no passwords, no key sequences - only anonymous key frequency counters stored locally on your own machine.

Since the last update, quite a lot has changed:

• I added real-time keyboard monitoring.
• I implemented automatic saving while monitoring.
• Added keyboard and mouse inactivity detection with configurable timeout.
• Added the ability to disable automatic shutdown when desired.
• Improved local storage by moving everything into a dedicated ~/KeyGlow/ directory.
• Added JSON, CSV and TXT export support.
• Added an information command displaying database size, stored keys, total presses and other useful details.
• Added confirmation before deleting collected data, along with a –force / -f option for power users.
• Improved error handling for corrupted databases and invalid data.
• Added automatic creation of missing storage/export directories.
• Cleaned up dozens of small edge cases and improved the overall stability of the application.
• Wrote a complete README and documentation.
• Added a completely unnecessary but absolutely essential keyglow joke command because every CLI deserves at least a little personality.

At this point, most of my work isn’t about adding new features anymore (though it is tempting not gonna lie)-it’s about making sure the tool behaves correctly in every situation. That means testing fresh installations, handling invalid input gracefully, making the CLI feel polished, and improving the overall user experience.

The project is now very close to its first public release.

Before I publish it, there are only a few things left to finish:

  • Debug a few remaining pieces of code.
  • Update the KeyGlow ASCII logo.
  • Package everything properly.
  • Publish the project on PyPI.

Once that’s done, anyone will be able to install it with a simple:
“pip install keyglow”
I’m genuinely excited to finally share this project. It started as a small idea and slowly grew into something that feels like a proper open-source tool. There’s still plenty of room for future improvements, but I’m really happy with where it is today.

Thank you to everyone following the development so far. I can’t wait to release KeyGlow and hear what people think! 🤍

0
55

Comments 0

No comments yet. Be the first!