Classic confinement request for yazses

[mskazemi]

To make the review of this request easier, I am using the requested template.

• name: yazses

• description: YazSes is a local-first Linux voice dictation tool. It records audio from the user’s microphone, performs local/offline speech transcription, and inserts the transcribed text into the currently focused desktop application. The goal is to provide system-wide voice typing for Linux desktops.

• snapcraft: snap/snapcraft.yaml in the upstream repository.

• upstream: GitHub - novafabric/yazses · GitHub

• upstream-relation: I am the upstream author and snap publisher.

• supported-category: Productivity / accessibility / desktop automation / developer tools

• reasoning: YazSes needs classic confinement because its core function is system-wide voice typing. The application must interact with the user’s active desktop session and insert transcribed text into arbitrary focused applications, not only into resources inside the snap sandbox.

  The snap needs capabilities such as:

  1. Recording audio from the user’s microphone for local dictation.
  2. Running local Python/Whisper-style transcription dependencies.
  3. Keyboard/input integration for dictation workflows.
  4. Typing or pasting the transcribed text into whichever desktop application currently has focus.
  5. Desktop automation behavior similar to voice typing, keyboard macro, and accessibility tools.

  Strict confinement is generally preferred, and I understand that. However, strict confinement does not appear sufficient for the main product behavior: system-wide text insertion into arbitrary Linux desktop applications. A strictly confined version would only be a limited demo and would not provide the actual dictation workflow expected by users.

  I have considered existing interfaces such as audio-related interfaces for microphone access, but the remaining requirement is global desktop/input integration and text insertion into arbitrary focused applications.

  YazSes is user-launched and intended for desktop productivity. It is not a background system service. Its core workflow is local/offline transcription and desktop text insertion.

I understand that strict confinement is generally preferred over classic.

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

Additional revision details:

• Snap name: yazses
• Version: 0.3.0
• Revision: 1
• Build URL: https://github.com/novafabric/yazses/actions/runs/25993233222
• Current status: Manual review pending

[ogra]

@mskazemi

• supported-category: Productivity / accessibility / desktop automation / developer tools

This is not a supported category only categories listed in the supported set from the page below are permitted to get classic confinement granted and fitting into one of them is a hard requirement to even have your request processed any further:

Process for reviewing classic confinement snaps

Classic confinement review process Background As of snapd 2.20, snappy supports confinement: classic which allows the snap to run without restrictions. Future releases of snapd will also support a classic interface (name TBD) that operates similarly. Snaps specifying classic confinement may target the stable channel, but are only supported on classic distro systems (ie, not on Ubuntu Core). Because classic confinement snaps run without restrictions, use of classic confinement effectively grant…

I highly doubt your tool fits into one of these categories though, what were the issues you ran into with the existing interfaces, the above use-cases you describe should all be covered by certain interfaces (audio-record for microphone use, the desktop/desktop-legacy interfaces for (automated) copy/pasting and any further interaction with GUI apps, etc etc) did the snappy-debug tool give you any suggestions when running it against your running strict snap ?