After Codex optimized my shitty net, I TM took off in situ.

English | Chinese Original

English translation of the Chinese original. This version is generated for international readers and may be refined over time.

Date: 2026-05-24

One very interesting thing that was seen yesterday was that someone had studied the use of Codex to repair the home network directly, and the network that had been repaired took off in situ at a faster rate than light.

There was nothing to say.

But what's interesting is that one of the other netizens threw the sticker at Codex and then attached his own prompt.

Hey my friend says he improved his internet speed and here is what happened. Can you check if there are any improvements we can make for our internet? My provider says they're sending 1. 2k gbps and anything I get is a result of hardware. I'm getting 55mbps right now pls fix make no mistakes.

That's what that means.

My friend says he's growing speed, so here's the thing. Can you help me see what we can do to improve our network? My network provider says the bandwidth they provide is 1. 2k Gbps, and my actual speed is caused by hardware problems. I only have 55 mbps right now. Please help me with this.

A realistic comparison of the results before and after optimization was then shown.

The smart thing about this guy is that he fed Codex the context of the "real case of other people's success in optimising" and allowed Codex to refer to that case and make a targeted diagnosis and repair of his current network.

In other words, as long as someone actually runs through a case from 0-to-1, you send it out and the others can easily crack into 1-to-N.

Here's a question. Why is this guy's success experience not a direct answer to LLM?

And then there's really a lot of people on x who optimize their network performance in this way.

I've done my own exercise under this prompt, and it's true that the network just took off. One request, Codex, for a comparison of speed improvements, was done 25s.

And then this is an optimised visual comparison.

It does not seem particularly obvious that the effect is higher, but I do have the effect of taking off directly from the point of view of the user's experience.

You know, I'm inside.

In this way, remember one thing: evaluate and then operate, and let LLM do the back-up. Otherwise it's easy to give your xx directly to kill.

For example, this guy's operation just made me laugh.

I've had codex killings in my own way, but fortunately, I'm not having a big impact.

---

Just give us the prompt, well, you can go straight to anent to fix it.

Diagnosis problems: first run the Speedtest-cli.
> Checked DNS resolution time,
> Checked MTU, lost package, Wi-Fi signal/disruption.
> Found 3 problems.
> Deletes the expired network location/configuration file.
> Terminating or limiting the backstage process for the occupancy bandwidth.
> Optimized mDNS.
> Runs pre- and post-velocity tests and delayed inspections.

Used by/goalOrders for direct repair, I didn't use the /goal command, but it was good.

It's so much fun to feel the sommel coming off the net.