r/flatpak

Unofficial ChatGPT/Codex Flatpak

I was looking for a ChatGPT Flatpak so I could run Codex safely alongside my local dev environment, couldn't find anyone maintaining one, so I built my own.

No OpenAI binaries are redistributed: the payload is an extra-data source, so installs fetch their .deb straight from OpenAI against a pinned sha256, for x86_64 and aarch64. Electron renderers run under zypak instead of --no-sandbox. The remote is GPG signed, and the release gate in CI does a real flatpak install from the published URL with verification on.

Updates are hands-off: a nightly job reads upstream's APT index and re-pins the manifest when a new version appears, so you get the latest even when it lands at 3am my time (I'm an Aussie, timezones are rough).

The sandbox starts sealed and you grant directories with overrides. Main known issue: the app's transparent overlay window (the desktop pet) doesn't composite on Wayland, which upstream has acknowledged as part of their Wayland support still maturing.

flatpak remote-add --user chatgpt https://rulin132.github.io/chatgpt-flatpak/chatgpt.flatpakrepo
flatpak install --user chatgpt io.github.rulin132.ChatGPT

Source: https://github.com/rulin132/chatgpt-flatpak

I'm maintaining it for my own use either way, and if OpenAI ever ships an official Flatpak I'll point people at theirs and wind this down. Bug reports and PRs welcome.

reddit.com
u/elantrix — 5 days ago
▲ 4 r/flatpak+1 crossposts

Inkscape Flatpak is very slow do things

I have about 70 apps all flatpak, inkscape is the only one I have issues with. It is slow to save a 780 mb file, switching tabs in the sidebar takes several seconds - the gui seems to freeze, and when saving this file several times a popup appears saying that inkscape is not responding.

What can I do to get better response times? Should I just use the .deb version? None of the other flatpaks have issues like this including gimp.

In case it matters:

  • Ubuntu 24.04.4 LTS
  • Wayland.
  • Intel® Core™ i7-14700 × 28
  • 32GB RAM (2 x DDR5 DIMM 5600MHz Corsair)
  • 1TB hard disc with over 400GB free (Samsung 990 PRO (NVMe PCIe 4.0))
  • AMD Radeon RX 7600 | 8GB GDDR6

I have flat seal installed but have never really used it as I don't know what all the settings do really and didn't want to make things worse.

I can use several apps at the same time, like OBS, handbrake, Kdenlive, Browser with videos playing and play games on steam all at once without any issues, but inkscape - even when the only app running - is slow to do everything. Small files don't exhibit these issues. 780MB doesn't seem that large to me.

reddit.com
u/Sketchbuch — 6 days ago

Setting Flatpak permissions manually without FlatSeal?

I was going to install FlatSeal, but my platform only offers as a FlatPak. The FlatPak needs about 3 GiB of GNOME dependencies that I just didn't want to install.

I just want LibreWolf to be able to see my YubiKey, but I can't seem to query for a guide that says something other than "use FlatSeal" -- does anyone have any advice?

[edit]

There is probably a more narrow way to do this, but this worked:

>sudo flatpak override --device=all io.gitlab.librewolf-community

reddit.com
u/cgb-001 — 8 days ago
▲ 20 r/flatpak+1 crossposts

Fix for Firefox flatpak update error "Decompressed delta part exceeds configured limit of 55726617 bytes"

reddit.com
u/ramoslala — 10 days ago

Security of the Flatpak version of Firefox.

Hello people!

I use the flatpak version of Firefox cause it gives me hardware acceleration and patented codecs inside the browser on openSUSE Tumblweeed so I don't have to mess with third party repos.

Lately I've read discussion about the security side of Flatpak browsers and how the technology "weakens the browser's own sandboxing". I kinda get the idea of how it conflicts but I am not sure how it affects security, cause the Flatpak isolates itself from the host so I can't say if it makes the browser more unsafe.

What do you think? Does it raise some concern or is it a viable option security wise? I know that it is maintained and verified by Mozilla, so it at least has to be viable.

reddit.com
u/Teemestari — 13 days ago
▲ 11 r/flatpak

flatpark — update (Jul 12 – Aug 8)

I let these slip for a few weeks, so this one covers everything since the last post rather than a single week. The catalog grew from 40 to 55 apps.

Contributed by other people

Four of this window's packages came in as pull requests from outside, and two of them from the app's own developer:

  • Zuko (⭐ 12) — Private remote shells over Iroh: no open inbound ports, no VPN, pair once and reconnect by name. Submitted and maintained by its author, @adonm, who has kept shipping the version bumps since.
  • LibreDB Studio (⭐ 135) — Open-source SQL IDE that runs entirely on your machine; PostgreSQL, MySQL, MongoDB and more. Submitted by the LibreDB project itself (@cevheri).
  • Harbor Beta (⭐ 1.3k) — Beta channel of Harbor, a desktop media client for Stremio addons. Packaged by @AdityaHebballe, who also followed up with the desktop-integration fixes.
  • Antigravity — Google's desktop command center for running local AI coding agents in parallel. Packaged by @h1zardian. Note this is the Antigravity desktop app, not the Antigravity IDE — the two split upstream and the tarball here carries no editor at all.

And the first outside contribution to the site itself: @cevheri noticed the header search was cramped on phones and sent a fix giving it its own row under 480px. Small patch, but it's the part of the site I look at least and most people see first — thank you.

Upstreams packaging their own app is exactly the loop we're after: the people who build it decide how it's sandboxed, and packaging issues route to whoever can actually fix them.

New apps

