[probonopd]

Repository: https://github.com/acking-you/POCOX

Every device, in your pocket. Keep using Codex, Claude Code and OpenCode; POCOX sees every session on your computers, lets you pick any of them up from another device, and exposes each machine's services to all the others.

• Stars: 17
• Release with the AppImage: v0.6.0 (2026-10-20T10:57:33Z)
• AppImage asset: pocket-codex-app-v0.6.0-linux-x86_64.AppImage
• License: Apache-2.0

Found by .github/workflows/discover-apps.yml, which looks for GitHub
repositories that publish AppImages but are not in the catalog yet. This
entry was not tested by a human; please review it before merging.

[github-actions]

❌ Test failure

@acking-you: this pull request adds the AppImage from your GitHub repository to the AppImage catalog; the test reports the following. Could you have a look?

Tested:

• pocket-codex-app-v0.6.0-linux-x86_64.AppImage from release v0.6.0

Compatibility: not self-contained: uses the C library of the system; uses an old AppImage runtime that needs the C library (and libfuse2) of the system; references glibc 2.34

Names:

WARNING: AppImage name 'pocket-codex-app-v0.6.0-linux-x86_64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')
WARNING: The names of the repository, the AppImage and the README differ: repository 'POCOX', AppImage 'pocket-codex-app', README 'POCOX'

• The application needs a library that is neither in the AppImage nor on the test system ("error while loading shared libraries", the first error below names it). Please bundle this library, and what it depends on, in the AppImage: an AppImage cannot rely on libraries that are not installed on every target system.
• The application quit or crashed right after starting; the error below usually shows why. Note that the test runs the application without network access, on purpose, and that this is a requirement for the catalog: an AppImage must start without network (users are offline too). If the application needs a server, a login or an update check to start, please make it show its window (or at least a message) first and connect afterwards, and handle a failed connection instead of exiting.
• Please check the remarks about the names below.
• The repository, the AppImage and the README (whichever exist) call the application by different names (see the remarks below). Please check that they all belong to the same application, and that the name of the file in data/ is the right one.

First error in the log:

/run/firejail/appimage/usr/bin/pocket_codex: error while loading shared libraries: libwebkit2gtk-4.1.so.0: cannot open shared object file: No such file or directory

The application showed no window, but may be a system tray application (usr/bin/lib/libayatana-appindicator3.so.1: libayatana-appindicator3.so.1); running it again with a system tray
/run/firejail/appimage/usr/bin/pocket_codex: error while loading shared libraries: libwebkit2gtk-4.1.so.0: cannot open shared object file: No such file or directory
No icon appeared in the system tray either
ERROR: The application exited within 11 seconds instead of showing a window

What next: once the AppImage is fixed (e.g. in a new release), comment /retest here to test it again. If it should not be in the catalog after all, close this pull request; an app that is already in the catalog can be removed by a maintainer with /remove.

Commit dff5c03. Full log

[acking-you]

/retest

The v0.6.0 AppImage has been repackaged and replaced at its existing download URL. The fix is merged in acking-you/POCOX#141.

It now bundles WebKitGTK's dependency closure, GTK resources and Flutter's dynamically loaded GLES library, and uses a static AppImage runtime. The unused Android JNI bridge is omitted. The original application bundle/version and source artwork are retained, and the signed update manifest has been refreshed.

The actual artifact passed dependency inspection and displayed its welcome window in a clean Ubuntu 22.04 container with networking disabled and no system WebKit, Java or FUSE. Its screenshot was checked as well. Publication and validation: https://github.com/acking-you/POCOX/actions/runs/39488084516.

POCOX is the current application name; the legacy pocket-codex-app-...-linux-x86_64.AppImage filename is retained because installed updaters select that suffix. This entry points to the official upstream repository.

[github-actions]

✅ Test passed

Please check that the screenshot shows the application's main window.

POCOX

Tested:

• pocket-codex-app-v0.6.0-linux-x86_64.AppImage from release v0.6.0

Compatibility: not self-contained: uses the C library of the system; references glibc 2.35

Names:

WARNING: AppImage name 'pocket-codex-app-v0.6.0-linux-x86_64.AppImage': should not contain 'Linux', since all AppImages are for Linux (e.g. 'App-1.0-x86_64.AppImage', not 'App-1.0-linux-x86_64.AppImage')
WARNING: The names of the repository, the AppImage and the README differ: repository 'POCOX', AppImage 'pocket-codex-app', README 'POCOX'

Warnings:

• Please check the remarks about the names below.
• The repository, the AppImage and the README (whichever exist) call the application by different names (see the remarks below). Please check that they all belong to the same application, and that the name of the file in data/ is the right one.
• The AppImage contains no update information, so users cannot update it with AppImageUpdate or similar tools. Please consider embedding it when building the AppImage (e.g., appimagetool -u) and publishing the .zsync file next to the AppImage; see https://docs.appimage.org/packaging-guide/optional/updates.html

Commit dff5c03. Full log

[acking-you]

The retest has passed and the PR now has screenshot-ok; both failure labels have been cleared. I checked the screenshot: it correctly shows POCOX's first-run welcome screen.

Upstream confirmation: data/POCOX is the correct name and points to our official repository. The legacy filename is retained for existing updater compatibility. POCOX already updates through its own signed release manifest, so it does not currently use AppImageUpdate metadata. The tested Linux baseline is Ubuntu 22.04 / glibc 2.35.

@probonopd, could you please review and merge this catalog entry? The only remaining gate reported by the workflow is the maintainer review for an automatically discovered entry. Thanks for discovering POCOX and for the useful packaging checks.