<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Launchctl on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/launchctl/</link>
    <description>Recent content in Launchctl on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sat, 30 May 2026 09:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/launchctl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Python App in macOS LaunchAgent Can&#39;t Reach the Internet? Here&#39;s the httpx Proxy Trap You Need to Know</title>
      <link>https://blog.margrop.net/en/post/macos-launchagent-python-httpx-proxy-no-route-to-host/</link>
      <pubDate>Sat, 30 May 2026 09:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/macos-launchagent-python-httpx-proxy-no-route-to-host/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;When a Python application using httpx with &lt;code&gt;trust_env=True&lt;/code&gt; runs inside a macOS LaunchAgent, it silently picks up the system proxy settings from &lt;code&gt;scutil --proxy&lt;/code&gt;. But the LaunchAgent process may not be able to reach that proxy server at all — resulting in &lt;code&gt;All connection attempts failed&lt;/code&gt; or &lt;code&gt;No route to host&lt;/code&gt; errors.&lt;/p&gt;&#xA;&lt;p&gt;The fix is one line: add &lt;code&gt;NO_PROXY=*&lt;/code&gt; to the LaunchAgent&amp;rsquo;s plist &lt;code&gt;EnvironmentVariables&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This article documents the full debugging journey: from discovering that my AI Agent&amp;rsquo;s WeChat Enterprise (WeCom) messages weren&amp;rsquo;t being replied to, through methodical proxy troubleshooting, to finally pinning down the root cause — macOS system proxy + LaunchAgent network isolation. We&amp;rsquo;ll dive deep into Python httpx source code, macOS proxy architecture, and the many gotchas of LaunchAgent runtime environments.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Install Frp client on Mac and use remote desktop</title>
      <link>https://blog.margrop.net/en/post/mac-frpc-install-for-remote-desktop-problem/</link>
      <pubDate>Mon, 18 Jan 2021 13:28:26 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/mac-frpc-install-for-remote-desktop-problem/</guid>
      <description>You can install it with Homebrew.&#xA;The following section shows the old manual extraction method. Keep reading if you want that approach.&#xA;brew install frpc vi /usr/local/etc/frp/frpc.ini brew services start frpc Download the Darwin package from FRP releases and unzip it omitted Copy the executable sudo mv ~/Downloads/frp_0.34.3_darwin_amd64/frpc /usr/local/bin/ Add the frpc configuration file Adjust server_addr, server_port, and remote_port as needed. Edit the auto-start configuration Commands related to auto-start sudo su cat&amp;gt;/etc/frpc.</description>
    </item>
  </channel>
</rss>
