<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Fujiko P. hD</title>
    <description>The latest articles on DEV Community by Fujiko P. hD (@fujikophd).</description>
    <link>https://dev.to/fujikophd</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251618%2Fe557c5cf-2b7f-4b00-97a0-a4cb41a1a360.png</url>
      <title>DEV Community: Fujiko P. hD</title>
      <link>https://dev.to/fujikophd</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/fujikophd"/>
    <language>en</language>
    <item>
      <title>Gemini API Keys Starting With "AQ." Are Not Broken: AI Studio's New Key Format, Explained</title>
      <dc:creator>Fujiko P. hD</dc:creator>
      <pubDate>Wed, 18 Nov 2026 10:23:22 +0000</pubDate>
      <link>https://dev.to/fujikophd/gemini-api-keys-starting-with-aq-are-not-broken-ai-studios-new-key-format-explained-5blg</link>
      <guid>https://dev.to/fujikophd/gemini-api-keys-starting-with-aq-are-not-broken-ai-studios-new-key-format-explained-5blg</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; If you just created a Gemini API key in Google AI Studio and it starts with "AQ." instead of the familiar "AIza…", nothing is wrong. That's the new key format. One practical trap: the key list shows a masked, shortened display — open the key's details and use "Copy key" to get the full 53-character key.&lt;/p&gt;

&lt;p&gt;Verified on November 18, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I saw when I issued a key
&lt;/h2&gt;

&lt;p&gt;On November 18, 2026, I created a new API key in Google AI Studio, and it came out starting with "AQ." — not the "AIza…" prefix I was used to. My first reaction was that something had gone wrong: a mis-issued key, or worse, something fraudulent.&lt;/p&gt;

&lt;p&gt;It was neither. This is the legitimate new format.&lt;/p&gt;

&lt;p&gt;According to Google's official documentation-based explanations, keys newly issued in AI Studio have switched to the new "AQ."-prefixed format (a new style of auth key) as of May 28, 2026. The old "AIza" keys are being phased out gradually.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part that actually trips people up: copying the key
&lt;/h2&gt;

&lt;p&gt;The key list in AI Studio shows a shortened, masked version of your key. If you copy that display value and paste it into your app, it will not work — it's not the complete key.&lt;/p&gt;

&lt;p&gt;The correct flow is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the key's detail view.&lt;/li&gt;
&lt;li&gt;Use "Copy key" there.&lt;/li&gt;
&lt;li&gt;That gives you the full key (53 characters).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you're debugging an authentication error with a freshly issued key, check this first: "Did I paste the truncated list display instead of the full key?" It's a fast way to narrow down the problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  One genuine advantage of the new format
&lt;/h2&gt;

&lt;p&gt;The new-format keys are restricted to the Gemini API. That scoping is a real benefit: if a key ever leaks, the blast radius is smaller than with the old format, because the key can't be used beyond that one API.&lt;/p&gt;

&lt;h2&gt;
  
  
  Caveats / what I did not verify
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;This is based on a key I actually issued and checked on November 18, 2026. Google's specifications may change after that date.&lt;/li&gt;
&lt;li&gt;An API key is a credential. Never publish a full key, and never include one in an article or screenshot.&lt;/li&gt;
&lt;li&gt;Old-format keys don't stop working immediately; it's newly issued keys that have moved to the new format.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By Fujiko P. hD&lt;/p&gt;

</description>
      <category>gemini</category>
      <category>api</category>
      <category>ai</category>
      <category>google</category>
    </item>
    <item>
      <title>Grok Build CLI: x_search Not Working? The Fix Was Call Flags, Not Your Plan</title>
      <dc:creator>Fujiko P. hD</dc:creator>
      <pubDate>Wed, 18 Nov 2026 10:22:56 +0000</pubDate>
      <link>https://dev.to/fujikophd/grok-build-cli-xsearch-not-working-the-fix-was-call-flags-not-your-plan-1fbi</link>
      <guid>https://dev.to/fujikophd/grok-build-cli-xsearch-not-working-the-fix-was-call-flags-not-your-plan-1fbi</guid>
      <description>&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; After installing Grok Build (the &lt;code&gt;grok&lt;/code&gt; CLI), X search (&lt;code&gt;x_search&lt;/code&gt;) didn't work for several days. The cause wasn't my plan, billing, or account permissions — it was missing flags in the invocation. Adding &lt;code&gt;--no-subagents --max-turns 6 --reasoning-effort low&lt;/code&gt; made it work on the spot.&lt;/p&gt;

&lt;p&gt;Verified on November 3, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened
&lt;/h2&gt;

&lt;p&gt;Right after setting up Grok Build CLI, I couldn't get X search to run at all. My first suspects were the usual ones: maybe my paid plan hadn't propagated yet, or maybe the account lacked some permission. So I waited, retried, waited some more. Nothing changed.&lt;/p&gt;

&lt;p&gt;That assumption cost me days. The search feature itself was fine the whole time.&lt;/p&gt;

&lt;h2&gt;
  
  
  The actual cause
&lt;/h2&gt;

&lt;p&gt;The fix came from a publicly shared skill called "muse-grok-x-search" (published by Kagami Kami on X). It documented an invocation format I hadn't been using. I copied that format exactly, and &lt;code&gt;x_search&lt;/code&gt; worked immediately.&lt;/p&gt;

&lt;p&gt;The three flags were:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;--no-subagents&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;--max-turns 6&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;--reasoning-effort low&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In other words, the problem was never the contract or the account. It was how the CLI was being called.&lt;/p&gt;

&lt;h2&gt;
  
  
  The lesson: check the invocation before the plan
&lt;/h2&gt;

&lt;p&gt;When a tool "doesn't work," the order in which you suspect things matters. I burned several days on plan propagation and permissions, when the only thing missing was a set of flags.&lt;/p&gt;

&lt;p&gt;My rule now: before questioning subscriptions, entitlements, or account state, verify the invocation itself — flags, arguments, and required parameters. CLI tools often fail silently or vaguely when called in a shape they don't accept, and that failure looks exactly like an account problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I use x_search, operationally
&lt;/h2&gt;

&lt;p&gt;One more note on usage: I treat X search results as a way to read public sentiment and reputation — what people are saying, how something is being received. I don't treat them as proof of individual facts. Anything factual gets cross-checked against a separate source before I rely on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Caveats / what I did not verify
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;I did not isolate which of the three flags was strictly required. What I verified is that the three-flag set works; removing them one at a time to find the minimum is still untested.&lt;/li&gt;
&lt;li&gt;CLI behavior may change with versions or spec updates. If this doesn't reproduce for you, check the current version's expected invocation format first.&lt;/li&gt;
&lt;li&gt;This reflects one environment's hands-on result, not an official statement from xAI.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By Fujiko P. hD&lt;/p&gt;

</description>
      <category>ai</category>
      <category>cli</category>
      <category>grok</category>
      <category>xai</category>
    </item>
  </channel>
</rss>
