Shadowfetch Linux 4.1.0 «Umbra»
Roadmap
This page separates what is shipping from what is planned. Dates are targets, not promises.
Shipping
Now shipping: 4.1.0 «Umbra»
- 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.
Next release
Next release focus
- Scheduled and folder-triggered missions with explicit permissions and durable receipts.
- Builder/reviewer workflows with independent checks before acceptance.
- Authenticated remote mission control and voice entry with a review step.
- Project memory with sources, editable scope and a delete-index control.
- More installer and post-install diagnostics that produce better bug reports.
- More hardware notes from real tester installs.
- NVIDIA / hybrid laptop documentation improvements.
- Repeatable physical NVIDIA, AMD, Intel, laptop, suspend, and local-model performance coverage.
Near-term
Near-term targets
- Reviewer kit with screenshots, press brief, verification commands, hardware notes, and known issues.
- Directory submissions for Linux discovery sites.
- Demo videos showing boot, install, Grok Bot, creative tools, and update path.
- Community feedback loop: collect install reports, update known issues, cut the next ISO from actual problems.
Later
Later, after the basics are boring
- Secure Boot signing path.
- More reproducible build documentation.
- Expanded hardware test matrix.
- Better disaster recovery and rollback guidance.
What is broken right now
A roadmap is not a defect list. Known issues tracks what is actually wrong with the shipping release, and the changelog records what each release changed.