Running Claude Desktop and Cowork on Fedora Linux

A technical guide to running Anthropic's Debian-packaged Claude Desktop client on Fedora Linux, covering cryptographic verification, non-root installation, and KVM virtualisation for Cowork.

TL;DR

  • Upstream Packaging Barrier: Anthropic provides the Linux beta of Claude Desktop exclusively as a Debian/Ubuntu .deb package.
  • Non-Root Extraction: The community utility claude-desktop-rpm installs the official .deb archive directly into unprivileged user-space (~/.local) without modifying the host system RPM database or redistributing binaries.
  • Cryptographic Verification: Every installation and update verifies Anthropic’s APT repository using pinned GPG public key fingerprints, InRelease signature checking, expiration verification, and double SHA256 checksum validation.
  • Claude Cowork Prerequisites: Local virtualisation for Cowork requires system-level packages installed via DNF (qemu-system-x86-core, edk2-ovmf, virtiofsd), loading the vhost_vsock kernel module, and adding the user to the kvm group.
  • Automated Updates & Profiles: Daily background updates are managed via a systemd user timer without system APT tooling, and multiple accounts can be segregated using Chromium --user-data-dir profile launchers.

Anthropic’s official release of the Claude Desktop Linux beta marks a significant expansion of desktop AI workflows to Linux platforms. However, the initial beta deployment targets Debian and Ubuntu distributions exclusively through standard .deb packages. Operating systems built on Red Hat technology—such as Fedora Workstation—are not natively supported by Anthropic’s distribution channels. For systems engineers and software developers who rely on Fedora Workstation, running the desktop client historically required manual binary extraction, unsafe system-level conversion tools, or containerised workarounds that break desktop environment integration.

Deploying claude desktop fedora linux environments cleanly requires an approach that preserves the integrity of Fedora’s package manager while adhering to standard security isolation practices. Forcing Debian packages into the system RPM database via utilities like alien damages system integrity and risks package collisions. Conversely, executing unverified third-party repackaging scripts introduces supply-chain vulnerabilities into developer workstations.

This technical guide demonstrates how to deploy Claude Desktop and configure its local execution agent, Claude Cowork, on Fedora Linux Workstation. Using the open-source installation helper claude-desktop-rpm, this deployment strategy preserves strict cryptographic chain-of-trust verification, runs application binaries inside unprivileged user-space directories, and bridges native Fedora KVM/QEMU virtualisation infrastructure to support local execution tasks.

1. The Debian-Only Linux Beta and the Fedora Workstation Gap

Anthropic’s software distribution architecture for the Claude Desktop Linux beta relies entirely on standard Debian APT repositories. Linux distributions outside the Debian and Ubuntu families lack native repository definitions and binary packaging for this client. Platform engineers running Fedora Workstation face an architectural trade-off when integrating proprietary tools published under restrictive distribution models:

  1. System-Wide Package Conversion: Converting .deb archives to RPM via automated tools and installing them using rpm -i or dnf install installs unverified file layouts into system locations such as /usr/bin and /usr/share. This pollutes the local RPM database, breaks file dependency tracking, and causes audits using rpm -V to fail.
  2. Containerised Wrappers: Running the desktop client inside Flatpak or OCI containers isolates the binary, but introduces complex permission layers that interfere with desktop integration features such as system keyrings, IPC mechanisms, and local socket mounting required by execution agents like Cowork.
  3. Engineered User-Space Extraction: Extracting official binaries directly from upstream repositories into user-controlled paths (~/.local/share, ~/.local/bin) avoids root elevation during software installation. This pattern protects system paths while maintaining full access to host desktop interfaces.

The helper script claude-desktop-rpm, maintained by Ajith Kumar Karudasevai under the MIT license, implements this user-space extraction pattern. It acts strictly as an installation workflow orchestrator: it contains zero proprietary binaries from Anthropic. Instead, it interacts directly with Anthropic’s official APT repository during execution, retrieving upstream assets directly over TLS, validating signatures, and unpacking the binaries locally.

Upstream Compatibility Baseline

