Skip to main content
  1. Posts/

Keelhaven Releases New Version—This Time, Updates Come from Real User Feedback

·557 words·3 mins· ·
Table of Contents
My Open Source Projects - This article is part of a series.
Part 5: This Article

On August 31st, I released Keelhaven; on September 3rd, I introduced it in the previous post.

Keelhaven

After that article was published, I started receiving feedback from real users: some sent emails, some opened GitHub Issue directly, some reposted on X, some gave a Star, and some even donated.

Thank you very much!!!

Some of these feedbacks were features I came up with myself while sitting at my computer, while others were usage scenarios I hadn’t considered at all before. For example:

  • One user provided feedback on five issues in a single Issue, including both bugs and features;
  • Another user, who migrated from command-line restic, listed all the parameters they were using and asked if they could be used in Keelhaven.

In the newly released 0.8.0, many of these feedbacks have been implemented. I won’t go into specific details here; if you’re interested, you can directly install the latest version using the commands below.

brew install --cask shenxianpeng/tap/keelhaven
# or
curl -fsSL https://keelhaven.app/install.sh | bash

Real User Feedback is the Most Valuable
#

When I first released it, I thought I had tested it thoroughly, and that the App was already quite easy to use. However, just a few days after its release, I started receiving user feedback.

Interestingly, most of the feedback wasn’t about bugs, but rather feature requests, and many of these requests were things I hadn’t thought of myself.

This made me realize even more: any tool, whether for developers or general users, only reveals its true usage scenarios once it actually starts being used. Many things are difficult to fully envision by simply thinking about them alone at a computer; only by putting the tool into users’ hands and listening to their voices can one truly know what it still lacks.

So, I’d like to specially thank every user who took the time to write feedback.

I’ve seen all your feedback and am seriously considering it. Many have already been implemented, and the rest are still under consideration and design.


If you use a Mac and are looking for a backup tool
#

Keelhaven is worth ten minutes of your time to try: select the folders you want to back up, the destination, and the backup frequency, then you can essentially forget about it.

It will back up on schedule in the background, periodically check the repository automatically, and only notify you when there’s an issue.

Encryption is done locally, there’s no account system; backups use the standard restic format, which can be restored at any time or migrated to other tools. It’s open source, free, and available on macOS 14 or above. Its specific workings are described in more detail in the previous post.

Official website: https://keelhaven.app Source code: https://github.com/shenxianpeng/keelhaven

After trying it out, whether you find it useful or run into problems, you’re welcome to let me know: you can send an email to support@keelhaven.app, or open a GitHub Issue; you can also leave a message on WeChat official account, Zhihu, or X. Especially if you post content related to Keelhaven on X, you can @ me, and I will also update relevant comments on its official website.

If you find it useful, please give it a Star and feel free to share it with friends who might need it.

Thank you to everyone who tried it, offered suggestions, or even donated.

Xianpeng Shen
Author
Xianpeng Shen
Engineer. Builder. Maintainer.
My Open Source Projects - This article is part of a series.
Part 5: This Article

Related

How to backup Jenkins

·214 words·2 mins
This article explains how to backup Jenkins using the ThinBackup plugin and shell scripts, ensuring that your Jenkins configuration and build data are safely stored.

Open Delivery Spec update: AI code shouldn't just pass the gate — it should leave evidence

·1560 words·8 mins
Three weeks ago I introduced Open Delivery Spec (ODS), my side project for governing AI-assisted code in CI. Since then the CLI has shipped 5 releases and grown two new pillars: deterministic merge-confidence signals that answer “is this AI PR safe to merge?”, and an auto-generated, standards-based evidence document on every PR. As always, this post sticks to what actually ships — no hype.

Open Delivery Spec—I Built a CI Quality Gate for AI-Generated Code

·1018 words·5 mins
Over the past few months, I’ve been working on an open-source organization called Open Delivery Spec (ODS) in my spare time. The initiative stemmed from the increasing volume of AI-generated code and the lack of reliable governance mechanisms within teams. This article records the thought process, progress, and boundaries based on the project’s real-world status, without any exaggeration.