Classic confinement request: ai-control-center

Hi! I’d like to request classic confinement for the snap “ai-control-center”.

AI Control Center is a desktop panel to manage and update local AI tools on Ubuntu (Ollama, Open WebUI, ComfyUI, LM Studio, Jan, SillyTavern, n8n and others, plus user-defined ones).

It needs classic confinement because it:

  • starts/stops and enables/disables systemd system and user units (e.g. ollama.service, ~/.config/systemd/user/*.service),
  • runs the host docker CLI to start/stop containers and change their restart policy,
  • reads and removes AI tool folders anywhere in the user’s home when the user asks to uninstall them,
  • updates those tools with the host’s own tools when the user clicks Update (docker pull / docker compose, git pull + pip/npm in the tool’s folder, flatpak update, the official Ollama installer via pkexec),
  • starts desktop AI apps (AppImage, Flatpak, .deb) and writes XDG autostart entries.

There are no snapd interfaces that cover managing arbitrary systemd units or the host Docker daemon, so strict confinement isn’t possible.

Source: GitHub - cesarbarbozarueda/ai-control-center-ubuntu: AI Control Center para Ubuntu: detectá, iniciá, actualizá y desinstalá tus IAs locales (Ollama, ComfyUI, Open WebUI, LM Studio y más). GPL-3.0. ♥ Apoyá el proyecto con una donación por Binance Pay desde el botón Donar. · GitHub Website: https://www.devcibr.com License: GPL-3.0-or-later

Thanks!

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

Not a store reviewer, however, note that classic confinement is only granted for apps in supported categories:

I would suggest avoid investing effort on it unless you sure your application fit in one of the supported categories or you’re fine with NOT distributing your snap via the Snap Store but via alternative channels(e.g. GitHub releases).

Hi folks!

As @Lin-Buo-Ren pointed out, snaps need to fit under one of the supported categories for classic confinement to be considered. In this case, I believe the technical reasons falls more on the explicitly unsupported set.

Additionally, 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 ai-control-center 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

Because of all the previous reasons, I do not think ai-control-center should get classic confinement.

Thanks for your understanding.