Classic confinement request: tuxagent

store-requests classic-confinement
1

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.

  • name: tuxagent

    description: AI desktop assistant for Linux that helps users with system tasks via natural language. Features screenshot analysis, 50+ system tools, and shell command execution.

    snapcraft: tux-agent/snap/snapcraft.yaml at main · sebastianaldrin/tux-agent · GitHub

    upstream: GitHub - sebastianaldrin/tux-agent: Linux desktop AI assistant - Ask questions, attach screenshots, get help with your system

    upstream-relation: I am the author and maintainer

    supported-category: system-utility

    reasoning: TuxAgent is an AI assistant that helps Linux users by executing shell commands and file operations on their behalf. It requires:

    1. Arbitrary filesystem access - Users ask “read my config file at ~/.bashrc” or “save this to ~/Documents/notes.txt”
    2. Shell command execution - Users ask “install Chrome” or “check disk usage” which requires running arbitrary commands
    3. D-Bus session access - The GTK4 overlay communicates with a background daemon via D-Bus
    4. Process management - Listing and managing running processes

    These cannot be achieved with strict confinement because:

    • home interface doesn’t cover dotfiles or system paths users may reference
    • process-control doesn’t allow arbitrary process inspection
    • No interface allows arbitrary command execution which is the core feature

I understand that strict confinement is generally preferred over classic.

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

2

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

3

Hey @sebastianaldrin

Please note that classic confinement is a sensitive matter and it is reserved for mature, well-known applications published by mature, well-known entities. As of today, I believe that tuxagent doesn’t meet this criteria because of the following reasons:

  • The project seems to be very fresh, according to the upstream repository

  • The projects seems to have little/none community around according to upstream repository (contributors, issues, PRs, etc.)

  • I could not find evidences that the project has a strong enough user base currently

Considering all these factors, I think tuxagent should not get classic confinement as of now.

Thanks

4

Please note that there is no such category on:

It is a hard requirement that your application fits into one of the pre-defined supported categories listed there, else classic confinement will not be granted …