Thirteen more, most of them AI/agent desktops — enough that the site now has its own AI section:

  • goose (⭐ 52.5k) — Open-source AI agent that installs, executes, edits and tests; now stewarded by the Agentic AI Foundation.
  • Cockpit Tools (⭐ 15.4k) — Manage and switch accounts across AI coding assistants and IDEs, with plan and quota per account.
  • Claude Code Haha (⭐ 14k) — Desktop workspace running several coding agents side by side, each on its own git branch or worktree.
  • DeepChat (⭐ 6.2k) — Local-first LLM client that hosts MCP servers, runs skills and agents, and speaks ACP.
  • Lap (⭐ 1.7k) — Offline-first photo manager that reads your existing folder tree in place, built for 100k-file libraries.
  • thClaws (⭐ 1.2k) — Rust AI agent harness in one binary: GUI with terminal/chat/files tabs, plus CLI, headless and web.
  • DocKit (⭐ 1.1k) — Desktop GUI client for Elasticsearch, OpenSearch, DynamoDB and MongoDB, with natural-language queries.
  • SqlKit (⭐ 536) — Agentic SQL client for 40+ databases — PostgreSQL, MySQL, Oracle, SQLite, ClickHouse and more.
  • tldraw offline (⭐ 515) — tldraw's infinite canvas as a desktop app: no accounts, no servers, portable .tldraw files.
  • Alma (⭐ 392) — AI assistant by yetone with persistent memory, a skill system and multi-provider support.
  • ZCode — Z.ai's agentic coding desktop app for GLM models, with editor, terminals and diff review in one window. Upstream marks the Linux build beta.
  • WeMeet — Tencent Meeting, the cloud HD conferencing client.
  • THS — Hithink RoyalFlush (同花顺) A-share quotes, charting and portfolio tracking.

The site speaks Chinese now

The whole site has a Simplified Chinese locale — UI chrome, content pages, catalog sections and the sandbox-permission strings. AppStream metainfo is read per xml:lang, so translated upstream descriptions come through instead of falling back to English.

Also on the site:

  • App pages show What's New, taken from the upstream release the current pin points at, so you can see what changed before you update.
  • The homepage catalog folds behind a sticky control bar and reveals five rows at a time instead of being one endless wall.
  • A dedicated AI section, since a third of the catalog now lives there.

Packaging notes

Most of the month's bug fixes were one bug wearing different hats: Flatpak redirects the XDG directories, not $HOME itself. An app that keeps its state in ~/.something gets a tmpfs there and silently loses everything on restart. Fixed that way for dbx (~/.dbx, ~/.duckdb), TriliumNext (the note database) and AB Download Manager (~/.abdm, which also unblocked its tray).

The mirror image: cc-switch had a single-file --filesystem grant for a config the tool rewrites atomically — renaming onto a bind mount is EBUSY, so the write fails. Those per-tool grants are gone; the app page documents the flatpak override commands instead, for anyone who wants them.

WeMeet needed its own trick: screen sharing only works under XWayland, so the package forces it there rather than shipping a session that silently shares a black rectangle.

Developer-approved

14 apps now carry the blue shield — upstream explicitly authorized the flatpark listing. New this window: Zuko and LibreDB Studio, both approved by construction since their developers submitted them.

Infrastructure

  • The daily pin robot now unpacks the payload before pinning it and holds back anything that fails to unpack, instead of publishing a build that only breaks on the user's machine.
  • verify builds against a temporary local remote and cleans up afterwards, so a failed verification can't leave junk in your flatpak config.
  • Push-mode updates (upstream release webhook → dispatch → PR) have been running in production the whole window; the daily cron is now the fallback path.

Auto-updates

The pin pipeline ran every day of the window, refreshing extra-data pins across Markra, dbx, Alma, Orca, ZenNotes, Tine, Claude Desktop, electerm, LibreDB Studio, Folia, Longbridge Pro, Aptakube, SqlKit and others.

As always: https://flatpark.org — issues and PRs welcome, especially "this app has no Linux packaging and should" suggestions.# flatpark — update (Jul 12 – Aug 8)

I let these slip for a few weeks, so this one covers everything since the last post rather than a single week. The catalog grew from 40 to 55 apps.

u/jing2uo — 14 days ago

Is there anything someone should know or check before using the Flatpak version of Steam?

So, I'm in the process of making a new Linux gaming PC for myself, but I want to double-check myself before getting too far into my project, and I want to make sure I install and configure the Flatpak version of Steam correctly.

I have used the Flatpak version of Steam in the past on my old PC. When I first set up Flatpak Steam, it was kind of finicky with directory permissions. I had to go into Flatseal and change some of Steam's directory permissions so it would work the way I wanted it to.

I got it working, and it worked fine, but Steam Flatpak and my Steam games were all on the same drive,

and I think my games also shared Steam's sandbox.

My old Linux gaming machine had a 500 GB SSD and a 750 GB HDD. I figured 500 GB would be enough for all my games, and the HDD would be for everything else that didn't benefit from being on an SSD.

Unfortunately for me, I assumed incorrectly, and 500 GB wasn't going to be nearly enough space for all my games.

My current plan for my new PC is to use the 500 GB SSD as mostly a boot drive, and I have a 2 TB SSD that I want to use to store all my games.

However, if Steam Flatpak is installed on one drive, but I try installing my games on a different drive, could that cause any issues?

Does Flatpak Steam need to be on the same drive as my Steam games, or can they be separate?

Thank you.

reddit.com
u/ClocomotionCommotion — 12 days ago