Skip to content

← English Topics

X English Hot Topics Brief

Date13 November 2026 · FridayWindow2026-11-11 08:55 to 2026-11-13 08:55CoverageComplete

Translation

English translation of the Chinese original.

Today's Priority Reads

  1. Expo launches cloud phone simulators for AI coding agents (corresponds to candidate 1). Worth doing now: the official post has about 1.234 million views and 1,088 likes, making it the highest-traction product launch this issue. It fills the link agents most lack when writing mobile apps: once the code is written, the agent itself installs it on a cloud iPhone or Android emulator, clicks through it, records the screen, and hands back the evidence. Best supplementary angle: the agent bottleneck is moving from "writing code" to "proving the code works," and this product is an example of "verification" becoming a standalone service. Format suggestion: a standalone original post that spells out cost and limits. The official page and press release are Verified, so drafting can start; actual performance was not tested this round.
  2. Fable 5.2 completes 41.3% of real outsourcing work on the Remote Labor Index (corresponds to candidate 2). Worth doing now: this is a rare score measured on real paid outsourcing projects, and a year ago the top of the leaderboard was only 2.5%. Best supplementary angle: make clear what this 41.3% is and is not: 240 Upwork projects, human review, excluding projects that require meeting clients or doing work in person, so it does not equal "41% of remote work has been replaced." Format suggestion: a standalone original post or a quote post. The leaderboard numbers have been checked against the Scale Labs page, so drafting can start.
  3. Replit Agent can now buy things and run ads for you (corresponds to candidate 3). Worth doing now: for the first time in a mainstream product, an agent formally gets permission to spend money. Best supplementary angle: look at how it prevents runaway spending: every purchase stops at the checkout page waiting for your approval, the command line and free browsing are switched off at payment time, and the approval check is written into the code rather than left to the model's judgment. This design is useful for comparing various "agents that spend money." Format suggestion: a standalone original post. The official blog is Verified, so drafting can start; the shopping feature is only available in the United States.

Candidate Topics

1. Expo Simulators: Give coding agents a cloud iPhone so they can check their own work

Original post and traction: @expo's official post, November 13 at 01:01, 1,088 likes, about 1.234 million views, 560 bookmarks. The explanation post from @aresotik, November 13 at 01:55, "Expo gave the AI agent its own phone," 170 likes, about 28,000 views. @heyDhavall, November 13 at 01:14, 42 likes, about 28,000 views.

Content and focus: the official post's claim is that coding agents now write mobile code faster than teams can review it. Expo Simulators are cloud iOS simulators and Android emulators: the agent installs the changes, clicks through them itself, brings back screen recordings, screenshots and logs, then hands them to a human for review. The explanation post focuses on "running iOS simulators without a Mac." The official post's views are far higher than its likes, which may point to promotion (Speculation).

Why it's worth doing / possible angles: it can be written as "the agent's next bottleneck is acceptance." For individual developers building apps with AI, the concrete benefit is that you don't have to sit at your computer clicking through it again and again; the agent can open several machines in the cloud at once to test, and attach a screen recording to every change. Also spell out the cost: billing is per minute, and a session keeps billing if you don't shut it down manually.

Timeliness and verification: within 24 hours. Verified: the Expo product page confirms support for Claude Code, Codex, Cursor and any agent that can run command-line commands, and the app does not have to be built with Expo; the press release confirms the launch on November 12, availability only on paid plans, iOS and Android both at $0.10 per minute, 60 minutes included per month on paid plans, and no AI model of its own; the pricing page states a single session lasts at most 115 minutes and the free tier is "coming soon." According to the Unite.AI report, the command-line tool is still experimental, physical devices are not offered, and recordings may drop frames. Performance was not tested this round.

2. Remote Labor Index: Fable 5.2 completes 41.3% of real outsourcing projects, while the best score a year ago was 2.5%

Original post and traction: @alliekmiller's original post, November 12 at 03:16, 218 likes, about 17,000 views, 60 bookmarks.

