Classic confinement request for prettymux

store-requests classic-confinement
1

name: prettymux

description: PrettyMux is a native GTK4/libadwaita terminal workspace for Linux, built with libghostty. It provides split panes, workspaces, vertical tabs, notifications, automation, and an optional embedded browser for multitask developer workflows.

snapcraft: prettymux/snap/snapcraft.yaml at main · patcito/prettymux · GitHub

upstream: GitHub - patcito/prettymux · GitHub

upstream-relation: I am the upstream developer and publisher.

supported-category: terminal-emulator

reasoning: PrettyMux embeds a real terminal and is designed to run the user’s normal shell and development tools directly on the host system. It needs broad access to user project directories, shell configuration, arbitrary user commands, host browser/open behavior, and host networking state for features like port detection. Strict confinement would break core terminal workspace functionality, and the existing interfaces are not sufficient.

  • I understand that strict confinement is generally preferred over classic.

  • I’ve tried the existing interfaces to make the snap work under strict confinement.

1 Like
2

This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.

3

This request has been added to the queue for review by the @reviewers team.

4

Hello @patcito!

Even though your snap does fall under the supported categories for classic, the project seems to be very fresh, according to the upstream repository and I could not find evidences that the project has a strong enough user base currently. Thus it is currently not a good candidate for classic confinement (#reject).

If you need further assistance, feel free to share your questions :slight_smile: