Hello Fedora Community!
I wanted to share a project I’ve been developing to solve a specific workflow challenge in modern immutable/atomic Linux distributions (developed and heavily tested on Fedora Kinoite, Silverblue, and the COSMIC desktop spin).
It’s called Claw Launcher — a high-performance WebApp execution engine built in Rust using Tauri 2.0.
The Problem & The Motivation
On atomic desktops, we heavily rely on Flatpaks or Distrobox containers to keep the underlying host system completely clean and immutable. However, when it comes to web-heavy workflows (running multiple isolated instances of VS Code Web, specific AI dashboards, cloud storage frontends, or messaging clients), spinning up full Chromium/Electron instances or managing dozens of browser profiles can quickly drain RAM and compromise strict data isolation.
Claw Launcher bridges this gap by acting as a single, shared, ultra-lightweight compiled native binary (~12MB) that spawns dedicated, sandboxed Wayland WebViews dynamically via CLI parameters.
Key Engineering Features
Strict Runtime Profile Isolation: Each instance (e.g., VSCode Web, Gemini, OneDrive) gets its own isolated sandbox for cookies, localStorage, and cache under ~/.local/share/{APP_ID}/. Sessions and data are never shared between instances or other system users.
Resource Optimization: Features aggressive WebKit Memory Pressure management to explicitly prevent RAM leaks common in long-running standalone Electron apps.
Native Wayland Integration: Built with pure Wayland in mind (optimized for KDE Plasma and COSMIC). It ensures perfect window grouping on your taskbar by properly binding the application via StartupWMClass and prgname inside dynamically generated .desktop files.
State & Geometry Persistence: Dynamically monitors and serializes window sizing and coordinates, so every custom app restores exactly where you left it.
Atomic & Idempotent Design: Fully compatible with rpm-ostree environments. It operates without requiring any local HTML overhead, Python runtime dependencies on the host, or invasive system modifications.
Architecture & How It Works
Instead of compiling a new binary for every web application, the engine is completely data-driven. A single global binary handles execution via strict CLI argument parsing (using clap):
Bash
claw-launcher --app-id Claw_Gemini --url https://gemini.google.com --name Gemini
This single command triggers a native Wayland WebView wrapper and structures the isolated directory tree on the fly. The generated .desktop file integration looks completely native:
Ini, TOML
[Desktop Entry]
Name=Gemini
Comment=Gemini - Dashboard IA
Exec=claw-launcher --app-id Claw_Gemini --url https://gemini.google.com --name Gemini %U
Icon=Claw_Gemini
Terminal=false
Type=Application
StartupWMClass=Claw_Gemini
Categories=Network;
Compiling and Testing on Fedora
If you are running a Silverblue/Kinoite setup with your layering development packages ready (webkit2gtk4.1-devel, openssl-devel, etc.), you can compile it natively using standard Rust toolchains:
Bash
cd claw-launcher/src-tauri
cargo build --release
The resulting binary can even be safely copied to /usr/local/bin/ to be shared among different users on the same immutable system, as data profiles remain strictly tied to each user’s ~/ home directory.
Looking for Feedback!
I would love to hear thoughts, architectural suggestions, or feedback from fellow atomic desktop users!
How do you currently handle heavy web-app isolation on Silverblue/Kinoite?
Would an automated Flatpak-packaged generator for this architecture be something the community prefers over host-compiled binaries?
Check out the project source structure and details here: GitHub - RafaelBatistaDev/Claw_Launcher_Linux_App_Rust: Claw Launcher é um motor de execução de WebApps de alto desempenho, desenvolvido em Rust com Tauri 2.0. Ele foi projetado especificamente para sistemas Linux modernos (como Fedora Kinoite/Silverblue) · GitHub