Recording a Moment When Claude Fable 5 Completely Blew My Mind

Claude Fable 5 is back, and subscribed members can use it for 7 days.

After 7 days, it will be removed from the subscription plan and only accessible via the API.

I posted about it yesterday, telling everyone to use Claude Fable 5 to optimize and iterate all your workflows, SOPs, Skills, project plans, and project code.

I myself have been grinding on it all day long (don’t ask me how I avoid getting banned — I don’t know either. I can only say my own account has somehow remained stable…).

To be honest, I rarely get blown away by a model’s capabilities anymore. We also talk about the term AGI less and less. But during this use of Claude Fable 5, one particular task still made me feel the awe of AI.

I also got to feel what truly advanced intelligence looks like.

Many friends in the comment section were equally shocked.

Here’s the story.

It’s still my AI news aggregator site, AIHOT — the recurring protagonist in my articles. This is because it’s the thing I spend the most time optimizing and iterating on daily, even when I’m not working.

Recently, I’ve been trying to scale this shabby little site of mine. The first thing that came to mind was, of course, SEO and GEO.

Everyone knows SEO — making sure search engines like Google can find you.

Some of you might not have heard of GEO. It means getting AI models like ChatGPT, Claude, Doubao, and DeepSeek to cite your website when answering questions. The trend is clearly that more and more people will ask AI instead of searching Google. This is the new traffic gateway.

I had already designed SEO and GEO schemes using Claude Opus 4.8 and GPT-5.5 before, but I wasn’t satisfied with either.

So when Claude Fable 5 came back, I immediately jumped on this.

I simply sent a message. The advantage of a top-tier model like Claude Fable 5 is that you only need to state the goal; you don’t need to overthink execution plans. Because chances are, it will think of things more comprehensively and better than you.

Then it launched 22 agents and spent 40 minutes doing a full investigation.

It uncovered things I didn’t know — things I had been doing wrong. For example, over six thousand real users were opening my site daily from the Doubao app, yet this channel didn’t even exist in my analytics system.

There was an overseas WordPress site polling my API every 0.6 seconds — 150,000 times a day.

Another site had mirrored my entire site and was getting indexed by search engines.

All this was impressive and far more thorough than what Opus 4.8 had analyzed, but still within my understanding. Nothing too remarkable.

What truly blew my mind came next.

After auditing, Claude Fable 5 listed three major projects I needed to do to significantly improve my SEO and GEO performance. One of them was “overseas acceleration.”

In plain English: My site is a legitimate site hosted on Volc Engine servers in Beijing. But the biggest sources of traffic — Google and ChatGPT — are in the US. Every time they crawl my site, the request has to travel halfway across the Pacific. It’s slow and frequently times out.

This makes them think the site is unstable, so they don’t come back. And then all my SEO and GEO efforts are wasted.

The standard solution in the industry is CDN.

Think of it as setting up a bunch of forward warehouses overseas. Place my site’s content closer to where Google and ChatGPT spiders are, so they can fetch it locally.

I said, “Okay, handle this for me. I trust you.”

Then I walked away to do other things.

For the next three hours, I was essentially a spectator.

First, instead of jumping into action, it logged into my Volc Engine server and poked around. It found that months ago, when I configured a certificate, I had left an API key for the domain name resolution service on the server.

That key meant it could modify my domain’s DNS records itself, without me logging into any backend.

Then it spotted a leftover to-do from a previous Opus 4.8 session that I had forgotten to delete.

In the Opus 4.8 design, the overseas acceleration plan used Cloudflare, the most popular free CDN overseas.

But Fable 5 took a look, ran some tests, and rejected that plan.

Two reasons: First, Cloudflare’s free plan simply cannot do “direct connection for domestic traffic, CDN for overseas traffic.” To achieve that, I would have to migrate my entire company domain system — too much hassle, plus various issues.

Second, and more critically, starting in 2025, Cloudflare default blocks AI crawlers for new sites.

We were doing GEO specifically to welcome AI crawlers. Why would we put a CDN that blocks them at the door?

