It has been maintained for years, and it supports every Kobo AFAIK.
It's called NickelMenu, and it's great. I'm in the Kobo ecosystem because of NickelMenu and Plato.
One note if you're thinking about getting a kobo due its relative openness: consider getting a two-core device. I did not do my homework and got a Clara BW because I don't want the color display. Later I found out that color is the only one with the two-core CPU.
I created this as I could not find anything existing that gives the capabilities I wanted. I read several things downloaded over web apart from books on my Mac and phone, which I would prefer to do on an eInk display. Search papers on arxiv and read them offline later, Substack, even spending a lot of time on chess puzzles, monitor my Claude/Codex remotely, generate explainer audiobooks and listen to them on my bluetooth speaker etc.
The longer battery and the display makes some use cases really shine and I wanted to create apps for my own Kobo and potentially helpful for others as well.
Nickelmenu deserves a mention in the opening paragraph and a differentiation of what this new piece of software brings to the table.
NickelMenu is a mature project and perfect at what it does, we just have different goals. NickelMenu is designed to extend Kobo's stock interface. Cobalt is designed to be an app platform like Android has for example. I wanted app creators to just write their app logic and not build things like a UI toolkit for their apps, app lifecycle and rendering support (framebuffer drawing, partial eInk refreshes, touch input handling etc.), bluetooth handling, sensor and more. Anything launched through NickelMenu like KOReader or Plato have to implement these on their own.
AFAIK NickelMenu command actions spawn arbitrary shell cmds that inherit root from Nickel, we avoid it by running apps as separate unprivileged processes with declared capabilities like network, storage, audio, fronlight etc.
I also wanted to provide ability to quickly build apps with the SDK and our simulator to test apps on before putting it on the real device, an app store to get new apps over the WiFi after the initial USB install.
This was more oriented on making my life easier, say I have an app idea that I want on my Kobo tomorrow and how quickly can I bring it live on the device. The 'you can run apps' I wrote was meant to signify anyone can now create apps using the SDK without bothering about the device specific bits and publish them and install it via Cobalt's app store. I hope this clarifies things.
It runs Android. It's a Chinese company and comes with a bunch of pre-installed apps, but I just blocked its abilities to phone home and use Koreader. It's been great for me
https://goodereader.com/blog/product/onyx-boox-go-7-bw "The Onyx Boox Go 7 is a dedicated e-book reader with a black and white e-paper display. This device has the same specifications and software as the Go 7 Color Gen 2, except that this model doesn’t have a Kaleido 3; instead, it uses the latest generation Carta 1300 e-paper panel, which increases responsiveness. The key selling points of this model are the physical page-turn buttons and Google Android 13, as well as full access to the Play Store. For those of you who want an e-reader that doesn’t lock you into a specific ecosystem, this deserves a look."
(slower by 2 minutes...)
When reading, agree on it being more than sufficient.
My recommendation is partially because the price can be identical when they have a sale. That was the case when I got a BW--it was the same price as the color.
I should also mention I run quite a few things on my kobo: boringtun to connect to my home network, a fetcher to sync my books and feeds, Plato and its article fetcher whenever I update my Wallabag articles. I'm beyond pleased with my reader experience. The extra processing power would just be icing on the cake.
I got the BW over the Color only because I had read the color screen wasn't as sharp, though I've never compared them side by side.
I recommend enabling ssh (native kobo feature) so it's easier to modify the config without needing to plug in, though obviously this is optional.
If you connect over SSH, I would recommend not touching system files. The new kobos don't have a removable SD card so if you corrupt the system files and it can't boot, you need to either do some PCB surgery or get a new mainboard.
What's tricky is that although I don't want it to be an unconstrained app platform, I do want the ability to integrate with services that host my things to read. Karakeep, RSS, Google Play Books or Internet Archive, etc.. but I think that could be handled in a more narrow fashion.
On many occasions I have compiled notes, sometimes manually created sometimes LLM curated, and put them into a .epub file to send to my kindle so I can read as I am out walking.
It would be cool to skip a few steps there, and have "live" documents at the ready, particularly in markdown if possible, without having to sync/publish etc
Thanks for the clarification Claude
Edit: damn, just saw the BW note. It looks like the Clara Colour would be blocked by Cobalt...
Me personally, I just want a reliable toaster.
The street finds its own use for things is the excitement that we don't know what is possible, and that we ought be free to try. The amazing suite of software here sure looks like self evident proof about how exciting it is when we can go further, to me. I love the LLM prompt sidekick; super neat as an ambient display.
It's really sad how HN is so vocally anti-hacker, is so conservative, shows up so regularly to declare alliance to anti-possibility, to anti-features. For some people, they don't only fail to be interested, they are expressly anti interested, the only thing they want is for everyone else to have to live as constrained and unexplorarive and unthoughtful as they are. I don't get it. Conservatism is a wicked disease, imo.
Ended up being more involved than the benefit it would bring, especially considering that these media server programs know how to interface with the traditional remote over HDMI (if you have the right graphics card or a dongle) and show the selection UI on screen like a smart TV.
Anyway, my response is "you don't necessarily have to complicate your e-reader, instead you have the option of making it not an e-reader."
Years ago, it was practically a hobby of mine to go to my local Goodwill, and find an extremely cheap old used Kobo and find someone to donate it to. Now I'm thinking of getting old Kobos just for the eink display so I can run simple apps on it - while continuing to use my regular Kobo as an ereader.
I can simulate it by staying on the "Library" tab, but it tends to forget halfway frequently.
It is not because you can install and run apps that you have to.
HN Search: enshittification - https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
Everyone already has at least one multitool, the smartphone. Most also have a tablet and/or a laptop. While this project looks like a cool hack, I don't see much practical use for another multitool with a weak CPU, laggy screen, and poor input.
If your software is mostly written by the slop machine, fine. I don't have to be upset about it unless I think about contributing and then notice the uncanny nature of the source code. But a website and a README is directly user facing and it is a major disservice, and in my opinion, lack of respect, to generate your website copy with an LLM.
"These are photographs of the device, not simulator captures" is the kind of total throwaway verbiage that a human would never even pause to consider writing because it "clarifies" something that in the totality of context is beyond obvious. It makes the writing more fatiguing to read, and creates a terrible first impression for a project.
much prefer ai assisted development than someone who does it by hand, prone to errors and lacking in features.
You prefer AI-assisted development with errors and lacking features rather than something done by hand with errors and lacking features?
https://github.com/Podginator/KoboOmnivoreConverter
It took a lot of messing around trying to figure out how nickel fit together. This is much more … impressive.
I mean I got a laptop, e ink laptop would be cool but this certainly isn't it and who needs a book with Claude code agent? You either read or you do what exactly with that linux pc on a book hardcover? Just grab your laptop like a normal civilized person
It's not that vibe coding is bad on its own, but it makes me worried about project's future (ease come, easy go).
Store-only by design: installing it proves delivery of an app the USB package never contained.
> Tested on one device: the Kobo Clara BW (N365, device code 391), firmware 4.45.23697. Every device write is gated on an exact match of framebuffer identity, geometry, device code, serial model prefix, firmware version and kernel release, so a different reader is refused rather than guessed at.
I can't stop reading "gated" on LLM output lately.
Anyways, I wish this worked on my Libra :<
> Charge a Kobo Clara BW (N365) and connect it over USB. Other models are refused, not guessed at.