<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>MacOS 26 on Margrop Blog</title>
		<link>https://blog.margrop.net/en/tag/macos-26/</link>
		<description>Recent content in MacOS 26 on Margrop Blog</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 30 Jun 2026 09:30:00 +0800</lastBuildDate>
		
			<atom:link href="https://blog.margrop.net/en/tag/macos-26/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Stop Treating Passkeys as SSH Passwords: The Right Way to Use SSH Keys and Phone/Desktop Passkeys</title>
				<link>https://blog.margrop.net/en/post/ssh-passwordless-login-passkeys-correct-use/</link>
				<pubDate>Tue, 30 Jun 2026 09:30:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/ssh-passwordless-login-passkeys-correct-use/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;SSH passwordless login and passkeys on phones, Macs, and Windows PCs both use the public-key idea, but they are not the same tool. SSH keys are for logging in to servers, Git remotes, jump boxes, and automation endpoints. Passkeys are for signing in to websites, apps, and account systems. They are like two modern key rings: one opens the machine-room door, the other opens your online account door. The cryptographic idea is related, but the locks are different.&lt;/p&gt;&#xA;&lt;p&gt;The practical rule is simple: generate a separate SSH key on each client device, keep the private key only on that device or inside a hardware security key, and put only the public key on the server. Verify public-key login before disabling password login. Use passkeys through iPhone, Android, macOS 26, Windows 11, system password managers, or hardware security keys for website and app sign-in. Do not try to paste a phone passkey into &lt;code&gt;authorized_keys&lt;/code&gt;. This post includes one-click scripts for Windows 11, Ubuntu 26.04, and macOS 26, plus a manual automation path and an Agent-driven configuration path. The examples do not depend on any third-party service and do not contain real internal addresses, full computer names, private domains, or secrets.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>Stop Clicking Update One App at a Time: Let an Agent Upgrade Common Software on Windows 11, Ubuntu 26.04, and macOS 26</title>
				<link>https://blog.margrop.net/en/post/agent-upgrade-common-software-windows11-ubuntu2604-macos26/</link>
				<pubDate>Sun, 28 Jun 2026 08:58:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/agent-upgrade-common-software-windows11-ubuntu2604-macos26/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Updating everyday software is painful not because the commands are impossible, but because the update sources are scattered across several worlds. Windows 11 has WinGet, Microsoft Store, and vendor installers. Ubuntu 26.04 has apt, snap, flatpak, and service restarts. macOS 26 has Software Update, App Store, Homebrew, and applications downloaded outside the store. A human can easily miss something. An AI Agent can help, but only if you give it boundaries.&lt;/p&gt;&#xA;&lt;p&gt;My recommendation is to treat the Agent as an update operator: inventory first, dry-run second, execute third, verify last. This article provides three one-command scripts for Windows 11, Ubuntu 26.04, and macOS 26. They do not depend on third-party update assistants or cloud services. They call only built-in update tools and package managers already installed and configured on the machine. The examples contain no real private address, full computer name, private domain, token, or key.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>Is Your Computer Always Full? Use an AI Agent to Safely Clean Junk Files on Windows 11, Ubuntu 26.04, and macOS 26</title>
				<link>https://blog.margrop.net/en/post/ai-agent-cleanup-windows11-ubuntu2604-macos26/</link>
				<pubDate>Sun, 28 Jun 2026 07:15:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/ai-agent-cleanup-windows11-ubuntu2604-macos26/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Junk cleanup is risky not because it is hard to delete files, but because it is easy to delete too much. On Windows 11, Ubuntu 26.04, and macOS 26, the safe cleanup targets are usually temporary directories, package caches, old logs, recycle bin or trash contents, and files that can be regenerated. A cleanup script should not casually touch documents, photos, browser profiles, keys, certificates, virtual machine images, or application data.&lt;/p&gt;&#xA;&lt;p&gt;This article gives you two paths: &lt;strong&gt;manual automation&lt;/strong&gt;, where you run the scripts yourself, inspect the dry-run output, and then explicitly enable deletion; and &lt;strong&gt;Agent-driven automation&lt;/strong&gt;, where Codex, Claude, OpenClaw, HermesAgent, or another AI Agent performs the same scan, review, execution, and verification flow for you. The three scripts cover Windows 11, Ubuntu 26.04, and macOS 26. They do not depend on third-party services, do not download cleanup utilities, and do not contain real private addresses, computer names, private domains, or secrets.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>Chrome Ate 4GB of Disk Space? Delete the Local AI Model and Stop It Coming Back</title>
				<link>https://blog.margrop.net/en/post/chrome-disable-local-ai-model-4gb/</link>
				<pubDate>Sat, 27 Jun 2026 23:00:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/chrome-disable-local-ai-model-4gb/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Some Google Chrome installations now download several gigabytes of local generative AI model data in the background. This is usually not malware and not a broken cache. It is Chrome preparing on-device AI models for browser and web features. Deleting the folder only frees disk space temporarily. The durable fix is to &lt;strong&gt;disable the local GenAI foundational model download with Chrome policy, then remove the already downloaded model folders&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This guide covers Windows 11, Ubuntu 26.04, and macOS 26. It includes one-click scripts, manual steps, and an agent prompt you can hand to Codex, Claude, OpenClaw, Gemini CLI, or another local operator. The scripts use native OS policy mechanisms and Chrome&amp;rsquo;s documented policy. They do not depend on third-party services and do not include real IP addresses, hostnames, internal domains, or secrets.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
			<item>
				<title>macOS 26 Boot Daemons: Put frp and EasyTier in LaunchDaemons, Not Login Items</title>
				<link>https://blog.margrop.net/en/post/macos-26-launchdaemon-boot-service-frp-easytier/</link>
				<pubDate>Sat, 27 Jun 2026 17:12:00 +0800</pubDate>
				<guid>https://blog.margrop.net/en/post/macos-26-launchdaemon-boot-service-frp-easytier/</guid>
				<description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Short version&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If you want &lt;code&gt;frp&lt;/code&gt;, &lt;code&gt;EasyTier&lt;/code&gt;, a sync agent, a collector, a bot, or a proxy daemon to start automatically on macOS 26, the key is not “where can I hide this command?” The key is “which native service manager owns its lifecycle?” This article is about unattended background services, not ordinary desktop login apps.&lt;/p&gt;&#xA;&lt;p&gt;On macOS 26, a daemon that must start before user login belongs in /Library/LaunchDaemons. Login items and LaunchAgents are tools opened after a person enters the room. LaunchDaemons are more like the building&amp;rsquo;s elevator or water pump: they should run as the machine comes up.&lt;/p&gt;&#xA;&lt;p&gt;I will show two paths: &lt;strong&gt;manual configuration&lt;/strong&gt;, for understanding every moving part, and &lt;strong&gt;agent / one-click automation&lt;/strong&gt;, for cases where you already know where the binary and config file live. The scripts are self-contained, use built-in OS mechanisms, do not download third-party wrappers, and do not include real addresses, hostnames, private domains, or secrets.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
			</item>
	</channel>
</rss>
