KomhandClaude Opus 5
0a77b1cb23
OpenPencil is a design editor that reads and writes native Figma .fig files as well as its own .pen documents. The catalog has no vector/UI design tool at all - Impasto is raster painting and tldraw offline is a whiteboard - and upstream is not on Flathub. Packaged as extra-data from the official amd64 .deb on org.gnome.Platform//50, the same Tauri/WebKitGTK shape as NoteGen: the whole usr tree is staged under /app/extra, the launcher name is read out of the package's own .desktop Exec= so an upstream rename cannot ship an app that will not start, and the wrapper only sets WEBKIT_DISABLE_DMABUF_RENDERER. The app id follows openpencil.dev, the project's own domain, rather than the maintainer's personal domain that the Tauri bundle identifier uses. Sandbox: network for the AI providers and the WebRTC collaboration sessions, the Secret Service for provider API keys, dri for canvas rendering, and no filesystem grant - documents go through the file-chooser portal. X11 is granted alongside Wayland rather than as fallback-x11, because the clipboard that copies nodes between apps falls back to X11 whenever the compositor does not offer Wayland data-control to a sandboxed client, and fallback-x11 withholds the socket in exactly that case. 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.