Content and focus: Allie K. Miller says she has not seen anyone discussing this score: 2.5% a year ago, 17.9% for Fable 5.1, 41.3% for Fable 5.2, "doubling time of roughly 3 months."

Why it's worth doing / possible angles: Chinese readers often see all kinds of benchmark scores, but this leaderboard's distinguishing feature is "real work, real money, human scoring," which is closer to what ordinary people care about: whether AI can take on jobs. Three points can be made: first, how it tests (the agent completes full projects inside a virtual computer with Blender, GIMP, Audacity and other software installed, and humans compare the results against deliverables from freelancers); second, the boundaries of the 41.3% (excluding projects that require communicating with clients or doing work in person); third, "doubling every three months" is an average, in reality it came in two big jumps, and the share can never double past 100%.

Timeliness and verification: 24–48 hours. Verified: the Scale Labs leaderboard confirms Fable 5.2 is first, with Opus 5.5 at 21.25%, GPT 6 Astra at 20.83% and Fable 5.1 at 17.92%, and states that the automation rate has no confidence interval. The verification article from CellCog gives 240 projects from 358 Upwork freelancers, a total price of about $144,000, an average human time of 28.9 hours, and the calculation that going from 2.5% to 41.3% means doubling on average in about 93 days, but unevenly; these details come from a third-party compilation and were not checked item by item against the original paper.

3. Replit Agent can buy things for you and run Google Ads: every purchase needs your nod

Original post and traction: @Replit's official post, November 13 at 01:22, 73 likes, about 24,000 views, 27 bookmarks. @amasad (Replit CEO), November 13 at 07:11, 83 likes, about 15,000 views.

Content and focus: the official post says "don't just build an idea, build a business": Replit Agent can now procure for your business through Stripe's Link and Visa, and can also run ads with Google Ads.

Why it's worth doing / possible angles: it can be written as "how to design an agent that spends money." According to the official blog: you say "find 50 boxes that fit this product, with shipping no more than $75," and the agent uses a browser sub-agent to pick items on merchant sites and fill the cart, then stops at the checkout page waiting for you to approve the total; at payment time the command line and free browsing are switched off, and the approval check is written into the code. On the ads side, the agent reads your site to write copy, produce images and suggest a daily budget, and ads go live only after you approve; because the app is its own work, it can also add conversion tracking along the way. This has real relevance for readers running small businesses who don't understand ad buying.

Timeliness and verification: within 24 hours. Verified: the official Replit blog confirms the flow and safety design described above, that the shopping feature is for Core and Pro users, launches in the United States first, supports only one-time purchases, and that the ads feature is for Pro users worldwide. Whether users in mainland China can use Link payments and run ads was not checked this round. Traction only reached the relaxed threshold, and it was selected because it belongs to the agent-practice category and is an official release from the party involved.

4. Primer: the Wharton team open-sources a system where a teacher describes the lesson and an agent generates a playable simulation

Original post and traction: @emollick's original post, November 13 at 06:03, 282 likes, about 19,000 views, 233 bookmarks.

Content and focus: Ethan Mollick's Wharton Generative AI Lab released Primer: a teacher explains what a lesson should teach, the system generates a scenario simulation students can play, and the paper, prompts and code are all open source. The bookmark count is higher than for an ordinary post, which suggests many people saved it for later use (Speculation).

Why it's worth doing / possible angles: for Chinese readers who do training or teach classes, this is very direct: it does not have AI generate questions directly, but first has an agent interview the teacher (what level the students are at, common misconceptions, how to grade), write a design document for the teacher to review, and only generate after the teacher approves. The student side has three roles: a tutor first helps you recall knowledge, a practice opponent drills with you or listens to you explain, and a coach finally gives feedback against the record. The flow of "interview first, produce a document, human approval, then generate" also applies to building any course with AI.

Timeliness and verification: within 24 hours. Verified: the official Primer page confirms it is open source, aimed at teachers rather than developers, with a division of labor between five build agents and three student-side agents, and that local or open-source models can be swapped in; the page states explicitly that it is an experimental prototype, has not been evaluated for learning outcomes in real classrooms, and has not undergone student privacy compliance review. The page also offers a prompt that lets an agent build Primer itself, and the official note warns it may run for several hours and incur model costs.

