Wanted to try Wispr Flow but they don't have a linux distro yet. I already run aaddrick/claude-desktop-debian (not just debian...), so I ran the same playbook here to create an auto-updating release pipeline.
I've only tested on Nobara (Fedora) KDE. Mind testing on your various setups?
If you run into issues on other backends/compositors/etc, feel free to file an issue, PR, or just drop a note here.
Yeah, I don't want want to take away from anyone. The COSMIC team is doing amazing and hard work. I started dev on claude-desktop-debian with Pop!OS COSMIC as my daily. We're just in a weird spot for that particular issue right now. In 3 years, it'll be something else. That's the nature of fragmentation.
While GNOME tray lovers and haters both exist, only one of those two groups is liable to submit an issue against my repo looking for help getting icons working correctly.
A lot of that is keyboard shortcuts for push-to-talk. Easy right?
X11 is mostly fine, but the world is moving into Wayland. Wayland doesn't have shortcuts native and relies on xdg-desktop-portal, which in turn relies on each backend to implement it's own version.
COSMIC from the Pop!OS team's xdg-desktop-cosmic doesn't support GlobalShortcuts yet (might now, haven't checked in a bit). So XWayland for them.
Tray icons? GNOME doesn't have a tray out of the box, but there's an extension. There's no standard for whether it's light mode or dark mode across distros and when you map out the options, no api's indicate whether the tray is light or dark while in light/dark mode. At some point you have to just accept it's not always perfect or patch in an override.
Debian is in the name, but scope has grown to all backends, compositors, etc.
The main reason must companies don't publish Linux electron apps is fragmentation. If you're doing anything more than rendering a webpage as an app, it starts to get complicated. I've got a bank of VM's setup for testing, and I still need it up.
That's me, and that sounds weird. Mind giving stone more details so I can help get to the source of it? Or just submit an issue on the repo. Should just be one main electron process.
Wrote this after seeing the news about the matplotlib debacle. Figured a decent solution to AI submitted PR's was to prompt inject them with your project's standards.
----
AI-assisted PRs are landing in maintainers’ queues with the wrong CSS framework and no tests. Sometimes with no disclosure that AI generated the code at all. The contributor often isn’t cutting corners. Their AI tool just had no project context when it generated the code.
There are two files that fix this. CLAUDE.md is read automatically by Claude Code when a contributor opens the project. AGENTS.md is a vendor-neutral standard, already supported by over twenty tools, that does the same thing across all of them. Both work the same way: when a contributor clones your repo and opens it in their AI tool, these files are loaded into the tool’s context before a single line is generated.
I'll be happy the day there's an official distribution and I can put the repo to rest