Shadowfetch Linux releases

https://www.shadowfetchlinux.org/releases.atom.xml Shadowfetch Linux releases Release announcements for Shadowfetch Linux, with checksums and signatures. 2026-10-01T00:00:00Z Shadowfetch Linux Release metadata; see the linked pages for licensing. https://www.shadowfetchlinux.org/releases/5.0.1 Shadowfetch Linux 5.0.1 «Umbra» - ShadowCode (update) 2026-10-01T00:00:00Z

Shadowfetch Linux 5.0.1 is an update for 5.0, delivered through the signed Shadowfetch APT repository; it has no ISO of its own. Installed 5.0.0 and 4.1 systems get it with sudo apt update, then sudo apt full-upgrade (this once, not fireproof update), and new installs start from the 5.0.0 ISO and update. It fixes fireproof update, which stopped partway when it updated Fireproof itself and could remove packages during a Debian testing transition: from 5.0.1 on, fireproof update is safe again and never removes packages during an update. It brings ShadowCode 1.0.1, whose window no longer grows each time it opens, fixes Mission Control answering "database is busy" under heavy disk load, lets Stop work while the database is busy, runs missions created in the same second in the order you created them, and says why a queued mission is waiting. Every Shadowfetch package moves to 5.0.1-1. Nothing a working 5.0.0 setup depends on is removed or renamed. What changed: - fireproof update can update Fireproof itself. Until now the incoming package's install script stopped fireproofd, the daemon that runs apt and dpkg, so dpkg was killed halfway through and the update could hang for up to an hour. No install script stops fireproofd any more, stopping it signals only the daemon (KillMode=mixed), needrestart leaves it alone, and the new daemon takes over once the update has finished. An earlier update that was interrupted is reported with the command that repairs it, sudo dpkg --configure -a && sudo apt -f install, instead of being built on. - Fireproof never removes packages as a side effect of an update. While Debian testing is in the middle of a library transition, it keeps the packages an upgrade would remove and holds back only those upgrades, lists them and says why; the rest of the update goes ahead, and held-back updates are not counted on the update badge. shadowfetch-desktop, shadowfetch-creative-base and anything you installed yourself are never removed by an update. - ShadowCode 1.0.1 fixes the window that grew each time it opened under Wayland: it no longer saves its size (position and maximized state are still restored), and the first window is fitted to the screen it opens on. shadowfetch-desktop now requires shadow-code (>= 1.0.1). - Mission Control no longer answers "database is busy" under heavy disk load. No database connection copies SQLite's write-ahead log back on close any more, which held an exclusive lock through two disk syncs, and show, list, events and the desktop's views read while the worker writes. shadowfetch-missions now needs Python 3.12 or newer, which 5.0 already ships. - Stop works while the database is busy. shadowfetch-missions cancel saves the request first and answers at once; the worker records it in the mission's history at its next check, and a queued mission whose stop is not yet recorded does not start. Mission Control shows "Stop requested: saved, waiting to be recorded" until then. A Stop that arrives while the mission is already finishing is recorded as asked for and not applied, never lost. - Missions created in the same second run, and list, in the order you created them. 5.0.0 broke such ties on the random mission id. - A queued mission held until you review another mission for the same project says so: show and list report a hold naming the mission to review, and Mission Control shows the reason on the queue row and under Waiting in the mission's Overview. - shadowfetch-defaults no longer starts KDE's update notifier on a live USB, so a live session would not download package lists after login. An update cannot change a USB stick: this reaches the live USB only with a later ISO, and a 5.0.0 stick keeps the refresh. Installed systems keep update notifications. Update through the signed Shadowfetch APT repository (suite umbra); Shadowfetch packages 5.0.1-1. No ISO of its own. Update an installed system: sudo apt update, then sudo apt full-upgrade New installs: the Shadowfetch Linux 5.0.0 ISO, then update Install media: shadowfetch-5.0.0-amd64.iso Install media SHA-256: 2d8a72e044e8061bd616b2b4668425cc4d4ec0480a98975f961c0e58cba95e21 Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-5.0.0-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-5.0.0-amd64.iso.asc Known limitation - Install this update with apt, not fireproof update: on a 4.1 or 5.0.0 system the update is still run by the Fireproof already installed, which can stop partway through updating Fireproof itself and can remove packages during a Debian testing transition. Run sudo apt update, then sudo apt full-upgrade; packages apt lists as kept back are expected during a transition, and apt removes nothing. From 5.0.1 on, fireproof update is safe again. If an earlier update stopped partway (sudo dpkg --audit prints anything, or apt asks for dpkg --configure -a): if apt says the lock is held by fireproofd, run sudo systemctl kill --signal=KILL fireproofd.service first; then run sudo dpkg --configure -a, then sudo apt full-upgrade, then sudo apt install shadowfetch-desktop shadowfetch-creative-base, and restart. Known limitation - Live USB: there is no 5.0.1 ISO, so every live USB is a 5.0.0 stick and keeps KDE's update notifier. About five minutes after login it refreshes the package lists, a download of about 200 MB that also takes about 350 MB of RAM. If the computer is low on memory or the connection is metered, stay offline in the live session or run systemctl --user stop app-org.kde.discover.notifier@autostart.service soon after logging in. Installed systems are not affected. Known limitation - After updating, the Mission Control worker already running in your session is still the 5.0.0 engine until you log out and back in, or run systemctl --user restart shadowfetch-missions.service. Known limitation - A shadowfetch-missions create that answers "database is busy" may already have queued the mission: after it commits, the engine reads the database once more to write the mission's entry to the system journal, and in rare cases under very heavy disk load that read is the one that answers busy. Check shadowfetch-missions list before creating it again. Not fixed in 5.0.1. Known limitation - Stop can still be slow on a saturated disk in one case: right after SQLite has emptied its log, the next write restarts the log with two disk syncs, and on the 5.0.0 stress guest one sync took up to 34 seconds. The Stop is saved before that write, so the worker still records it. Known limitation - Carried from 5.0.0, unchanged: the security advisory about the shared DKMS module-signing key on systems installed from 4.x ISOs (shadowfetch-doctor still flags it), OpenClaw's security-advisory record, Hermes Agent running unsandboxed, the agent network not setting ShadowCode's own network mode, ShadowCode's first run opening light on the dark desktop, ShadowCode's glibc 2.39 and Vulkan requirements, and Secure Boot that is not Microsoft-signed. See the known-issues page. https://www.shadowfetchlinux.org/releases/5.0.0 Shadowfetch Linux 5.0.0 «Umbra» - ShadowCode 2026-09-30T00:00:00Z