The installation workflow detailed in this guide is verified on Fedora 44 Workstation (GNOME, x86_64) and passes automated build and installation test suites on Fedora 45. Community reports indicate functional operation on immutable and atomic Fedora variants, such as Aurora using KDE Plasma, though GNOME Workstation remains the primary target configuration.

  • Foreign RPM Conversion (e.g. Alien)
  • Yes (System-wide)
  • Tainted (Fails rpm -V)
  • Bypassed / Broken
  • Manual path mapping required
  • Manual Unpack to /opt
  • Yes
  • Untracked binaries
  • Manual verification required
  • Requires custom permission rules
  • claude-desktop-rpm (User-Space)
  • No (Application deployment)
  • 100% Clean
  • Enforced (GPG + double SHA256)
  • Native (via standard QEMU/KVM)
  • Deployment Method Root Access Required? RPM Database Integrity Cryptographic Chain-of-Trust Cowork KVM Compatibility

    2. Cryptographic Integrity: How Repository Verification Works

    Downloading third-party binaries directly from remote repositories requires cryptographic validation to prevent man-in-the-middle (MITM) attacks, repository poisoning, or incomplete payload delivery. The claude-desktop-rpm utility executes a multi-stage validation sequence against Anthropic’s APT repository before any binary archive is extracted to disk.

    To execute the verification engine, the host operating system must have standard system utility dependencies installed. On Fedora Workstation, these packages are supplied by default or can be verified using DNF:

    sudo dnf install curl gnupg2 binutils tar

    The verification sequence models the security validation steps that APT perform under Debian systems. The architecture of this verification chain follows four rigid stages:

    +---------------------------------------------------------------------------------+
    |                         Verification Sequence Architecture                      |
    +---------------------------------------------------------------------------------+
    | 1. Download Anthropic Public Key  --> Match Pinned GPG Fingerprint               |
    |                                            |                                    |
    | 2. Fetch InRelease Index           --> Verify GPG Signature + Valid-Until Date  |
    |                                            |                                    |
    | 3. Parse Packages.gz Checksum      --> Match SHA256 against InRelease manifest  |
    |                                            |                                    |
    | 4. Fetch Claude Desktop .deb       --> Match SHA256 against Packages.gz entry   |
    |                                            |                                    |
    |                                   [ EXTRACT TO ~/.local ]                       |
    +---------------------------------------------------------------------------------+
    

    Validation Stage Details

    1. GPG Fingerprint Pinning: The script fetches Anthropic’s official public GPG signing key and compares its fingerprint against an immutable fingerprint hardcoded inside the script. This ensures that compromised upstream key-servers or rogue keys cannot sign payload metadata.
    2. Signed Repository Index Verification: The script downloads the upstream InRelease file. Using gpg2, it validates that the index signature matches the pinned key. Crucially, it parses the Valid-Until timestamp header within the InRelease document to ensure the repository metadata is current, preventing replay attacks using stale index manifests.
    3. Package Index Checksum Matching: The script extracts the hash of the target Packages.gz index from the verified InRelease document. It downloads Packages.gz and verifies that its computed SHA256 checksum matches the signed manifest entry exactly.
    4. Binary Package Integrity Verification: The script parses Packages.gz to retrieve the exact filename, relative repository path, and expected SHA256 checksum of the latest claude-desktop .deb package. Upon downloading the .deb file, the script calculates its SHA256 digest on the local filesystem. Only when this matches the index value does extraction proceed.

    If any cryptographic check fails—whether an expired index, a mismatched hash, or an invalid signature—the installer immediately aborts, purges temporary working files in /tmp, and leaves the host environment untouched.

    3. User-Space Deployment and Non-Root System Integration

    Standard software installations on Linux traditionally write files into system directories controlled by root. The user-space deployment pattern places all application code, desktop menu definitions, icon sets, and runtime launchers within the user’s home directory structures defined by the XDG Base Directory Specification.

    Step 1: Verify and Execute the Installer

    First, download the installer script alongside its cryptographic checksum manifest from the project’s official release asset pipeline:

    curl -fLO https://github.com/ajithakdev/claude-desktop-rpm/releases/latest/download/claude-desktop-rpm.sh
    curl -fLO https://github.com/ajithakdev/claude-desktop-rpm/releases/latest/download/SHA256SUMS
    
    # Verify installer script integrity prior to execution
    sha256sum -c SHA256SUMS --ignore-missing

    After verifying that the script output reports OK, grant execution flags and run the installation workflow as an unprivileged user:

    chmod +x claude-desktop-rpm.sh
    ./claude-desktop-rpm.sh install

    Step 2: Directory Isolation Model

    During installation, binutils extracts the data.tar.xz archive embedded inside the verified .deb package. The script maps the upstream Debian path structures directly to unprivileged user directories:

    • ~/.local/bin/claude-desktop-rpm: A self-copy of the management script used for future lifecycle tasks.
    • ~/.local/share/claude-desktop/: Contains extracted application assets, Electron runtime resources, and core binaries.
    • ~/.local/share/applications/claude-desktop.desktop: Desktop launcher entry integrated into the host desktop environment.
    • ~/.local/share/icons/hicolor/: Scalable and raster application icons registered with standard desktop themes.
    • ~/.config/Claude/: User application data, runtime state, local databases, and Cowork configuration profiles.

    Step 3: Handling GNOME GTK Dark Theme Integration

    Electron applications running under GNOME on Linux frequently display light-themed user interfaces even when the host system enforces a dark preference. This occurs because GNOME’s system-wide dark style preference toggles a Freedesktop color-scheme setting rather than changing the traditional GTK theme string. Electron reads the standard GTK theme name (e.g. Adwaita) and defaults to light mode rendering.

    To resolve this without altering Anthropic’s binary payloads or editing core application code, the custom desktop launcher wrapper generated by claude-desktop-rpm checks the desktop environment settings conditionally upon invocation. The launcher evaluates GNOME’s active color scheme and prepends environment flags when launching the application process:

    #!/usr/bin/env bash
    # Excerpt of the conditional launcher configuration pattern
    
    COLOR_SCHEME=$(gsettings get org.gnome.desktop.interface color-scheme 2>/dev/null)
    
    if [ "$COLOR_SCHEME" = "'prefer-dark'" ] && [ -z "$GTK_THEME" ]; then
        export GTK_THEME="Adwaita:dark"
    fi
    
    exec ~/.local/share/claude-desktop/claude %U

    If you have explicitly declared a custom GTK_THEME variable within your login shell profile (e.g., ~/.bashrc or ~/.config/environment.d/), the launcher defers to your explicit user configuration.

    4. Configuring KVM and QEMU Virtualisation for Claude Cowork

    Claude Cowork enables the Claude Desktop client to execute agentic tasks, run code, and manipulate workspace files locally. To insulate the host operating system from unintended file modifications or arbitrary command side effects, Cowork executes these agent tasks inside a isolated local micro-virtual machine.

    On Debian systems, Cowork relies on Debian-packaged QEMU binaries and custom configuration paths. On Fedora Workstation, these dependencies must be supplied using Fedora’s native hypervisor stack, including Kernel-based Virtual Machine (KVM) acceleration, QEMU system emulation, Open Virtual Machine Firmware (OVMF) for UEFI support, and virtiofsd for high-performance host-to-guest directory sharing.

    +---------------------------------------------------------------------------------+
    |                        Claude Cowork Architecture on Fedora                     |
    +---------------------------------------------------------------------------------+
    |  +---------------------------------------------------------------------------+  |
    |  | Host User Space (~/.local / GNOME Desktop)                                |  |
    |  |  [ Claude Desktop Application ]                                           |  |
    |  +------------------------------------+--------------------------------------+  |
    |                                       | Virtio Socket (vsock) / UNIX Socket     |
    |                                       v                                         |
    |  +---------------------------------------------------------------------------+  |
    |  | Host System Virtualisation Services (Root/Group Protected)                |  |
    |  |  [ virtiofsd ] <-- Host Directory Mounts (~/.config/Claude/workspace)     |  |
    |  |  [ KVM Kernel Module ] + [ vhost_vsock Kernel Module ]                    |  |
    |  +------------------------------------+--------------------------------------+  |
    |                                       | Hardware Virtualisation                      |
    |                                       v                                         |
    |  +---------------------------------------------------------------------------+  |
    |  | Isolated Guest Micro-VM (QEMU + edk2-ovmf UEFI Firmware)                  |  |
    |  |  [ Agent Execution Environment ] (~12 GB disk state in ~/.config/Claude)   |  |
    |  +---------------------------------------------------------------------------+  |
    +---------------------------------------------------------------------------------+
    

    Provisioning the Cowork Hypervisor Stack

    Unlike the baseline application deployment, establishing the virtualisation framework for Cowork requires administrative privileges to install native Fedora packages, write system module configurations, and update user group memberships. Execute the setup command:

    claude-desktop-rpm cowork

    This command performs three critical system configuration steps:

    1. Package Installation via DNF: Installs qemu-system-x86-core (providing core hypervisor binaries), edk2-ovmf (providing UEFI boot firmware files), and virtiofsd (providing low-latency virtual filesystem daemon functionality).
    2. Kernel Module Configuration: Configures automated kernel module loading for vhost_vsock by creating /etc/modules-load.d/vhost_vsock.conf and immediately executing modprobe vhost_vsock. The vhost_vsock module enables socket-based inter-process communication between the host application and the guest virtual machine without network overhead.
    3. KVM Group Provisioning: Adds your local user account to the system kvm group, granting access to /dev/kvm device nodes without root privileges.

    Session Re-authentication Required

    Group membership changes in Linux are applied upon session establishment. After running claude-desktop-rpm cowork, you must completely log out of your desktop session and log back in (or reboot) for your user account to acquire active kvm group privileges. Verify membership using the groups command before launching Cowork.

    RPM Database Integrity Preservation

    An early iteration of community installation scripts modified firmware symlinks owned by the edk2-ovmf RPM package to match Debian file locations. Modifying files owned by system packages violates RPM management boundaries and causes package audit failures during system upgrades.

    The current version of claude-desktop-rpm respects package ownership boundaries entirely. It leaves system firmware files in their standard Fedora paths (/usr/share/edk2/ovmf/) and maps paths through application-level launcher environment variables and local symlinks within ~/.config/Claude/. Consequently, running rpm -V edk2-ovmf qemu-system-x86-core returns zero checksum or file state discrepancies.

    Storage Budget Requirements

    When provisioning local storage for Cowork, account for the virtual machine image footprint. The guest image, base filesystem, and persistent execution state require approximately 12 GB of storage within your home directory path at ~/.config/Claude/. Ensure that the filesystem backing ~/.config has sufficient free capacity to avoid disk-full errors during agent execution cycles.

    5. Automating Background Updates via Systemd User Timers

    Because the application is deployed from an extracted .deb package without registering a system APT or DNF repository, traditional package management updates will not detect new upstream releases. Conversely, relying on the internal update notification prompt displayed by the Claude Desktop UI will fail: the “Update available” button points to Debian APT installation routines incompatible with Fedora.

    To deliver automated, unprivileged updates, claude-desktop-rpm provisions a background systemd user service and timer pair during installation.

    Systemd User Service Architecture

    The installer creates two unit files within the user’s systemd configuration path (~/.config/systemd/user/):

    • claude-desktop-rpm-update.service: Executes the script update routine using ~/.local/bin/claude-desktop-rpm update --quiet.
    • claude-desktop-rpm-update.timer: Triggers the update service once every 24 hours, scheduling runs with a randomized delay to avoid server synchronization spikes.
    # ~/.config/systemd/user/claude-desktop-rpm-update.timer
    [Unit]
    Description=Daily update check for Claude Desktop
    
    [Timer]
    OnCalendar=daily
    RandomizedDelaySec=1h
    Persistent=true
    
    [Install]
    WantedBy=timers.target

    Payload Staging and Deferred Replacement

    To prevent application crashes caused by replacing binary files while Electron is running, the background update mechanism uses a deferred payload swap workflow:

    1. The daily systemd user timer executes the update routine in the background.
    2. The script contacts Anthropic’s APT repository, validates all GPG signatures and SHA256 checksum manifests, and checks whether the upstream package version is newer than the installed version.
    3. If a new release is validated, the script downloads and extracts the update into an isolated staging directory: ~/.local/share/claude-desktop-staging/.
    4. If the Claude Desktop process is actively running, the script leaves the active installation unchanged and registers a pending update flag file.
    5. When you launch Claude Desktop, the wrapper script checks for the staging directory, replaces the contents of ~/.local/share/claude-desktop/ prior to process initialization, and cleans up the staging path.

    Manual Update Control Commands

    You can manage and inspect the automated update subsystem directly using the management utility:

    # Disable the background update timer
    claude-desktop-rpm auto-update off
    
    # Enable the background update timer
    claude-desktop-rpm auto-update on
    
    # Force an immediate foreground update check and installation
    claude-desktop-rpm update

    6. Managing Multi-Account Workflows and Chromium Profiles

    Engineers and platform administrators often require access to multiple Claude instances concurrently—maintaining separate sign-in sessions for enterprise corporate tenants, client accounts, and personal subscriptions. Because Claude Desktop stores authentication tokens and session data in unified configuration directories, logging in with a secondary account normally overwrites existing credentials.

    To solve this, claude-desktop-rpm provides a multi-profile management mechanism built on top of Chromium’s underlying profile directory flags.

    Profile Creation and Directory Segregation

    To generate an isolated secondary environment for a professional account, run:

    claude-desktop-rpm profile add work

    This command creates a dedicated profile structure and menu wrapper using the following mechanics:

    1. Generates a dedicated data store path at ~/.config/Claude-work/.
    2. Creates an additional desktop application entry at ~/.local/share/applications/claude-desktop-work.desktop.
    3. Configures the desktop launcher to pass Chromium’s data directory flag during binary execution: --user-data-dir=$HOME/.config/Claude-work.
    4. Registers a distinct desktop launcher title (“Claude (work)”) within the GNOME application grid.
    # Launching profile instances from the command line
    ~/.local/share/claude-desktop/claude --user-data-dir=$HOME/.config/Claude-work &

    Upstream Profile Parameter Constraints

    Passing --user-data-dir leverages underlying Chromium flag handling inherited by Electron. Anthropic does not officially document or support this parameter for Claude Desktop. If a future application release strips or overrides unrecognised command-line flags, profile shortcuts may revert to launching the default profile path at ~/.config/Claude/. System data and separate profile folders will remain intact on disk.

    Tray Icon Limitations and Identification

    When running multiple profile instances concurrently, GNOME desktop tray implementations display an AppIndicator icon for each active process. However, because both instances share the same packaged tray graphics, the visual menu bar icons appear identical. To distinguish between active profiles, click the system tray icon to reveal the context menu: the top header of the context menu displays the specific plan tier and user profile associated with that session instance.

    7. System Maintenance, Diagnostic Audits, and Uninstallation

    Maintaining non-native desktop packages requires diagnostic tooling to detect missing dependencies, broken launcher paths, or invalid permissions. The claude-desktop-rpm utility provides a built-in health check subsystem alongside an uninstaller.

    Running System Diagnostic Audits

    To verify that all application components, systemd timers, desktop linkages, and virtualisation permissions are operating correctly, run the doctor subcommand:

    claude-desktop-rpm doctor

    The diagnostic engine audits the system against a six-point operational checklist:

  • Binary Extraction
  • ~/.local/share/claude-desktop/claude
  • Re-run claude-desktop-rpm.sh install
  • Launcher Integration
  • ~/.local/share/applications/claude-desktop.desktop
  • Re-build desktop cache via update-desktop-database
  • Systemd User Timer
  • systemctl --user is-active claude-desktop-rpm-update.timer
  • Run claude-desktop-rpm auto-update on
  • GNOME Tray Extension
  • AppIndicator GNOME Shell extension presence
  • Install gnome-shell-extension-appindicator via DNF
  • Keyring Access
  • Secret Service API provider (gnome-keyring)
  • Verify PAM keyring initialization on session login
  • Cowork Prerequisites
  • /dev/kvm permissions, vhost_vsock module, virtiofsd
  • Run claude-desktop-rpm cowork and re-login
  • Diagnostic Check Target Component / Path Verified Remediation if Validation Fails

    Common Operational Mistakes

    • Executing Install Commands with Sudo: Running sudo ./claude-desktop-rpm.sh install extracts application binaries into /root/.local rather than your user’s home directory. The installer must always be executed as an unprivileged user. Root elevation is only required during the cowork phase.
    • Clicking Upstream In-App Update Notifications: Clicking the application update prompt inside the Electron interface will fail or display errors about missing apt-get binaries. Ignore in-app update prompts; allow the daily systemd user timer or run claude-desktop-rpm update manually.
    • Launching Cowork Before Group Membership Reload: Attempting to initialize Cowork immediately after running the virtualisation setup script without logging out results in hypervisor initialization errors due to missing /dev/kvm permissions.

    Complete Uninstallation and State Scrubbing

    To remove the application binary, desktop launchers, systemd timers, and icon manifests without leaving orphan files, run the uninstaller:

    claude-desktop-rpm uninstall

    This command performs the following cleanup steps without requiring root elevation:

    1. Stops and disables the systemd user timer and service units.
    2. Deletes ~/.local/share/claude-desktop/ and all associated profile launchers in ~/.local/share/applications/.
    3. Purges icon assets from ~/.local/share/icons/hicolor/.
    4. Rebuilds local system desktop databases and icon caches via update-desktop-database and gtk-update-icon-cache.

    By default, your sign-in tokens, local databases, and chat histories stored in ~/.config/Claude/ (and any profile paths like ~/.config/Claude-work/) are preserved to prevent data loss if you reinstall. To purge all application state and release the ~12 GB Cowork VM storage budget completely, manually delete those directories:

    # Optional: Completely remove all user state and chat history databases
    rm -rf ~/.config/Claude ~/.config/Claude-*

    Because the main application installation operates purely within user-space, running claude-desktop-rpm uninstall does not automatically remove the host virtualisation packages installed during the cowork configuration step. If you no longer require KVM virtualisation tools or the virtiofsd daemon for other workloads, remove them via DNF and delete the module configuration file:

    # Optional: Clean up system-level Cowork virtualisation packages
    sudo dnf remove qemu-system-x86-core edk2-ovmf virtiofsd
    sudo rm -f /etc/modules-load.d/vhost_vsock.conf

    8. Key Architectural Takeaways for Fedora Workstation Operations

    Deploying proprietary Debian-first developer tools onto RHEL-family workstations like Fedora requires balancing developer productivity against system integrity and security boundaries. The user-space deployment pattern analyzed here offers several critical operational guarantees:

    • Multi-Layer Security Validation: Cryptographic verification of upstream APT manifests—via pinned GPG key checking, expiration timestamp parsing, and double SHA256 checksum matching—guarantees that unverified or tampered code is never executed.
    • Absolute System Database Purity: By confining application assets to unprivileged paths inside ~/.local and ~/.config, system updates remain uninhibited, third-party binary conflicts are prevented, and system integrity verification via rpm -V remains completely clean.
    • Clean Boundary Separation: System-level administrative privileges are isolated strictly to infrastructure requirements (KVM enablement, QEMU binaries, and kernel module loading), while the application layer operates with zero administrative rights.

    By implementing this isolated user-space wrapper model, platform engineers and sysadmins can deploy Claude Desktop and leverage local execution workflows via Claude Cowork on Fedora Linux without compromise.

    Frequently asked questions

    Is root access required to install Claude Desktop on Fedora Linux?

    No, root access is not required for the standard application. The installer extracts binaries, menu entries, icons, and background update timers directly into your unprivileged user directories (~/.local and ~/.config). Root access via sudo is only required if you choose to set up Claude Cowork, which needs system-level virtualisation packages installed via DNF.

    How does Cowork virtualisation interact with Fedora’s KVM and QEMU setup?

    Claude Cowork executes agent tasks inside a local virtual machine for safety. On Fedora, the setup command installs native packages (qemu-system-x86-core, edk2-ovmf, virtiofsd), loads the vhost_vsock kernel module, and grants your user account access to /dev/kvm. This bridges Fedora’s native hypervisor stack to the client without altering package firmware links.

    Why does Claude Desktop stay light when GNOME is set to dark mode?

    Electron applications on Linux query the traditional GTK theme name rather than GNOME’s modern color-scheme preference. Because GNOME’s dark setting does not change the GTK theme string, Electron defaults to light rendering. The launcher generated by the install script checks GNOME’s active color scheme at startup and sets GTK_THEME=Adwaita:dark automatically when dark mode is enabled.

    How are automatic updates handled without APT or native RPM repositories?

    Updates are managed by a systemd user timer that runs once daily in the background. The timer downloads Anthropic’s APT index, verifies GPG signatures and SHA256 checksums, and stages new binaries in ~/.local/share/claude-desktop-staging/. If the application is open, the update waits safely and swaps the files into place the next time you launch Claude.

    How do I completely remove Claude Desktop and its virtualisation prerequisites from Fedora?

    Run claude-desktop-rpm uninstall to remove all user-space binaries, desktop launchers, systemd timers, and icon assets. To delete remaining chat histories and the ~12 GB Cowork VM image, delete ~/.config/Claude. To remove system virtualisation packages installed for Cowork, run sudo dnf remove qemu-system-x86-core edk2-ovmf virtiofsd and remove /etc/modules-load.d/vhost_vsock.conf.

    Sources and further reading

    This article was drafted with AI assistance from the publicly cited sources and passed automated checks for structure and sourcing. Verify critical details against the vendor advisories linked above before acting.