<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>OpenAI on Geek Vinkey</title>
    <link>https://www.mawenqian.com/en/tags/openai/</link>
    <description>Recent content in OpenAI on Geek Vinkey</description>
    <image>
      <title>Geek Vinkey</title>
      <url>https://www.mawenqian.com/images/papermod-cover.png</url>
      <link>https://www.mawenqian.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>MA Wenqian · mawenqian.com</copyright>
    <lastBuildDate>Sat, 03 Oct 2026 12:04:11 +0800</lastBuildDate>
    <atom:link href="https://www.mawenqian.com/en/tags/openai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ai-proxy-rules: Route Only OpenAI and Claude Through Your Proxy</title>
      <link>https://www.mawenqian.com/en/ai-proxy-rules/</link>
      <pubDate>Sat, 03 Oct 2026 11:00:00 +0800</pubDate>
      <guid>https://www.mawenqian.com/en/ai-proxy-rules/</guid>
      <description>&lt;p&gt;When you use Claude Code or call the OpenAI API from somewhere these services aren&amp;rsquo;t reachable directly, the easy fix is to switch your proxy to global mode. But then local sites, your company intranet and package downloads all take the detour too, so they get slower and sometimes break. The only traffic that actually needs the proxy is a few dozen AI domains.&lt;/p&gt;
&lt;p&gt;So I put together a rule set that covers just OpenAI and Claude. Those domains go through the proxy, and everything else stays direct.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