5. Fable 5.2 makes games and videos, but everyone is stuck on sound

Original post and traction: @rileybrown's original post, November 12 at 10:06, "Who has nailed sound design with Fable 5.2? That's the missing piece," 1,046 likes, about 137,000 views, 555 bookmarks. @pingouh's original post, November 12 at 05:55, 1,269 likes, about 49,000 views, 624 bookmarks.

Content and focus: pingouh used Fable 5.2 to build a small bipedal robotic creature driven entirely by code: first getting it to walk, run and sprint without falling in Three.js, then moving it into Unreal 5.8 and controlling it with a gamepad; he says there are no pre-recorded animations, everything is computed in real time, it was done in two days, and he admits himself that "the sound effects are bad and the scene is a bit random." Riley Brown's question nails this gap. Among the quote samples, someone recommends earshot, a GitHub repo that lets Claude "hear" video content (@mukudotgpt), and someone suggests breaking generation into a "sound cue sheet" and then aligning it to the picture (@findbestsol); these samples all have very low engagement.

Why it's worth doing / possible angles: in the past few days everyone has been talking about Fable 5.2 producing visuals, and the increment here is "where things get stuck after the visuals." It can be written for readers making videos or small games: the model can write code and tune visuals, but it cannot hear sound, so sound effects still depend on dedicated audio tools or human review. You can also collect readers' approaches and turn it into a call-for-submissions post.

Timeliness and verification: Riley's post is within 24 hours, pingouh's post is 24–48 hours, and it is a follow-up in the wave of Fable 5.2 work. pingouh's "two days" and "all computed in real time" are his own account; the earshot repo was not opened and checked this round.

6. Ethan Mollick's three-post run: RAG-style "chat with your documents" is already the past, and programming is the fastest-spreading counterexample for AI

Original post and traction: @emollick's original post, November 12 at 04:35, "Remember a year and a half ago when everyone said RAG-based 'chat with your documents' was the future of AI?", 1,572 likes, about 92,000 views. The second post, November 12 at 06:16, 606 likes, about 35,000 views. The third post, November 12 at 10:34, 356 likes, about 29,000 views.

Content and focus: the second post says people often claim new technology spreads slowly through industries, and programming is the counterexample: real working coding agents have existed for less than a year, and the profession is already transforming as a whole, faster than he expected from historical experience. The third post uses the power loom as an analogy: many mental jobs that could previously only be done by hand, and therefore could not be industrialized, may soon have to follow industrial logic too.

Why it's worth doing / possible angles: many companies in China are still running "knowledge base Q&A" projects. The first post can be used to discuss: now that long context and agents that can dig through files and look up material have appeared, which scenarios still suit the old approach of "chunk first, then retrieve, then answer" (analysis, not Mollick's own words). The second and third posts suit a combined piece on "which mental jobs will be industrialized first."

Timeliness and verification: the first two posts are 24–48 hours old, the third is within 24 hours. All three are personal opinions with no data attached; "RAG is obsolete" is his joke and must not be written up as an industry conclusion. Reply samples were not read this round.

7. Matt Pocock: "I just had the agent treat me as a tool call"

Original post and traction: @mattpocockuk's original post, November 12 at 08:28, the original line being "I just told the agent 'treat me as a tool call,' truly humiliating," 1,679 likes, about 102,000 views.

Content and focus: a one-line joke drew a lot of sympathy. The quote samples read are mostly joking, such as "the human tool has a call rate limit and returns 503 at lunchtime" (@dereklee1029); others think it may actually work better this way: clear input, structured output, no small talk (@pondtakesqueen). The samples all have very low engagement.

Why it's worth doing / possible angles: a small practical tip can be written: when the agent has questions, have it ask you the way it calls a tool, listing all the questions at once with options, and you just answer the options instead of going back and forth. The November 10 brief covered his suggestion to "explain why before having the agent ask you back," and this item can serve as a light opening on the same theme. Pocock himself did not explain how he set it up; that part is inference.