Shadowfetch Linux 5.0.0 "ShadowCode" is rebuilt around ShadowCode 1.0.0, preinstalled from its signed upstream .deb: the desktop's coding agent, reaching the models of the subscriptions (Codex, Claude Code, Cursor, Antigravity, Grok, through each vendor's own CLI), API keys (OpenRouter) and local runtime (a bundled llama.cpp) you already have, with you approving actions and reviewing diffs. Fire and Ice are replaced by one gold-and-steel-on-black look, and their security half survives as shadowfetch-agent-network online|offline. Welcome offers exactly three optional agents -- Grok Bot, Hermes Agent and OpenClaw -- then hands you to ShadowCode to connect your services. Buzz and the shadowfetch-codex / shadowfetch-code-agent helpers are removed. What changed: - ShadowCode 1.0.0 is preinstalled as package shadow-code. Shadowfetch republishes upstream's .deb byte for byte; its Ed25519-signed release metadata is checked against a vendored trust policy at fetch, package-gate and ISO-gate time, and the bundled llama.cpp may live only under /usr/lib/shadowcode/. - One picker in ShadowCode: subscriptions through each vendor's own command-line tool, an OpenRouter API key billed per token, or a free local model run by the bundled llama.cpp. You approve actions and review each task's diff. - ShadowCode 1.0 is easy to start and ready for real work: free local models are listed first until you connect a subscription, a failed task says what went wrong in plain words with the next step, and ? opens a glossary. Approval cards say what an action does, how much it can affect and whether Rewind can undo it; Always allow here covers exact test and build commands per project. Commits, pushes and pull requests are checked for secrets first, new packages are looked up on npm, PyPI and crates.io, and API keys can move into the system keyring, which is created and unlocked at login so saving a key does not prompt. One rulebook reaches every agent; second opinions, per-step roles, spending limits ($1 a task and $10 a day by default), stuck detection, a code index for up to 250,000 files and review grouped by risk come with it. - One look: gold #F2B33D and steel #BCC0C6 on black, from a new emblem and wallpaper across Plasma, SDDM, Plymouth, GRUB and the installer. The Ice colour scheme, Glacier Konsole scheme, Ice look-and-feel and the Fire/Ice wallpapers are removed; a one-time login migration repoints only settings that named a removed asset. - shadowfetch-agent-network online|offline replaces the Fire/Ice switch's security half. Firebreak, Grok Bot, Hermes, OpenClaw, Workbench, Mission Control and Welcome read it; an upgraded Ice machine reads as offline, so no sandbox gains network. The boot menu offers the offline choice and the installer carries it to the installed system. - Welcome offers exactly three optional agents -- Grok Bot, Hermes Agent (Nous Research) and OpenClaw -- each installed only if you pick it, then opens ShadowCode to connect your services. None is preinstalled. - Removed: Buzz (including the 4.x retirement helper), shadowfetch-codex, shadowfetch-code-agent and shadowfetch-element. ShadowCode connects the vendor CLIs itself. SHA-256: 2d8a72e044e8061bd616b2b4668425cc4d4ec0480a98975f961c0e58cba95e21 Size: 4085778432 bytes - 4.09 GB (3.81 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-5.0.0-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-5.0.0-amd64.iso.asc GitHub release: https://github.com/Shadowfetchapps/shadowfetch-linux/releases/tag/v5.0.0 Known limitation - Update with apt for now, not fireproof update. When fireproof update installs a new version of Fireproof itself, which every 4.1 to 5.0 upgrade does, it stops partway through and can stay stuck for up to an hour. Fireproof's update plan can also currently remove the desktop metapackages (shadowfetch-desktop, shadowfetch-creative-base) and apps such as Krita and Kdenlive while Debian testing is in the middle of a library transition; apt holds those packages back instead. Until further notice, update from a terminal with sudo apt update, then sudo apt full-upgrade, and not with fireproof update or Control Center's Software page. If an update already stopped partway (sudo dpkg --audit prints anything, or apt asks for dpkg --configure -a): 1) if apt says the lock is held by fireproofd, run sudo systemctl kill --signal=KILL fireproofd.service (a normal restart is refused while it is stuck; sudo systemctl reboot -i also works); 2) run sudo dpkg --configure -a, then sudo apt full-upgrade, then sudo apt install shadowfetch-desktop shadowfetch-creative-base; 3) restart. Known limitation - ShadowCode 1.0.0's window grows each time it opens on Wayland: each launch restores a slightly larger window, which can end up extending under the panel, and on a 1366x768 screen even the first window is larger than the screen. Workaround: maximize the window (its maximize button, or Meta+PgUp); ShadowCode then does not save the size. Fixed in ShadowCode 1.0.1, part of the 5.0.1 update. Known limitation - Under very heavy disk load, Mission Control or a shadowfetch-missions command can briefly report "database is busy" while a mission is finishing a step. Nothing is lost; retry after a few seconds and it works. Fixed in the 5.0.1 update. Known limitation - Live USB: about five minutes after login, KDE's update notifier refreshes the package lists, a download of about 200 MB that also takes about 350 MB of RAM because the live session keeps its changes in memory. Installed systems are not affected. If the computer is low on memory or the connection is metered, stay offline in the live session or stop the notifier with systemctl --user stop app-org.kde.discover.notifier@autostart.service. An update cannot change a USB stick: 5.0.1 is an APT update with no ISO of its own, so a 5.0.0 stick keeps the refresh. Known limitation - The 5.0.1 update fixes the first three issues above: from 5.0.1 on, fireproof update can update Fireproof itself and removes no packages during an update. Install 5.0.1 itself with sudo apt update, then sudo apt full-upgrade, not with fireproof update. It arrives through the Shadowfetch APT repository and cannot change a live USB stick, so on a 5.0.0 stick use the workaround for the fourth. Known limitation - Published 2026-09-30. The ISO, its signature and checksum, the CycloneDX SBOM, the package manifest, the release dossier and the QA evidence bundle are on the download server and attached to the v5.0.0 GitHub release; PUB-01 confirmed that GitHub, this site, the signed downloads and APT expose the same release. Known limitation - Acceptance on this exact ISO: 12 cases pass (including EVIDENCE-01) and 6 are waived by the release owner, who chose to ship this image and deliver its fixes through APT updates, starting with 5.0.1. Four waivers are account or harness limits: MISSION-01's code missions need a paid vendor account (the media and cited-report missions pass); GROK-01 and GROK-VISUAL-01 need an X/Grok account (install, integrity, launch to sign-in and the URL handler are proven; a signed-in session is not); UPGRADE-01's recovery leg has no harness. Two are checks that did not pass: SHADOWCODE-01's open/close soak failed only its memory-drift check, which a diagnostic rerun traced to the live session's one-time package-list refresh rather than ShadowCode; STRESS-01's two 45-minute runs of combined stress left the system healthy, but in both runs its mission loop stopped on "database is busy" and its container loop on a podman run --rm client that did not exit. Known limitation - The 4.1 -> 5.0 in-place upgrade passed with every migration check (gold accent, the doctor's shared-key check, the one-time notice, the agent-network migration, retired launchers removed, user data preserved). Its recovery leg is waived: the VM harness cannot roll an upgraded system back, so rollback after an upgrade was not exercised. Known limitation - The APT suite name stays umbra, so 4.1 systems receive 5.0 from the suite they already track. Known limitation - OpenClaw has a long security-advisory record. Shadowfetch pins its lockfile, sandboxes it in Firebreak and never installs its Gateway by default; that narrows exposure but does not make it safe, and an enabled Gateway runs outside the sandbox with your file access. Keep it updated. Known limitation - Hermes Agent is not sandboxed: it runs commands and edits files as you. Known limitation - shadowfetch-agent-network governs Firebreak sandboxes and the three optional agents only. ShadowCode starts Online by default; its own Settings › Permissions & network › Offline limits it to local models. Known limitation - ShadowCode's own agent runs shell commands in its sandbox; vendor CLIs (Codex, Claude Code, Cursor, Antigravity, Grok) enforce their own sandbox and do not inherit it. Known limitation - On a machine with no GPU render node (many virtual machines), ShadowCode's window would idle at high CPU: 122-174% in 5.0 VM qualification. Shadowfetch sets WEBKIT_DISABLE_DMABUF_RENDERER=1 for the session only on such machines, which brought it to about 7% over two minutes; ShadowCode 1.0.0 does not handle this itself yet. Known limitation - ShadowCode's first run can open in its light theme on the dark desktop; choose Dark in ShadowCode's settings. Known limitation - Secure Boot is not Microsoft-signed; disable Secure Boot or follow the documented enrollment path. Known limitation - Grok Bot needs an eligible account and internet. Hermes and OpenClaw need your own model-provider key. Known limitation - Security advisory for 4.x installs: earlier ISOs shipped a shared DKMS module-signing key. It matters only if you enrolled its certificate in Secure Boot; see the known-issues page for the check and the fix. 5.0.0 images are built without it. https://www.shadowfetchlinux.org/changelog#v4-1-0 Shadowfetch Linux 4.1.0 «Umbra» - Egress and Syscall Filters 2026-09-10T00:00:00Z

Shadowfetch Linux 4.1.0 turns three recorded intentions into enforced controls. Every sandbox now gets its own network namespace, so a task no longer reaches the host's loopback services or its abstract sockets in either network posture. Where a mission declares destinations, a default-DROP nftables ruleset in that namespace permits only the addresses those names resolved to. A seccomp-BPF filter denies 46 syscalls in every sandbox, self-tested against the real program before any command exists, and refuses the run rather than starting unfiltered. Declared masked paths are real mounts instead of a line in a record. An on-device provider ships, so local AI is no longer deferred. Seven changes break working setups; read the release notes before upgrading. What changed: - An egress allowlist that filters: nftables with default DROP inside the sandbox's own network namespace, permitting only the addresses the declared hostnames resolved to on the host at launch. - A syscall filter in every sandbox: 46 calls answer EPERM, applied through bwrap --seccomp from a sealed memfd, and not declarable by a provider because a provider choosing its own syscall surface is the thing a sandbox exists in order not to depend on. - Masked paths are mounts now, not records: an empty tmpfs over a directory, /dev/null over a file, applied by bwrap with no cooperation from the payload. - Both network postures unshare the network, so host loopback services and abstract AF_UNIX sockets are out of reach even when a task is online. - An on-device provider (localmodel) runs code and report missions with network policy none. No model weights are bundled: the installation reports installed-unavailable until you supply a model service. - A mission with more than one ready provider for its capability now refuses to guess -- pass --provider. SHA-256: e19e96302f97e94d5284f8fbef181c9b0e49ca7b746afe5e66e4bc6d5c551f25 Size: 3980670976 bytes - 3.98 GB (3.71 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-4.1.0-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-4.1.0-amd64.iso.asc GitHub release: https://github.com/Shadowfetchapps/shadowfetch-linux/releases/tag/v4.1.0 Known limitation - Seven documented breaking changes. --provider is required where more than one provider is ready, an approval recorded before this release no longer covers a networked mission, --net allow no longer reaches host loopback, and shadowfetch-update is now a shim over fireproof. Read the release notes first. Known limitation - --net allow with NO declared destination installs no ruleset and reaches anything the machine can reach -- the LAN is not the extent of it. The allowlist is a control only where destinations are declared. Known limitation - DNS leaves a sandbox whose filter is working: the resolver must be reachable or nothing routes. An allowlist narrows where bytes may be sent, not what can be signalled out in a query name. Known limitation - Masking is by path, so a hardlink to the same inode under an unmasked name is still readable. Egress filtering is by resolved IPv4 address, fixed once at launch. Known limitation - RESOURCE-01 and STRESS-01 are waived rather than passed: the 45-minute concurrent stress load is clean (stress-ng, containers, missions and workbench all succeed; zero service-journal faults; the mission worker does not peg a core), but the harness includes an account-gated Grok probe that cannot pass without an eligible vendor account, so the run is accepted with a recorded reason. The two Grok Bot cases are waived for the same account reason. Known limitation - Secure Boot is not Microsoft-signed; disable Secure Boot or follow the documented enrollment path. Known limitation - QXL virtual machines can report no DRM render node / gpu-verify-failed. That is the known VM graphics caveat, not an installed-desktop failure. Known limitation - Grok Bot needs an eligible account and internet. Sign-in screenshots do not prove authenticated cloud work. https://www.shadowfetchlinux.org/changelog#v4-0-0 Shadowfetch Linux 4.0.0 «Umbra» - Mission Control 2026-09-06T00:00:00Z

Shadowfetch Linux 4.0.0 makes Mission Control the desktop for inspectable agent work. Fire and Ice are real install-time identities. Firebreak no longer pins process address space to the RSS budget, so the code-mode host can reserve V8 sandbox VA without SIGTRAP while MemoryMax, TasksMax and CPUQuota stay in place. Grok Bot is a featured startup choice. Local AI is deferred. This signed ISO passed fresh BIOS Fire and UEFI Ice Calamares installs, Core first-boot, and a code-mode session/execute with unlimited RLIMIT_AS. Upgrade, 45-minute stress, the full visual matrix, and the complete APT/evidence publication are not claimed. What changed: - Mission Control queues code, citation-backed report, and deterministic FFmpeg work against an approved project and records files, tests and changes for review. - Firebreak keeps MemoryMax at 3072 MiB and leaves RLIMIT_AS unlimited so Codex V8 sandbox VA reservation no longer SIGTRAPs. - Fire starts connected. Ice is chosen from the live Ice GRUB menu so sf.element=ice is present at install, and Ice stays offline. - For the first time in Shadowfetch Linux, choose Grok Bot at startup. A world-first Grok-on-Linux claim is not established. - Local AI / Buzz replacement is deferred. No model weights or cloud credentials are bundled. SHA-256: 137c1f29e206c0d0e26e524c8c34a7dfe43b24c1d1df29f85d6b15283bab67fc Size: 3980261376 bytes - 3.98 GB (3.71 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-4.0.0-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-4.0.0-amd64.iso.asc GitHub release: https://github.com/Shadowfetchapps/shadowfetch-linux/releases/tag/v4.0.0 Known limitation - Secure Boot is not Microsoft-signed; disable Secure Boot or follow the documented enrollment path. Known limitation - QXL virtual machines can report no DRM render node / gpu-verify-failed. That is the known VM graphics caveat, not an installed-desktop failure. Known limitation - The public APT snapshot still lists 3.5.0-1 first-party packages until the full evidence-bundle and APT publisher run. Known limitation - 3.5-to-4.0 upgrade, 45-minute concurrent stress, and the full 1366×768 / 1920×1080 visual matrix were not repeated on this image. Known limitation - Grok Bot needs an eligible account and internet. Sign-in screenshots do not prove authenticated cloud work. Known limitation - Archive.org holds a public copy of this ISO; the download button uses the established shadowfetch.com object once it is published there. https://www.shadowfetchlinux.org/changelog#v3-5-0 Shadowfetch Linux 3.5.0 «Umbra» - Fire and Ice Workbench 2026-08-27T00:00:00Z

Shadowfetch Linux 3.5.0 turns the Fire and Ice identity into an operating model for production work. Fire starts connected and throughput-oriented; Ice starts agent sessions with no network. Element Workbench creates four private, consequence-aware project environments for software, AI, operations, and creative work. Buzz remains the optional local-model workspace, while Codex, Claude Code, Grok Build, and Cursor Agent remain independent, verified, user-owned choices. No model, cloud credential, account, OpenClaw runtime, or Hermes runtime is embedded. The exact signed ISO passed fresh BIOS Fire and UEFI Ice installs, recovery and visual gates, and a 2,709-second concurrent stress run with zero failures. What changed: - Element Workbench: Software Studio, AI Lab, Production Ops, and Creative AI show disk, network, account, accelerator, and package consequences before one signed transaction creates a private project with agent rules, provenance, tests, runbooks, and receipts. - Fire and Ice are real execution postures, not only themes: Firebreak defaults Fire sessions to connected and Ice sessions to no network, keeps the system read-only, scopes writes to the selected project, strips known secret variables, and records a visible launch receipt. - Buzz remains the sole optional local-model workspace. Model selection and download happen only after confirmation; no model weights are bundled. Codex, Claude Code, Grok Build, and Cursor Agent are optional, digest-verified installers with native sign-in and no preloaded credential. - Phoenix and Fireproof wrap profile installation, updates, and recovery with visible checkpoints, simulation, explicit confirmation, failure receipts, and tested retry paths. - Release QA: 11 of 11 prepublication gates passed; fresh BIOS Fire and UEFI Ice installs booted from disk; all 15 required visual frames passed at 1366x768 and 1920x1080; 214 rootless-container cycles and 239 Workbench/health probes completed during 2,709 seconds of sustained load with zero failures. - Supply-chain evidence includes the detached ISO signature, a 3,350-component CycloneDX 1.5 SBOM, manifests for 16 binary packages from 14 signed sources, and a 58-input reproducible QA evidence bundle. SHA-256: 2af853b1f5dedfca17a7a63783f4c881e72e912f26082b10c07d45aafe57b995 Size: 3980310528 bytes - 3.98 GB (3.71 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-3.5.0-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-3.5.0-amd64.iso.asc GitHub release: https://github.com/Shadowfetchapps/shadowfetch-linux/releases/tag/v3.5.0 Known limitation - Secure Boot is not Microsoft-signed; disable Secure Boot or follow the documented enrollment path. Known limitation - The release VMs validated Plasma, GLX, Vulkan initialization, and exact layouts through Mesa llvmpipe without GPU passthrough. The RTX 5060 Ti host was healthy, but these VM runs do not claim physical NVIDIA, AMD, or Intel acceleration performance. Known limitation - No multi-gigabyte Buzz model download or inference run was repeated for 3.5.0. The release validates consent, loopback, digest, rootless-container, decline, and package-payload contracts; model acquisition remains an explicit post-install workflow. Known limitation - Archive.org is not yet a 3.5.0 mirror. Historical releases remain archived there, while the current signed image and verification artifacts are served from the primary download endpoint. https://www.shadowfetchlinux.org/changelog#v3-0-0 Shadowfetch Linux 3.0.0 «Umbra» - Backfire 2026-08-26T00:00:00Z

Shadowfetch Linux 3.0.0 «Backfire» makes Shadowfetch the agent-safe local-AI workstation: the first desktop OS where autonomous coding agents are contained, observed, and reversible by default. The new Fireline system runs any agent full-auto inside a bubblewrap sandbox with the entire system read-only and only your chosen project writable, cuts its network on request, strips your API keys from its environment, takes a checkpoint before every session, and lets you undo everything the agent did with one command. Four signed, dependency-free first-party MCP servers let an agent call a checkpoint before it touches anything, and AI Ignition recommends an Apache-2.0 open model that actually fits your GPU. Everything from 2.1.5 carries forward: Shadowfetch Guide and the private System Passport, Phoenix restore points, Fireproof simulate-first updates, the optional loopback-only Buzz workspace, signed ISO and APT chain, zero telemetry, and the full creative stack. What changed: - Firebreak (shadowfetch-firebreak): run any coding agent — Claude Code, Codex CLI, Cursor, Grok Build, Aider — in full-auto mode inside bubblewrap: system mounted read-only, only the chosen ~/Workspaces project writable, optional --net none, and known credential variables stripped from the agent environment by default. Every session gets a pre-run checkpoint, a session manifest, and a journald audit record. - Agent Checkpoints (shadowfetch-checkpoint): snapshot, diff, and undo one workspace — see exactly what an agent touched (content-hashed diff) and reverse everything it did with one command. Btrfs subvolume snapshots when available, portable archives otherwise; a safety point is taken before every undo. - Shadowfetch MCP suite (shadowfetch-mcp): four signed, dependency-free Model Context Protocol servers — passport (read-only, privacy-scrubbed self-check), phoenix (read-only restore points), checkpoint (snapshot/diff/undo one workspace), fs (scoped read-only files). One command prints ready-to-paste agent configuration. - AI Ignition (shadowfetch-ai-ignition): reads your GPU's VRAM and recommends an open model that actually fits, from an Apache-2.0-forward catalog (Qwen3, Devstral, gpt-oss) — CPU-only machines get a right-sized pick, never a 130 GB download. All model downloads remain consent-gated; nothing is bundled in the ISO. - shadowfetch-hardware: the offline firmware diagnoser — names the Debian package behind a silent Wi-Fi/Bluetooth failure and prints the exact fix, designed to work with no network at all. - Release QA: BIOS+UEFI boot, a clean UEFI Btrfs install that boots from disk, and a full stress run (all cores + memory + IO saturated) with the desktop staying responsive and zero failed services — plus the Fireline containment suite: sandbox escape attempts blocked, network cut verified, credential scrubbing verified, checkpoint undo byte-identical. SHA-256: 110b0d075e699a05a8a2f8f8dcd05f19454bc8ae09acd0745ca0d947db8c5e3c Size: 3967508480 bytes - 3.97 GB (3.69 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-3.0.0-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-3.0.0-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-3-0-0 Known limitation - Secure Boot: the ISO is unsigned. Enroll it yourself or disable Secure Boot; the steps are documented on the site. Known limitation - Firebreak's sandbox is bubblewrap + unprivileged user namespaces (verified at runtime by `shadowfetch-firebreak check`); Landlock fine-grained scoping is used where the kernel offers it and skipped cleanly where it does not. Known limitation - NVIDIA driver installation remains a consent-gated post-install step through Drivers (validated path, RTX 5060 Ti) — the automatic first-boot flow is planned for the 3.0.x train. Known limitation - AMD and Intel hardware-rendering performance is not claimed — no physical AMD or Intel renderer was available in release QA. https://www.shadowfetchlinux.org/changelog#v2-1-5 Shadowfetch Linux 2.1.5 «Umbra» - Fire Edition 2026-08-20T00:00:00Z

Shadowfetch Linux 2.1.5 makes the first Linux session more useful and more honest. The new Shadowfetch Guide and its private System Passport check graphics, networking, audio, firmware, memory, storage, recovery readiness, and local-AI capacity before you install, and remain the first Control Center section afterward. The Passport is deterministic, read-only, and on-device: host identity, account names, serials, PCI-slot, and filesystem identifiers are omitted from any report you choose to save as HTML or JSON. Buzz stays the single optional local-AI workspace, loopback-only by default, and is now guarded against the WebKitGTK DMA-BUF freeze on Plasma Wayland. Four independent coding agents are offered as unchecked, verified, user-owned options with no bundled credentials. The signed 2.1.4 upgrade path, Phoenix rollback on separate-/boot Btrfs, and BIOS and encrypted UEFI installs were all re-validated against the exact final ISO. What changed: - Shadowfetch Guide and System Passport: a deterministic, read-only check of graphics, networking, audio, firmware, memory, storage, recovery readiness, and local-AI capacity — available from the live Ignition screen and as the first Control Center section. Its public schema is allowlisted and omits host identity, account names, hardware serials, PCI-slot, and filesystem identifiers, and it can export a redacted report as HTML or JSON. - Buzz remains the one optional local-AI workspace, keeps its relay and compute listeners loopback-only by default, and is now guarded against the WebKitGTK DMA-BUF rendering freeze on Plasma Wayland while preserving the normal X11 path and explicit overrides. No open model is bundled; Buzz downloads one only after you confirm in Settings > Compute. - Optional coding agents at first-run setup — OpenAI Codex CLI, Claude Code, xAI Grok Build, and Cursor Agent — each unchecked by default, pinned and verified, installed for the desktop user, with all sign-in left to the tool itself and no credentials preloaded. - Verified in-place upgrade from 2.1.4 through the signed APT repository (sudo apt update && shadowfetch-update), exercised from a real 2.1.4 install with user files and Buzz state preserved and zero failed services. - Update safety and recovery re-validated: the Phoenix atomic-swap and separate-/boot Btrfs rollback defect found in VM stress was fixed and re-tested, interrupted and removal-seeking updates recover, and BIOS plus encrypted UEFI installs pass on both firmware paths. - New-generation NVIDIA workflow validated against a physical RTX 5060 Ti; renderer claims stay measured — AMD and Intel Mesa paths ship but are not performance-claimed without a physical card. SHA-256: 848f043e4d6f85c3607e7034ba911a1ce8b4a317674feebef8b07fcd8f531c24 Size: 3968471040 bytes - 3.97 GB (3.70 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-2.1.5-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-2.1.5-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-1-5 Known limitation - Secure Boot: the ISO is unsigned. You enroll it yourself or disable Secure Boot; the steps are documented on the site. Known limitation - In QA, a Buzz model download did not auto-resume after a mid-transfer network drop; a clean retry after removing the disposable incomplete cache object completed real inference. Known limitation - AMD and Intel hardware-rendering performance is not claimed — no physical AMD or Intel renderer was available in release QA. https://www.shadowfetch.com/linux/changelog#v2-1-4 Shadowfetch Linux 2.1.4 «Umbra» - Fire Edition 2026-08-10T00:00:00Z

Shadowfetch Linux 2.1.4 is a focused modernization of 2.1.3. It strengthens the graphics path for new-generation NVIDIA cards, verifies NVIDIA's Debian 13 keyring, uses nvidia-driver-assistant to select the supported branch, simulates every transaction, refuses removals, and takes Btrfs Phoenix snapshots around driver changes. The workflow was validated in release QA against a physical RTX 5060 Ti with a removal-free transaction. Full upgrades are simulated and re-verified before applying, the 2.1.3 upgrade uses a removal-free bridge, and BIOS and UEFI encrypted installs were validated on both firmware paths. What changed: - Local model downloads remain optional and consent-gated; nothing is fetched until the user confirms the choice in Settings > Compute. - Graphics: new-generation NVIDIA cards no longer dead-end; keyring-verified nvidia-driver-assistant workflow with simulate-first, --no-remove, and Phoenix snapshots — validated against a physical RTX 5060 Ti. - Update safety: upgrades are simulated and re-verified before applying, refuse low-disk/active-package-manager/bad-power, and take a Phoenix pre/post pair; an interrupted update was killed mid-transaction in QA and recovered cleanly. - Removal-free 2.1.3 upgrade bridge; the migration retires only the signed legacy local-AI package set and preserves personal workspaces and downloaded models. - BIOS and UEFI encrypted installs (LUKS2 on Btrfs) validated on both firmware paths, including repeated reboot/unlock cycles and GRUB snapshot-boot recovery. - Launcher cleanup: the Local AI section and Lost & Found no longer duplicate after optional software is installed. SHA-256: 81a906788ec48150d4a4527b4d9e7b09a974d3d577f1bd32ba3f333df8a1a86b Size: 3968475136 bytes - 3.97 GB (3.70 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://www.shadowfetch.com/linux/download/shadowfetch-2.1.4-amd64.iso Signature: https://www.shadowfetch.com/linux/download/shadowfetch-2.1.4-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-1-4 https://www.shadowfetch.com/linux/changelog#v2-1-3 Shadowfetch Linux 2.1.3 «Umbra» - Fire Edition 2026-08-02T00:00:00Z

Shadowfetch Linux 2.1.3 is a security and stability release. A critical Calamares installer bug is fixed: sf-remove-live-user ran pkill -KILL -u shadow inside the target chroot to clear a defensive obstacle, but a chroot does not isolate the process table, so the signal killed the live desktop session instead, aborting every install at job 23/43 and leaving a half-installed system that retained the live shadow account with its published password and NOPASSWD sudo -- the exact exposure the script exists to close. The script no longer signals any process; it edits the target account database files directly, then verifies every artefact is gone and fails loudly if not. This release also stops shadowfetch-firstboot.service from running during a live session, which previously set the hardware clock and fetched Flatpak themes on a visitor's machine before the firewall was even up. What changed: - Critical fix: the installer no longer kills the live session mid-install. - Fixed a separate install-blocking bug found during QEMU verification: the removepackages step referenced two nonexistent live-task-* packages, aborting every install. - The live shadow account is now removed by editing target account files directly, with a fail-loud verification of every artefact -- account, password hash, home directory, sudoers, and autologin. - First-boot setup no longer runs when booting the ISO live (was setting the wrong hardware clock and fetching Flatpak themes on visitors' machines before the firewall was up). - No feature changes from 2.1.2 Fire Edition -- Ember Mode, Firewatch, Phoenix Recovery, Ignition Setup, and Fireproof Updates are unchanged. SHA-256: 5f6a639b98e280c3fd46fc581ed899ec4ca861fb924bed266d4e13b9f4d0a2fd Size: 4007569408 bytes - 4.01 GB (3.73 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://archive.org/download/shadowfetch-linux-2-1-3/shadowfetch-2.1.3-amd64.iso Signature: https://archive.org/download/shadowfetch-linux-2-1-3/shadowfetch-2.1.3-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-1-3 https://www.shadowfetch.com/linux/changelog#v2-1-2 Shadowfetch Linux 2.1.2 «Umbra» - Fire Edition 2026-07-31T00:00:00Z

Shadowfetch Linux 2.1.2 «Fire Edition» — a Debian-testing derivative with KDE Plasma 6. A focused release built to run hotter, update safer, recover faster, and launch local AI with less friction, with zero telemetry and no cloud accounts. Shadowfetch Control Center gains three sections: Ember Mode holds the machine in a performance profile and always returns to Balanced on its own; Firewatch shows temperatures, resource pressure, and a plain-language heat-map of what each application and agent consumes, with live tokens per second from local models; Phoenix Recovery takes automatic Btrfs restore points before every update, driver install, and AI-stack change, restorable in one click. llama.cpp with the Vulkan backend is preinstalled and models arrive through one-click, checksummed downloads that are never bundled; an Agent Workspace template starts a model server bound to localhost only. Ignition Setup lets first boot choose Core, Creator, Developer, AI Workstation, or Full Flame, and Fireproof Updates analyses pending changes, snapshots first, and offers rollback if verification fails. This is also the first Shadowfetch release that fits a FAT32 USB stick, and the first on which an encrypted install boots. What changed: - Ember Mode: one-switch performance profile with crash-safe auto-return to Balanced. - Firewatch: hardware and local-AI activity monitor with a per-application heat-map and tokens/second. - Phoenix Recovery: automatic Btrfs restore points before risky changes, one-click restore. - Local AI on first boot: llama.cpp + Vulkan preinstalled; models are one-click, checksummed, never bundled; localhost-only Agent Workspace. - Ignition Setup: first-run system chooser (Core / Creator / Developer / AI Workstation / Full Flame). - Fireproof Updates: analyse, warn, snapshot, verify, and offer rollback. - Under 4 GiB: the first release that fits a FAT32 USB stick, via curation not feature loss. - Encrypted installs boot: three defects fixed and verified booting end to end. - Reproducible builds against a pinned snapshot.debian.org archive from a signature-verified base. SHA-256: 9374a233c1bd6f38bcbfad2bf041805568afb13ee455c482a7c7f68e7d0c56b1 Size: 4136423424 bytes - 4.14 GB (3.85 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://archive.org/download/shadowfetch-linux-2-1-2/shadowfetch-2.1.2-amd64.iso Signature: https://archive.org/download/shadowfetch-linux-2-1-2/shadowfetch-2.1.2-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-1-2 https://www.shadowfetch.com/linux/changelog#v2-1-1 Shadowfetch Linux 2.1.1 «Umbra» - Accurate 2026-07-26T00:00:00Z

Shadowfetch Linux 2.1.1 «Umbra» — a Debian-testing derivative with KDE Plasma 6. A correctness release: 2.1.0 shipped identifying itself as 2.0.1 in /etc/os-release, the login banner, the installer branding, the SDDM theme and every helper command. The build now stamps the version from the version it was invoked with, and the commands read it at run time rather than carrying a compiled-in constant. It also gives shadowfetch-welcome, the graphical first-boot wizard, the --help and --version it never had — previously asking it for a version opened the flow that installs Flathub applications and the local AI stack. Everything 2.1.0 delivered is unchanged: Intel Sound Open Firmware with the matching ALSA profiles, Cirrus amplifier firmware, and shadowfetch-facts. SHA-256: f5fe0f20dd24176839d0443f75ac4110587dff1a369785abdbe2121e213afdba Size: 4510564352 bytes - 4.51 GB (4.20 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://archive.org/download/shadowfetch-linux-2-1-1/shadowfetch-2.1.1-amd64.iso Signature: https://archive.org/download/shadowfetch-linux-2-1-1/shadowfetch-2.1.1-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-1-1 Known limitation - The ISO cannot be copied onto a FAT32-formatted USB stick. FAT32 caps a single file at 4 GiB (4,294,967,295 bytes). This ISO is 4,510,564,352 bytes — 215,597,057 bytes (206 MiB) over that limit — so a plain file copy to a FAT32 stick fails with "file too large". Write the ISO to the USB device with an image writer (balenaEtcher, KDE ISO Image Writer, GNOME Disks) or dd instead of copying it onto a mounted FAT32 filesystem. https://www.shadowfetch.com/linux/changelog#v2-1-0 Shadowfetch Linux 2.1.0 «Umbra» - Audible 2026-07-26T00:00:00Z

Shadowfetch Linux 2.1.0 «Umbra» — a Debian-testing derivative with KDE Plasma 6. This release ships Intel Sound Open Firmware and the matching ALSA use-case profiles, so laptops whose audio DSP previously loaded no firmware and played nothing now have working sound out of the box. It also adds shadowfetch-facts, a read-only hardware inventory that records the source of every reading, and gives all sixteen helper commands a --help that is safe to run. SHA-256: 71ebae6632579b0f5d890dae7fc458edc99d01d0b9c6f28d40cddfaddd6cbe30 Size: 4509110272 bytes - 4.51 GB (4.20 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://archive.org/download/shadowfetch-linux-2-1-0/shadowfetch-2.1.0-amd64.iso Signature: https://archive.org/download/shadowfetch-linux-2-1-0/shadowfetch-2.1.0-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-1-0 Known limitation - The ISO cannot be copied onto a FAT32-formatted USB stick. FAT32 caps a single file at 4 GiB (4,294,967,295 bytes). This ISO is 4,509,110,272 bytes — 214,142,977 bytes (204 MiB) over that limit — so a plain file copy to a FAT32 stick fails with "file too large". Write the ISO to the USB device with an image writer (balenaEtcher, KDE ISO Image Writer, GNOME Disks) or dd instead of copying it onto a mounted FAT32 filesystem. https://www.shadowfetch.com/linux/changelog#v2-0-1 Shadowfetch Linux 2.0.1 «Umbra» - Reachable 2026-07-24T00:00:00Z

Shadowfetch Linux 2.0.1 «Umbra» — a Debian-testing derivative with KDE Plasma 6. This release repairs apt on installed systems, makes the on-device AI tools reachable from the application menu, and adds virtual-machine guest integration. SHA-256: b5e7fbe232027958aac2296c2e623a56e20f85c61d444fd59a784c2edbdb04be Size: 4498606080 bytes - 4.50 GB (4.19 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://archive.org/download/shadowfetch-linux-2-0-1/shadowfetch-2.0.1-amd64.iso Signature: https://archive.org/download/shadowfetch-linux-2-0-1/shadowfetch-2.0.1-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-0-1 Known limitation - The ISO cannot be copied onto a FAT32-formatted USB stick. FAT32 caps a single file at 4 GiB (4,294,967,295 bytes). This ISO is 4,498,606,080 bytes — 203,638,785 bytes (194 MiB) over that limit, so it cannot be copied onto a FAT32-formatted USB stick; write it with dd or an imaging tool, or use an exFAT/NTFS stick. https://www.shadowfetch.com/linux/changelog#v2-0-0 Shadowfetch Linux 2.0.0 «Umbra» - Bedrock 2026-07-21T00:00:00Z

Shadowfetch Linux 2.0.0 «Umbra» — a Debian-testing derivative with KDE Plasma 6, built 2026-07-21. amd64 hybrid ISO, BIOS and UEFI, 4.49 GB (4.18 GiB).

Shadowfetch Linux 2.0.0 «Umbra» — a Debian-testing derivative with KDE Plasma 6, built 2026-07-21. amd64 hybrid ISO, BIOS and UEFI, 4.49 GB (4.18 GiB). SHA-256: 0cbf9b90a4e561c57167cbac55d6fc4d02efc3dbd12a9c97c5034afc9fe6c671 Size: 4486000640 bytes - 4.49 GB (4.18 GiB) Signing key: 8F13 CE15 35EE 1F4A 2916 A1F7 3C5C 900B 7BE8 0CA1 Download: https://archive.org/download/shadowfetch-linux-2-0-0/shadowfetch-2.0.0-amd64.iso Signature: https://archive.org/download/shadowfetch-linux-2-0-0/shadowfetch-2.0.0-amd64.iso.asc Archive record: https://archive.org/details/shadowfetch-linux-2-0-0 Known limitation - The ISO cannot be copied onto a FAT32-formatted USB stick. FAT32 caps a single file at 4 GiB (4,294,967,295 bytes). This ISO is 4,486,000,640 bytes — 191,033,345 bytes (182 MiB) over that limit — so a plain file copy to a FAT32 stick fails with "file too large". Write the ISO to the USB device with an image writer (balenaEtcher, KDE ISO Image Writer, GNOME Disks) or dd instead of copying it onto a mounted FAT32 filesystem.