- name: sessionsifu
- description: SessionSifu saves and restores user desktop sessions. It records running applications, user-selected/open documents and observable window state, then can relaunch those applications and rebuild supported window layouts. The optional Privacy Recall feature is disabled by default and stores encrypted screenshots/OCR locally.
- snapcraft: SessionSifu/snap/snapcraft.yaml at main · tpluharik/SessionSifu · GitHub
- upstream: GitHub - tpluharik/SessionSifu: SessionSifu · GitHub
- upstream-relation: I am the upstream author/maintainer and the snap publisher.
- supported-category: agent/assistant that runs arbitrary user-directed code and needs to reach files and programs that aren’t known at build time.
- reasoning: SessionSifu’s core restore operation intentionally starts the exact host applications and opens the exact local documents selected by the user when the session was saved. Those application IDs, executable paths, desktop files, argument vectors and document paths are not known when the snap is built.
Strict interfaces such as desktop, desktop-legacy, wayland, x11, home, removable-media and desktop-launch were evaluated. They can expose the UI and selected files, but they cannot provide the complete core workflow:
- Session capture enumerates the user’s existing host processes/windows and reads bounded process metadata such as
/proc/<pid>/cmdlineand eligible/proc/<pid>/fdtargets to associate documents with applications. - Restore resolves host desktop entries/executables and launches arbitrary user-directed host applications with validated argument vectors.
desktop-launch/portals choose a handler for a URI but cannot restore the exact saved application and launch arguments. - Window-layout restoration must communicate with the current user session/window manager and, where available, host tools such as
wmctrlorkdotool. The required applications, files and compositor capabilities vary at runtime and cannot be declared as a fixed interface set.
Removing these operations would reduce the snap to a different product that cannot save and restore sessions. The snap therefore fits the supported agent/assistant category: it runs user-directed programs and reaches user-directed files that are unknown at build time.
This snap is the portable KDE Plasma/general GNOME edition only. It does not ship or install the GNOME Shell extension; the full Ubuntu 26.04/GNOME Shell 50 integration is distributed separately through the project’s PPA.
SessionSifu runs only as the logged-in user. It has no root helper, privileged daemon or sudo/pkexec integration. Session and Recall data remain local, Recall is off by default, and launch arguments are passed as bounded vectors rather than through a shell. The project documents its security and privacy boundaries at SessionSifu/SECURITY.md at main · tpluharik/SessionSifu · GitHub and SessionSifu/docs/PRIVACY.md at main · tpluharik/SessionSifu · GitHub .
I understand that strict confinement is generally preferred over classic. Classic is requested because the exact user-directed host application/process/session access above is the primary purpose of SessionSifu, not merely because strict packaging is inconvenient.