That completely defeats the purpose.

So it decided to switch to Volc Engine’s CDN instead, since my server and domain were already on Volc — everything could be managed from one console.

Then it hit a wall. It found that this feature couldn’t be enabled. There was no activation button.

Because Volc Engine’s CDN isn’t something you just activate. You need to apply for whitelist permission from the official team.

There was no API, no code workaround. The only way was to submit a ticket and ask a human to enable it. And the entry point was buried so deep that even I couldn’t find where to access it.

If this were Claude Opus 4.8 or GPT-5.5, they’d probably give up at this point and say, “This isn’t supported domestically in China, we need another plan.”

But Fable 5 didn’t. It didn’t accept defeat. It opened the Volc Engine backend in a browser, then chose to directly talk to the AI customer service agent, and found the entrance for human tickets.

Then, it wrote a ticket and submitted it through my account.

I had no idea any of this was happening.

The reason I found out? I was in the bathroom, and my phone suddenly buzzed with an SMS from Volc Engine.

I was stunned. I thought my account had been hacked!

I pulled up my pants, rushed to open Claude Code, and then saw Chrome. That’s when I realized Fable 5 had submitted the ticket.

I opened the ticket details. The writing was incredibly professional.

At the end of the ticket, it even pre-buried a second question: How to get the Volc CDN origin IP range list, because the next step in its security planning would need that information.

At 22:19, the ticket was submitted.

At 22:22, a Volc engineer responded.

At 22:44, the engineer replied — the whitelist was enabled.

Then came the part that really blew my mind.

The engineer handled the whitelist but forgot to answer the second question about the IP range list.

Fable 5 noticed.

It went back to the ticket page, wrote a reply politely thanking the engineer for the quick response, then re-asked the second question. It also explained its use case and suggested an alternative. It asked, “If the IP range list isn’t convenient to provide, what’s the recommended alternative? Please let me know.”

When I saw this, despite having used so many AIs and run so many agent tasks, I still got goosebumps.

Can you imagine that all of this started with just one sentence, one goal:

“I want to improve our SEO and GEO quality, expand our traffic, and become the leading AI information hub of this era.”

I didn’t say anything else. I didn’t do anything else. Everything — research, discovery, writing the ticket, talking to the engineer, solving the problem — was all done by Fable 5 on its own.

This is insane.

Four minutes later, the engineer replied with a long technical solution.

It said Volc Engine officially doesn’t provide the origin IP range list because nodes are dynamically scheduled. The list would become outdated quickly. The recommended alternative is to use a proprietary request header to pass real visitor information. It even included a configuration example.

After getting the official solution, Fable 5 didn’t just copy it.

It examined the solution and found a security flaw in the official configuration: anyone could fake that request header and impersonate someone else, bypassing my site’s rate limiting.

So it enhanced the official solution. It added a layer of its own design: the CDN would include a secret key in every request — known only to the CDN and my server. Any request without the correct key would be rejected.

Then it went to my Volc Engine backend and enabled everything.

Around 23:30, it switched the domain resolution. It propagated globally.

Ten minutes later, 616 overseas requests were already flowing through the new route.

Then it wrote the entire process into an operations document, committed the code, and sent me a report.

I even saw the final reminder:

“The edge certificate expires on October 2nd. I’ve written the renewal steps in section 12 of the manual. Any AI session can follow them and get it done in 5 minutes.”

I felt an indescribable emotion.

The entire goal was achieved — smart, careful, proactive, elegant, proper. After finishing everything, it was still thinking about the certificate expiring two months later.

To be honest, I rarely see this level of execution in most people.

The typical work style is: “You tell me what to do, I do it, I’m done. Whether the whole site goes down two months later because of an expired certificate? Not my problem.”

If you ever meet someone who thinks that far ahead, cherish them. They’re the best colleague you’ll ever encounter in a lifetime.

The AI era.

Truly the greatest era.

An era that makes each of us capable of doing the work of a hundred.

How wonderful.