https://blog.margrop.net/en/tag/electron/ Recent content in Electron on Margrop Blog Hugo -- gohugo.io en-US Wed, 25 Mar 2026 10:00:00 +0800 https://blog.margrop.net/en/post/macos-electron-app-proxy-wrapper-for-antigravity-and-claude/ Wed, 25 Mar 2026 10:00:00 +0800 https://blog.margrop.net/en/post/macos-electron-app-proxy-wrapper-for-antigravity-and-claude/ <blockquote> <p><strong>Before You Start</strong> This post documents a pattern that has already been validated in a real macOS environment: <strong>do not patch the original application bundle, and do not publish your real proxy endpoint. Instead, place a tiny wrapper app in front of the original Electron application.</strong> That wrapper becomes the stable place where proxy settings, launch flags, and Node-side bootstrap logic live.</p> </blockquote> <p>When people first hit this problem, the instinct is usually to edit <code>/Applications/Claude.app</code> or <code>/Applications/Antigravity.app</code> directly. That can work once, but it is a poor long-term operational choice for three reasons:</p> <ol> <li>You may break code signing behavior and make future launches or permission prompts more fragile.</li> <li>Auto-updates can overwrite your local modifications at any time.</li> <li>If you hardcode a real proxy endpoint into the app bundle, screenshots, scripts, or a public post, you can leak private infrastructure details that never needed to be exposed.</li> </ol> <p>The approach that proved much more stable was:</p> <ol> <li>Leave the original <code>Claude.app</code> and <code>Antigravity.app</code> untouched.</li> <li>Create <code>Claude (Proxy).app</code> and <code>Antigravity (Proxy).app</code> under <code>~/Applications</code>.</li> <li>Let each wrapper app do only three things: load a private <code>proxy.env</code>, export upper/lower-case proxy variables, and launch the original Electron binary with <code>--proxy-server</code>.</li> <li>If the target app also uses Node/undici <code>fetch</code>, inject a very small <code>NODE_OPTIONS=--require=...</code> bootstrap so Node-side requests follow the same proxy path.</li> </ol> <p>All proxy endpoints in this article are intentionally redacted and replaced with placeholders such as:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>http://127.0.0.1:PORT </span></span></code></pre></div><p>Replace that value with your own local proxy entrypoint. <strong>Do not publish real proxy hosts, internal IP addresses, usernames, passwords, tokens, or internal domains in a public article, repository, or screenshot.</strong></p>