{"id":1737,"date":"2026-09-15T09:05:04","date_gmt":"2026-09-15T01:05:04","guid":{"rendered":"https:\/\/blog.liu-qi.cn\/2026\/09\/15\/x-daily-2026-09-14\/"},"modified":"2026-09-15T09:05:18","modified_gmt":"2026-09-15T01:05:18","slug":"x-daily-2026-09-14","status":"publish","type":"post","link":"https:\/\/en.blog.liu-qi.cn\/2026\/09\/15\/x-daily-2026-09-14\/","title":{"rendered":"X Platform September 14 AI Brief | AI Safety Becomes Industry Consensus, Recursive Self-Improvement Enters R&D Roadmaps, Agent Capabilities Expand from Troubleshooting to Company Creation"},"content":{"rendered":"<h2 id=\"topic-8c666167d0\">Frontier AI&#8217;s &#8220;Slowdown&#8221; Shifts Toward Pre-Training Safety<\/h2>\n<p>OpenAI CEO Sam Altman stated that if frontier reinforcement learning training is expected to significantly enhance capabilities, OpenAI will now establish a clear safety case before training begins, elevating monitoring, runaway risk, and the collaborative development of safety standards to the level of industry cooperation. This &#8220;slowdown&#8221; is not a halt, but an acceptance of the additional costs brought by safety cases and monitoring; he also supports independent audits and a unified federal safety framework. Fran\u00e7ois Chollet, from another perspective, emphasizes that the excessive concentration of power in frontier AI itself is a risk, necessitating multiple independent providers, including open-source models.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@sama: <a href=\"https:\/\/x.com\/sama\/status\/2099348812305473766\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/sama\/status\/2099348812305473766<\/a><\/li>\n<li>@sama: <a href=\"https:\/\/x.com\/sama\/status\/2099352016988614852\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/sama\/status\/2099352016988614852<\/a><\/li>\n<li>@fchollet: <a href=\"https:\/\/x.com\/fchollet\/status\/2099230720753598471\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/fchollet\/status\/2099230720753598471<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-505fbe029e\">Zhipu Writes Recursive Self-Improvement into Next-Generation Model Roadmap<\/h2>\n<p>@MaxForAI relayed a Zhipu announcement stating the company completed approximately $5 billion in equity and debt financing, with about $2 billion from share placement and about $3 billion from convertible bonds; the disclosed use of funds includes the next-generation GLM foundational model, a fully self-training system, and large-scale training and inference infrastructure. More notably, Zhipu has written &#8220;Fully Self Training&#8221; and RSI (Recursive Self-Improvement) into its R&amp;D roadmap, with directions including model-generated data, Agent-generated training environments, and model participation in optimizing operators, kernels, scheduling, caching, and the Serving Stack. The above content is from the blogger&#8217;s summary of the announcement; the public post did not provide independent material proving that full RSI has already been achieved.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@MaxForAI: <a href=\"https:\/\/x.com\/MaxForAI\/status\/2099170395517780007\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/MaxForAI\/status\/2099170395517780007<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-0ac24bc1c5\">RSI is Being Deconstructed from a Slogan into a Five-Level Path from Runtime Adaptation to Meta-Improvement<\/h2>\n<p>@Gorden_Sun introduced a roadmap jointly published by Shanghai Jiao Tong University, Tsinghua University, ByteDance, Xiaohongshu, and Shanghai AI Lab, dividing self-improvement into L1 to L5: first executing according to human rules and accumulating results, then autonomously selecting improvement strategies, generating training tasks for weaknesses, accumulating skills and tools from real environments, and ultimately modifying the underlying methods of research and self-training. It provides a hierarchical framework for judging an Agent&#8217;s capability boundaries: being able to complete tasks, choose methods, self-train, adapt on-site, and improve its own mechanisms are not at the same level.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@Gorden_Sun: <a href=\"https:\/\/x.com\/Gorden_Sun\/status\/2099447356580348144\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/Gorden_Sun\/status\/2099447356580348144<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-d5c82f18d7\">Agents Begin to Handle Faults in a Closed Loop at Real Work Sites<\/h2>\n<p>@xiaohu relayed an Anthropic demonstration: after the payment interface error rate exceeded 2%, Claude Tag automatically pulled monitoring data in Slack, compared recent deployment and feature toggle records, and located the issue in about 15 minutes to a retry program lacking a concurrency limit, proposing two fixes. After the engineer confirmed &#8220;add limit, keep feature on,&#8221; it changed only 4 lines of code and continued monitoring for 10 minutes after deployment. The key to this case is not full delegation, but that the Agent can investigate the site, provide reviewable repair suggestions, while keeping merging and deployment in human hands.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@xiaohu: <a href=\"https:\/\/x.com\/xiaohu\/status\/2099414562516943276\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/xiaohu\/status\/2099414562516943276<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-d66de1a8c1\">Grok Bot Galaxy Turns &#8220;AI Building Companies&#8221; into Public Live Action<\/h2>\n<p>@poteto previewed that they, along with @mattyp and @roshan_s, will use only Grok Bot in a Grok Bot Galaxy livestream to start a new company from scratch, with a 3-day time limit; they later stated about 70,000 people registered for the livestream. Another practical test shared by Elon Musk shows Grok Bot would daily read user X bookmarks, launch Cursor Agent to create a demo, verify with screenshots or videos, then create a code branch and deploy a preview via Cloudflare. Both signals point toward a more specific Agent closed loop: sourcing from personal interests, automatically generating runnable prototypes, then handing them over for human review.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@poteto: <a href=\"https:\/\/x.com\/poteto\/status\/2099516697489314157\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/poteto\/status\/2099516697489314157<\/a><\/li>\n<li>@elonmusk: <a href=\"https:\/\/x.com\/elonmusk\/status\/2099505692805582871\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/elonmusk\/status\/2099505692805582871<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-22a1ca0cc2\">AI Video Production Shifts from &#8220;Card Drawing&#8221; to White Model and Reference-Driven Approaches<\/h2>\n<p>@derek_wall90176 believes the real difficulty in AI video is stably reproducing shots according to design, therefore suggesting first having an Agent call Blender to create a white model, determining character positions, action relationships, camera angles, and spatial structure, then handing it to MiniMax H3 for rendering, separating &#8220;structural determinism&#8221; and &#8220;visual imagination.&#8221; The Dunhuang group dance production workflow shared by @LufzzLiz also adopts a similar approach: using GPT-6 Astra for video understanding, image generation, and breakdown, then using H3 for omnidirectional reference generation of two video segments, requiring five adult characters to maintain identity consistency during occlusion, turns, and formation changes. The currently visible materials are creators&#8217; practical tests and tutorials, illustrating workflow and effects, not that models have solved all deformation issues.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@derek_wall90176: <a href=\"https:\/\/x.com\/derek_wall90176\/status\/2099321649518797090\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/derek_wall90176\/status\/2099321649518797090<\/a><\/li>\n<li>@LufzzLiz: <a href=\"https:\/\/x.com\/LufzzLiz\/status\/2099466952309903560\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/LufzzLiz\/status\/2099466952309903560<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-bbf18f1651\">Personal Knowledge Tools Merge Reading, AI Assistance, and Note-Taking into Mobile<\/h2>\n<p>The Obsidian e-book reader released by @vista8 supports EPUB, PDF, MOBI, AZW3, FB2, and other formats, and can call Codex, Claude Code, ZCode, Kimi, or DeepSeek APIs to assist reading; highlights and notes are written to Markdown files, the code is open-source, and a mobile adaptation tutorial was later added. The value of such tools is not just another reader, but integrating file rendering, cross-model assistance, and portable note accumulation into the same workflow, reducing dependence on the built-in models of a single reading platform.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@vista8: <a href=\"https:\/\/x.com\/vista8\/status\/2099433692083212573\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/vista8\/status\/2099433692083212573<\/a><\/li>\n<li>@vista8: <a href=\"https:\/\/x.com\/vista8\/status\/2099501969312485767\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/vista8\/status\/2099501969312485767<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-787d735ad2\">After Agent Scaling, Bottlenecks Shift to Runtime and Infrastructure<\/h2>\n<p>@steipete indicated that the next version or development channel will use folder cloning with APFS, Btrfs, XFS, and ReFS to make worktrees approximately 80% faster while saving disk space; after targeting teams, he also stated that the current environment runs about 80 sessions in parallel without significant pressure. On the other hand, @rauchg announced that Steren, the creator of Google Cloud Run, has joined Vercel to oversee Fluid computing products such as Functions, Containers, Sandbox, and Builds, and directly pointed out that Agents require new computing primitives. The visible change is that competition among Coding Agents is no longer just about model response quality, but also about code isolation, concurrent sessions, sandboxing, and build\/run environments.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@steipete: <a href=\"https:\/\/x.com\/steipete\/status\/2099197266636783989\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/steipete\/status\/2099197266636783989<\/a><\/li>\n<li>@steipete: <a href=\"https:\/\/x.com\/steipete\/status\/2099195896508617141\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/steipete\/status\/2099195896508617141<\/a><\/li>\n<li>@rauchg: <a href=\"https:\/\/x.com\/rauchg\/status\/2099514906366328902\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/rauchg\/status\/2099514906366328902<\/a><\/li>\n<\/ul>\n<h2 id=\"topic-0ea179fcce\">The Differentiation Point for AI Application Startups Shifts from Development Speed to Growth and Distribution<\/h2>\n<p>@lifesinger relayed an observation from a friend, stating that Silicon Valley AI application startups often scale their growth teams to a size similar to their product and R&amp;D teams because, with AI, product development might just be a matter of time; what truly creates a gap is traffic and growth. @bbkirstry, meanwhile, categorized AI monetization into seven types: saving time, improving efficiency, selling features, selling judgment, selling attention, selling connections, and selling assets. Both are analyses from bloggers rather than industry statistics, but together they provide an actionable insight: being able to build a product is just the starting point; the methods of capturing value\u2014such as services, subscriptions, content, consulting, and channels\u2014along with the ability to consistently reach users, are what determine whether commercial results can be achieved.<\/p>\n<p>Sources:<\/p>\n<ul>\n<li>@lifesinger: <a href=\"https:\/\/x.com\/lifesinger\/status\/2099458064038723779\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/lifesinger\/status\/2099458064038723779<\/a><\/li>\n<li>@bbkirstry: <a href=\"https:\/\/x.com\/bbkirstry\/status\/2099432847706857648\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/x.com\/bbkirstry\/status\/2099432847706857648<\/a><\/li>\n<\/ul>\n<p>Statistics: Scanned timeline count=476 Number of bloggers matched=57 Total matched tweets=331 Weighted tweet score=245.8 Original tweet count=130 Retweet count=87 Crawl attempt count=3 Boundary coverage status=tail_confidently_crossed_target_boundary<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Discussion focused on shifting AI safety strategies from post-training to pre-training, explicit planning for model recursive self-improvement, and Agents demonstrating closed-loop handling and creative capabilities in real work scenarios.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[19],"class_list":["post-1737","post","type-post","status-publish","format-standard","hentry","category-brief","tag-x--ai-"],"_links":{"self":[{"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/posts\/1737","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/comments?post=1737"}],"version-history":[{"count":1,"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/posts\/1737\/revisions"}],"predecessor-version":[{"id":1738,"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/posts\/1737\/revisions\/1738"}],"wp:attachment":[{"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/media?parent=1737"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/categories?post=1737"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/en.blog.liu-qi.cn\/index.php\/wp-json\/wp\/v2\/tags?post=1737"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}