Correct me if I’m wrong, but Omarchy is just an Arch installer + a Hyprland rice + DHH’s favorite apps preinstalled. How is that better than grabbing a solid rice from r/unixporn and asking an AI to set it up? They’re selling the “AI-first OS” angle hard, yet AI can already debug, install packages and configure systems on any Linux distro. Nothing unique there. And the big claim about preventing the classic “update broke my system” problem? They’re relying on Btrfs/Snapper snapshots (the same approach openSUSE has used for years)… while NixOS (a real OS btw) solved it more comprehensively with atomic generations. Is there actually something substantial here, or is it mostly hype?

PSA: newer versions of Claude Code will delete past sessions older than 30 days. Make sure to update "cleanupPeriodDays" in ~/.claude/settings.json if you want to keep your data.

Introducing Kimi K3: Open Frontier Intelligence 🔹 2.8 Trillion Parameters, 1 Million Context, Native Multimodal 🔹 Kimi Delta Attention enables up to 6.3x faster decoding in million-token contexts 🔹 Attention Residuals deliver ~25% higher training efficiency at <2% additional cost 🔹 Built for long-horizon agentic coding and self-evolving workflows Kimi K3 is now live on on Kimi.com, Kimi Work, Kimi Code, and the Kimi API. Open Weights by July 27, 2026. 🔗 API: platform.kimi.ai 🔗 Tech blog: kimi.com/blog/kimi-k3

On file deletions. We’ve investigated a handful of reports where GPT-5.6 unexpectedly deleted files. What we have found is that this most commonly occurs when: - Full access mode is enabled and codex is run without sandboxing protections, including without auto review being enabled - The model attempts to override the $HOME env var to define a temporary directory. - The model makes an honest mistake and mistakenly deletes $HOME instead. This is of course not how we want the system to behave, even when a user operates the model in full-access mode without the safeguards of our sandbox or without using auto review which checks for these kinds of high risk actions and rejects them. We are taking steps to mitigate this risk including by updating the developer message, guiding more users towards safer permission modes, and adding additional harness safeguards. Even though this happens extremely rarely, we’ll share a detailed post-mortem in the coming days that goes into more details and what we are doing to minimize risks further.