KomhandClaude Opus 5
4c6b40954b
NoteGen is a Tauri/WebKitGTK notebook that separates capturing from organizing: records (text, voice, screenshots, images, links, files) go in as they happen, and a model of your choice turns a selection of them into a structured Markdown note you keep editing. Not on Flathub under any id, and upstream ships an official amd64 .deb, so it repackages cleanly as extra-data. The app id is upstream's own Tauri identifier from tauri.conf.json rather than one invented here. Two things needed care in the sandbox. The clipboard plugin the app builds on opens an X11 display while it initialises and exits with DisplayParsingError(DisplayNotSet) when there is none, so the package grants --socket=x11 rather than fallback-x11, which withholds X11 whenever Wayland is present; the window stays Wayland-native. And the .deb's payload is a binary plus a Tauri resource tree at usr/lib/NoteGen that the app resolves relative to its own executable, so apply_extra stages the whole usr tree and links a stable launcher name into /app/extra/bin - the launcher name itself is read out of the package's .desktop Exec= so a rename upstream cannot ship an uninstallable pin, and the link's name keeps matching StartupWMClass. Beyond network, audio and the tray, nothing is granted: the workspace, database, images and attachments live under ~/.var/app/com.codexu.NoteGen, and a workspace elsewhere is an opt-in flatpak override documented in the metainfo. Co-authored-by: Claude Opus 5 <[email protected]>
Yet another Flatpak hub
FlatPark is a Flatpak hub for apps that ship as a definitive download, built to be driven by AI agents.
Goals
- AI-driven by design. Onboarding, review, publishing, upgrading, and cleanup are all meant to be driven by AI agents. Leaning on agents to do this work efficiently is a primary goal, not an afterthought.
- One runtime version, always the latest. Every app targets the current major of its runtime — never one app on GNOME 49 and another on 50. Old majors are dead weight on your disk, so the whole catalog moves forward together.
- extra-data only, no build hosting. FlatPark hosts only extra-data apps: it downloads official releases and repackages them — it never builds the app from source. (Supporting libraries the runtime lacks may be built from pinned source; the app itself is always the vendor's own binary.) That keeps installing and updating the apps you need in one place, while Flatpak keeps them sandboxed and out of your home directory.
- Open to vibe-coded apps, with guardrails. Apps built with AI ("vibe coding") are welcome, under clear rules enforced by AI review that weighs development history and app quality — and with an explicit de-listing process.
Install
flatpak --user remote-add --if-not-exists flatpark https://dl.flatpark.org/flatpark.flatpakrepo
flatpak --user install flatpark <app-id>
--user installs into your home (no admin); drop it from both commands for a
system-wide install. Browse the catalog at https://flatpark.org.
Add an app
Onboarding is meant to run through an AI agent. Open this repo in your agent (e.g. Claude Code) and prompt it:
I want to publish <app or upstream URL> to FlatPark. Read
CONTRIBUTING.mdand the existing PRs, then write and validate the manifest underregistry/<app-id>/.
It writes the flatpark.yml descriptor and Flatpak manifest, validates and
test-builds them, and opens a PR. If it can't get there from the rules and the
existing PRs, open an issue — letting an agent submit, test, and PR end-to-end
is the goal.
License
FlatPark's own code is MIT. It does not license the packaged applications themselves — those remain their vendors' property and are fetched from official sources at install time.