Classic confinement request for gritcode

store-requests classic-confinement
1
  • name: gritcode
  • description: Native desktop AI coding assistant built with C++20 and wxWidgets. Streaming markdown rendering, multi-session history with SQLite full-text search, and a one-click Play button that builds and runs projects without an AI roundtrip. Supports DeepSeek V4.
  • snapcraft: gritcode/snap/snapcraft.yaml at main · lszl84/gritcode · GitHub
  • upstream: GitHub - lszl84/gritcode: Native desktop AI coding assistant. wxWidgets + C++20. No Electron. · GitHub
  • upstream-relation: I am the author and sole maintainer of the project.
  • supported-category: IDEs and developer tools — the same category as VS Code (code), Vim (nvim), Emacs (emacs), and Helix (helix), all of which are classic-confined snaps.
  • reasoning: gritcode’s core function is to execute arbitrary user shell commands via its bash tool, read/write/edit any file on the filesystem, spawn build systems and dev servers, access the OS keyring for API key storage, and communicate over the network to multiple LLM providers. Every tool the AI uses (bash, read_file, write_file, edit_file, web_fetch, list_directory) directly accesses host resources that strict confinement would block. The app IS a general-purpose developer tool — sandboxing it defeats its entire purpose. This is the same fundamental constraint that led to classic grants for VS Code (integrated terminal), Vim/Emacs (arbitrary file access, shell commands), and Helix (LSP integration requiring system access).

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

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

2

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

3

Hi @lukedevmindscape

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 gritcode 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 gritcode should not get classic confinement as of now.

4

Thanks for your reply.

Unfortunately, this means I won’t be able to publish the app to the Snap Store as classic confinement is pretty much required for this kind of project.

I will go ahead and build the user base distributing raw deb packages, but that does not look as professional as store distribution.

Will bump this thread once I get more users.

Thanks,

Luke