Timeliness and verification: 24–48 hours (just past 24 hours). The exact prompt wording needs to be tested yourself.

8. Follow-up: levelsio adds "video to 3D" to Interior AI in three hours, then adds one-click renders

Original post and traction: @levelsio's original post, November 12 at 09:34, 235 likes, about 43,000 views, 169 bookmarks. The "Render" button post, November 12 at 22:00, 109 likes, about 33,000 views. The style preview post, November 13 at 01:07, 64 likes, about 29,000 views.

Content and focus: he says the feature went live three hours later: upload a walkthrough video of a living room or a whole floor, and Interior AI turns it into a walkable 3D space where you can paint walls, move furniture and produce a floor plan; it uses headless Blender that he set up himself on a VPS. Then he added a "Render" button that turns a 3D view into a photo-realistic render in about 20 seconds, and also added a style preview menu. He says the next step is to connect 3D walkthroughs to video models to make videos.

Why it's worth doing / possible angles: yesterday's brief covered his announcing the upgrade, and today's increment is the pace and approach of "one person shipping three features in one evening": running the heavy work on his own cheap server while AI writes the code. It suits showing readers who want to build small products how fast feature iteration can be.

Timeliness and verification: within 24 hours, and a follow-up to yesterday's candidate 12. The features come from his demo and his own account and were not tested this round; "three hours" and "20 seconds" are both his claims.

9. Follow-up: NVIDIA GR00T 2 completes a whole chemistry experiment with no cuts and no speedup

Original post and traction: @DrJimFan's original post, November 11 at 23:32, 723 likes, about 49,000 views, 191 bookmarks. The retelling by @RoundtableSpace, November 13 at 03:45, about 50,000 views, 18 likes.

Content and focus: Jim Fan says the video is autonomous operation, uncut, at 1x speed: GR00T 2 controls real dexterous hands to complete a chemistry experiment from start to finish, and cleans up after itself. He says this is the first episode of a new series, and that real-time robot videos will keep coming, with no "4x" or "8x" speed labels hidden in the corner.

Why it's worth doing / possible angles: the daily brief on November 10 covered the GR00T 2 release, and the increment here is the way it is demonstrated. You can give readers a small piece of common sense for watching robot videos: first check whether there is a speed label in the corner, whether it is cut, and whether it is teleoperated, then judge the capability.

Timeliness and verification: 24–48 hours, a follow-up. "Autonomous, uncut, 1x speed" is Jim Fan's own claim; it was not independently verified this round, and the specific content and success rate of the experiment were not seen.

10. Value watch: Simon Willison says Gemini 4 pricing doesn't make sense and Hydrogen is only 25% cheaper

Original post and traction: @simonw's original post, November 13 at 08:36, 34 likes, about 3,692 views.

Content and focus: he points out that Carbon and Argon are the same price, and the "cheap" Hydrogen is only 25% below them; Carbon and Argon double in price from December 1, at which point Hydrogen will only then be about 75% cheaper. He also had Hydrogen draw "a pelican riding a bicycle" and says the quality is clearly worse.

Why it's worth doing / possible angles: the daily brief covered Hydrogen's official pricing, and the increment here is "how to compare prices." You can remind readers using the Gemini API that prices differ before and after December 1, so they need to recalculate at the price in effect then; Hydrogen is a free-tier model and will also be used in the AI features of Google Search. When collected, the post was less than half an hour old and had low traction, and it was included as a Value watch because the information is practical.

Timeliness and verification: within 24 hours. Verified: Simon Willison's blog lists a price table: Carbon and Argon are $2 per million input tokens and $10 output through November 30, and $4 and $20 from December 1; Hydrogen is $1.50 and $7.50; he also writes that Claude Haiku 5.5 and GPT-6 Luna are both $0.10 and $0.50. The price table is his own compilation and was not checked against Google's official pricing page this round. The pelican test is his personal fun test, not a formal evaluation.

This issue has 10 items in total; the remaining candidates lacked sufficient traction or information, so it did not reach 20 items.