雪踏乌云's banner
雪踏乌云's profile picture

雪踏乌云

@Pluvio9yte44,649 subscribers

📌 聚焦:AI & Vibe coding & Prompt & Agent 🌏 在做:创业 | Web出海 | Web3 🌊 持续分享AI编程、AI工具、出海干货和创业经验

Shorts

将最近全网爆火的分手片段复刻了一下。 同样的提示词,来看 Minimax H3 和 Seedance 2.5 的实测对比,差异这么大啊 Seedance2.5明显人物对微表情控制的更好。

将最近全网爆火的分手片段复刻了一下。 同样的提示词,来看 Minimax H3 和 Seedance 2.5 的实测对比,差异这么大啊 Seedance2.5明显人物对微表情控制的更好。

37,315 Aufrufe

Codex 大更新 —— Chrome 内置最完全功能应用解析 1. 内置浏览器 + Chrome Cookie 一键导入 现在导入了 Cookie 之后,能够把抖音、小红书、推特的账号 Cookie 都导入。现在打开,直接就是登录状态。 2. 开发者模式 可以查 DOM、Console、Network 请求、性能等。 比如说,原来我开发网站如果遇到性能问题,让它优化就会麻烦一些。现在直接用内置的浏览器,速度非常快,这个优化速度。 下面是一些应用场景 内容创作与研究 让 Codex 带着你的账号去小红书、微博、知乎等平台“逛”,找选题、分析爆款、抓用户反馈。 开发者调试 开启开发者模式后,Codex 能实时 inspect 页面: 快速定位 console error、网络请求异常。 分析 DOM 结构、调试已登录态的内部工具。 提示词示例:“开启开发者模式,打开这个页面,检查 Network 请求里和用户数据相关的接口,并把 console 里的 error 列出来。” 测试需要真实登录态的 Web 应用等

Codex 大更新 —— Chrome 内置最完全功能应用解析 1. 内置浏览器 + Chrome Cookie 一键导入 现在导入了 Cookie 之后,能够把抖音、小红书、推特的账号 Cookie 都导入。现在打开,直接就是登录状态。 2. 开发者模式 可以查 DOM、Console、Network 请求、性能等。 比如说,原来我开发网站如果遇到性能问题,让它优化就会麻烦一些。现在直接用内置的浏览器,速度非常快,这个优化速度。 下面是一些应用场景 内容创作与研究 让 Codex 带着你的账号去小红书、微博、知乎等平台“逛”,找选题、分析爆款、抓用户反馈。 开发者调试 开启开发者模式后,Codex 能实时 inspect 页面: 快速定位 console error、网络请求异常。 分析 DOM 结构、调试已登录态的内部工具。 提示词示例:“开启开发者模式,打开这个页面,检查 Network 请求里和用户数据相关的接口,并把 console 里的 error 列出来。” 测试需要真实登录态的 Web 应用等

158,697 Aufrufe

AI Is Moving Beyond “Generating Videos” — Toward “Generating Worlds” Over the past two years, AI video models have advanced at an astonishing pace. From Runway and Pika to Sora and Veo, AI-generated videos have become increasingly realistic and more consistent with the physical laws of the real world. Many people believe the next objective is simply to generate videos that are longer, sharper, and more lifelike. But if we take a step back, we can see that the real transformation is not happening in video itself. It is happening in world models. What Is a World Model? In 1943, psychologist Kenneth Craik proposed an idea that would influence artificial intelligence research for decades. He argued that the human brain does not merely react to the outside world. Instead, it maintains an internal model of how the world works. Because we have this internal model, we can predict the outcome of an action before we actually take it. Before crossing a road, we estimate whether a car will pass by. Before catching a ball, we predict its trajectory. These abilities come from continuously simulating the world in our minds, rather than relying entirely on trial and error. This idea later became known by a more formal term: World Model. A world model does not describe a single image or a fixed video clip. It is an internal representation capable of continuously simulating the rules and dynamics of the real world. Why Is AI Research Turning Toward World Models? Because predicting “what comes next” is becoming increasingly central to how AI systems work. Language models predict the next token. Image models predict the next step in the denoising process. Video models predict the next frame. A world model, however, attempts to predict something broader: What should the world look like in the next moment? In 2018, David Ha and Jürgen Schmidhuber proposed in their paper World Models that an intelligent agent could first learn a model of the world, and then use that internal model to plan its actions. The Dreamer series later demonstrated that many complex tasks could be learned by training agents inside an “imagined world.” At the same time, the development of video models such as Sora and Veo led researchers to another realization: A model capable of continuously generating video has already learned, at least implicitly, many of the rules governing the real world. As a result, these two research directions have gradually begun to converge. But Video Is Not Yet a World This is where the distinction is often misunderstood. For a world model to support meaningful real-time interaction, it must solve several critical problems. Most video models today are essentially answering one question: What should the next frame look like? A true world model needs to answer much more: What happens if I take one step forward? If I walk behind a building and then return, will the building still be there? If I suddenly change the camera angle, will the entire space remain consistent? If I enter a command such as: “Summon a dragon.” Will the world respond immediately? In other words, a world model must do more than generate content. It must understand space. It must understand time. It must understand causality. And it must understand interaction. Moving from watching to participating is where the real difficulty of world models begins. World Models Are Entering the Interactive Era One of the latest attempts in this direction is Alaya World, recently open-sourced by Alaya World, or Alaya Lab. Instead of generating a fixed video clip, it generates a world that users can explore in real time. Users can begin with text, an image, or a video, enter the generated scene, move freely through it, and introduce new prompts at any moment during generation. The world responds immediately. According to the publicly released information, Alaya World provides: Real-time streaming generation at 720p and 24 FPS Stable continuous exploration for more than one minute The ability to switch prompts and trigger skills or events during generation Model weights and inference code released under the Apache 2.0 License Training code and datasets planned for future release What makes these capabilities important is not simply the technical specifications. It is that the generated “world” can now support continuous interaction. The official demo shows that users can genuinely control, transform, and explore the generated environment. AI Is Evolving From a Tool Into an Environment Over the past few years, most discussions around AI have focused on content generation. Generating text. Generating images. Generating videos. But world models raise a fundamentally different question: Can AI generate an environment that people can inhabit, explore, and continuously evolve? If the answer is yes, the impact will extend far beyond video generation. Game development, robotics training, embodied intelligence, digital twins, virtual production, and many other fields could be transformed by the development of world models. World models are still at a very early stage. Yet from Craik’s proposal of an internal mental model more than eighty years ago to the emergence of today’s interactive world-generation systems, a clear evolutionary path is beginning to take shape. Perhaps what AI is ultimately learning has never been limited to images, videos, or language. Perhaps it is learning the world itself. References GitHub: Technical Report:

AI Is Moving Beyond “Generating Videos” — Toward “Generating Worlds” Over the past two years, AI video models have advanced at an astonishing pace. From Runway and Pika to Sora and Veo, AI-generated videos have become increasingly realistic and more consistent with the physical laws of the real world. Many people believe the next objective is simply to generate videos that are longer, sharper, and more lifelike. But if we take a step back, we can see that the real transformation is not happening in video itself. It is happening in world models. What Is a World Model? In 1943, psychologist Kenneth Craik proposed an idea that would influence artificial intelligence research for decades. He argued that the human brain does not merely react to the outside world. Instead, it maintains an internal model of how the world works. Because we have this internal model, we can predict the outcome of an action before we actually take it. Before crossing a road, we estimate whether a car will pass by. Before catching a ball, we predict its trajectory. These abilities come from continuously simulating the world in our minds, rather than relying entirely on trial and error. This idea later became known by a more formal term: World Model. A world model does not describe a single image or a fixed video clip. It is an internal representation capable of continuously simulating the rules and dynamics of the real world. Why Is AI Research Turning Toward World Models? Because predicting “what comes next” is becoming increasingly central to how AI systems work. Language models predict the next token. Image models predict the next step in the denoising process. Video models predict the next frame. A world model, however, attempts to predict something broader: What should the world look like in the next moment? In 2018, David Ha and Jürgen Schmidhuber proposed in their paper World Models that an intelligent agent could first learn a model of the world, and then use that internal model to plan its actions. The Dreamer series later demonstrated that many complex tasks could be learned by training agents inside an “imagined world.” At the same time, the development of video models such as Sora and Veo led researchers to another realization: A model capable of continuously generating video has already learned, at least implicitly, many of the rules governing the real world. As a result, these two research directions have gradually begun to converge. But Video Is Not Yet a World This is where the distinction is often misunderstood. For a world model to support meaningful real-time interaction, it must solve several critical problems. Most video models today are essentially answering one question: What should the next frame look like? A true world model needs to answer much more: What happens if I take one step forward? If I walk behind a building and then return, will the building still be there? If I suddenly change the camera angle, will the entire space remain consistent? If I enter a command such as: “Summon a dragon.” Will the world respond immediately? In other words, a world model must do more than generate content. It must understand space. It must understand time. It must understand causality. And it must understand interaction. Moving from watching to participating is where the real difficulty of world models begins. World Models Are Entering the Interactive Era One of the latest attempts in this direction is Alaya World, recently open-sourced by Alaya World, or Alaya Lab. Instead of generating a fixed video clip, it generates a world that users can explore in real time. Users can begin with text, an image, or a video, enter the generated scene, move freely through it, and introduce new prompts at any moment during generation. The world responds immediately. According to the publicly released information, Alaya World provides: Real-time streaming generation at 720p and 24 FPS Stable continuous exploration for more than one minute The ability to switch prompts and trigger skills or events during generation Model weights and inference code released under the Apache 2.0 License Training code and datasets planned for future release What makes these capabilities important is not simply the technical specifications. It is that the generated “world” can now support continuous interaction. The official demo shows that users can genuinely control, transform, and explore the generated environment. AI Is Evolving From a Tool Into an Environment Over the past few years, most discussions around AI have focused on content generation. Generating text. Generating images. Generating videos. But world models raise a fundamentally different question: Can AI generate an environment that people can inhabit, explore, and continuously evolve? If the answer is yes, the impact will extend far beyond video generation. Game development, robotics training, embodied intelligence, digital twins, virtual production, and many other fields could be transformed by the development of world models. World models are still at a very early stage. Yet from Craik’s proposal of an internal mental model more than eighty years ago to the emergence of today’s interactive world-generation systems, a clear evolutionary path is beginning to take shape. Perhaps what AI is ultimately learning has never been limited to images, videos, or language. Perhaps it is learning the world itself. References GitHub: Technical Report:

113,347 Aufrufe

接入anysearch后,我的agent搜索效率提高了 Parallel、Perplexity、Tavily 这些搜索工具给 Agent 用,有个一直没解决好的问题——返回的是链接加摘要,Agent 拿到之后还要自己点开网页、筛选内容、判断哪条有用。金融、学术、代码这些垂直领域的搜索质量更差。输出没有结构,光解析内容就要烧掉大量 token。 分享一个我一直在用的为 AI Agent 设计的搜索基础设施 —AnySearch,一个为 Agent 量身打造的「搜索 Skill」: - 实时网页搜索 - 支持金融、学术、代码、社会媒体等垂直领域搜索 - 直接把网页转成干净的 Markdown(extract) - 输出结构化,Agent 能直接拿来用 安装 AnySearch SKILL 超级简单:复制下方提示词并发送给你的 Agent,即可自动完成安装:

接入anysearch后,我的agent搜索效率提高了 Parallel、Perplexity、Tavily 这些搜索工具给 Agent 用,有个一直没解决好的问题——返回的是链接加摘要,Agent 拿到之后还要自己点开网页、筛选内容、判断哪条有用。金融、学术、代码这些垂直领域的搜索质量更差。输出没有结构,光解析内容就要烧掉大量 token。 分享一个我一直在用的为 AI Agent 设计的搜索基础设施 —AnySearch,一个为 Agent 量身打造的「搜索 Skill」: - 实时网页搜索 - 支持金融、学术、代码、社会媒体等垂直领域搜索 - 直接把网页转成干净的 Markdown(extract) - 输出结构化,Agent 能直接拿来用 安装 AnySearch SKILL 超级简单:复制下方提示词并发送给你的 Agent,即可自动完成安装:

94,323 Aufrufe

Claude Fable 5 经过1个月紧急下架后再回归,我这两天也重新去测试了一下。 正好一直刷到赛博斗蛐蛐的视频,正好拿来测试一下,看看能不能做个同款出来。 给大伙看看fable 5 的效果:视频1 再来对比一下GPT-5.5的效果,老实说有点拉了,为什么把restart按钮直接盖住了屏幕啊?不是很理解:视频2 最后再来看看国产Deepseek V4 Pro的效果,物理效果感觉还是不行,有点迟钝的感觉:视频3 Fable 5的整体效果是最接近我刷到的小视频的效果的。 虽然效果很强,但是现在fable 5最大的问题在于,官方在6月22日以后,订阅套餐不能用Fable,只能走API。 但是价格实在是遭不住:每 M 输出 50 美元的定价让社区吐槽声不断!我推荐用Zenmux,这个省一些。目前有个加赠20%的活动,每人最高可享 300刀 ! 官网在这里: RPM、不限流。可调用全平台 200+ 模型(含 Claude Fable 5),非常适合做这种评测、并排对比和长期开发。

Claude Fable 5 经过1个月紧急下架后再回归,我这两天也重新去测试了一下。 正好一直刷到赛博斗蛐蛐的视频,正好拿来测试一下,看看能不能做个同款出来。 给大伙看看fable 5 的效果:视频1 再来对比一下GPT-5.5的效果,老实说有点拉了,为什么把restart按钮直接盖住了屏幕啊?不是很理解:视频2 最后再来看看国产Deepseek V4 Pro的效果,物理效果感觉还是不行,有点迟钝的感觉:视频3 Fable 5的整体效果是最接近我刷到的小视频的效果的。 虽然效果很强,但是现在fable 5最大的问题在于,官方在6月22日以后,订阅套餐不能用Fable,只能走API。 但是价格实在是遭不住:每 M 输出 50 美元的定价让社区吐槽声不断!我推荐用Zenmux,这个省一些。目前有个加赠20%的活动,每人最高可享 300刀 ! 官网在这里: RPM、不限流。可调用全平台 200+ 模型(含 Claude Fable 5),非常适合做这种评测、并排对比和长期开发。

48,569 Aufrufe

I went a little overboard with Codex last week and burned through my entire weekly allowance in two days. Luckily, my quota reset today. Otherwise, I’m not sure what I would’ve done. It got me thinking: instead of asking one large model to handle everything from start to finish, why not let a stronger model plan the project and review the work, while a model built for execution handles the day-to-day implementation? So I tried it. The result was better than I expected. I used GPT-5.6 Sol in Codex as the decision-maker, then ran Ling-3.0-flash from Ant Ling inside OpenCode as the execution engine. Together, they built a small 3D farming game. Before writing any code, I had Codex create four documents: SPEC.md defined the product scope and the lines we couldn’t cross. ARCHITECTURE.md laid out the isometric coordinate system, state machine, and module boundaries. TASKS.md broke the project into small jobs Ling could tackle one at a time. ACCEPTANCE.md explained how each step would be tested and what “done” actually meant. Then I gave Ling a very straightforward role: You are the execution model for this project. Read all four documents before you begin. Work only on the task assigned for this round. When you’re done, run typecheck, test, and build. If anything fails, read the error, fix it, and run the checks again. Do not move on to the next task early. Ling handled dependency installation, project structure, strict TypeScript configuration, test setup, and a production build in 6 minutes and 3 seconds. It ran into issues with the Vite test config, a TS6310 error, and a missing jsdom dependency along the way. Instead of stopping at the first error, it kept reading the logs and fixing the problems until all three checks passed. The speed was honestly hard to believe. If you exclude the time spent waiting on tools, it was producing more than 100 tokens per second. That made the whole development loop feel noticeably faster. After this experiment, I’m planning to keep using the same workflow. If the task is small, there’s no reason to call an expensive planning model for every single step. If the task is large, handing the entire project to a Flash model in one prompt isn’t a great idea either. The setup that makes more sense to me is: Use a more capable model such as Codex to explore the project, make architectural decisions, and break the work down. Put the constraints into specs, schemas, types, and tests instead of leaving them buried in chat history. Give Ling-3.0-flash a steady stream of clear, verifiable implementation tasks. Report bugs with structured context and actual error logs, rather than saying, “It still doesn’t work.” Bring Codex back in for architecture reviews, visual checks, and changes that affect multiple parts of the project. The point of this setup isn’t to give AI a big “build the whole project” button. It’s to turn software development into a pipeline with a much more sensible cost structure: Codex figures out the plan, sets the boundaries, and catches problems. Ling-3.0-flash moves quickly, calls tools reliably, and works through well-defined tasks at scale. For agent workflows that involve lots of repetitive edits, production tasks, and tool calls, this may be a more practical answer than simply using the biggest model for everything.

I went a little overboard with Codex last week and burned through my entire weekly allowance in two days. Luckily, my quota reset today. Otherwise, I’m not sure what I would’ve done. It got me thinking: instead of asking one large model to handle everything from start to finish, why not let a stronger model plan the project and review the work, while a model built for execution handles the day-to-day implementation? So I tried it. The result was better than I expected. I used GPT-5.6 Sol in Codex as the decision-maker, then ran Ling-3.0-flash from Ant Ling inside OpenCode as the execution engine. Together, they built a small 3D farming game. Before writing any code, I had Codex create four documents: SPEC.md defined the product scope and the lines we couldn’t cross. ARCHITECTURE.md laid out the isometric coordinate system, state machine, and module boundaries. TASKS.md broke the project into small jobs Ling could tackle one at a time. ACCEPTANCE.md explained how each step would be tested and what “done” actually meant. Then I gave Ling a very straightforward role: You are the execution model for this project. Read all four documents before you begin. Work only on the task assigned for this round. When you’re done, run typecheck, test, and build. If anything fails, read the error, fix it, and run the checks again. Do not move on to the next task early. Ling handled dependency installation, project structure, strict TypeScript configuration, test setup, and a production build in 6 minutes and 3 seconds. It ran into issues with the Vite test config, a TS6310 error, and a missing jsdom dependency along the way. Instead of stopping at the first error, it kept reading the logs and fixing the problems until all three checks passed. The speed was honestly hard to believe. If you exclude the time spent waiting on tools, it was producing more than 100 tokens per second. That made the whole development loop feel noticeably faster. After this experiment, I’m planning to keep using the same workflow. If the task is small, there’s no reason to call an expensive planning model for every single step. If the task is large, handing the entire project to a Flash model in one prompt isn’t a great idea either. The setup that makes more sense to me is: Use a more capable model such as Codex to explore the project, make architectural decisions, and break the work down. Put the constraints into specs, schemas, types, and tests instead of leaving them buried in chat history. Give Ling-3.0-flash a steady stream of clear, verifiable implementation tasks. Report bugs with structured context and actual error logs, rather than saying, “It still doesn’t work.” Bring Codex back in for architecture reviews, visual checks, and changes that affect multiple parts of the project. The point of this setup isn’t to give AI a big “build the whole project” button. It’s to turn software development into a pipeline with a much more sensible cost structure: Codex figures out the plan, sets the boundaries, and catches problems. Ling-3.0-flash moves quickly, calls tools reliably, and works through well-defined tasks at scale. For agent workflows that involve lots of repetitive edits, production tasks, and tool calls, this may be a more practical answer than simply using the biggest model for everything.

23,107 Aufrufe

我的视频复刻Skill在Sol模型的加持下,现在非常牛逼,只要你觉得某个视频是Remotion或者Hyperframes做的,都能复刻。 评论区还有视频样例和开源地址

我的视频复刻Skill在Sol模型的加持下,现在非常牛逼,只要你觉得某个视频是Remotion或者Hyperframes做的,都能复刻。 评论区还有视频样例和开源地址

23,709 Aufrufe

Videos

Pluvio9yte's profile picture

用了两天的Fable-5,得到了一个与大部分人截然相反的结论,实测体验如下: 速度:非常慢,尤其是开始分析和规划的时候能感受到像乌龟慢爬 价格:我是Max5订阅用户,虽然输入输出定价为Opus的两倍,但是实际消耗量并没有像流水一样,消耗速度确实变快了,但命中缓存后消耗没有特别高,没有人传人的消耗那么离谱的快 所以铺天盖地说消耗非常快的只有三种可能: 第一种是Pro订阅账号容量本来就小, 第二种是没自己账号纯造谣, 第三种是本来对Opus的消耗没有感知,看到别人说fable消耗快自己也一用发现消耗快于是觉得是真的消耗快了。本身Opus的消耗就非常快嘛,现在只不过是变为了原来的大概1.5x 对于我来说,我通常只用Opus,所以这个1.x倍Opus的消耗量能够接受。实际使用中建议把缓存重建修改为1小时。 能力:能力强体现在思维边界更广,架构能力更强。 对于前端能力测试确实是有很大提高,尤其是创意能力。真正落地到工程项目中,我的体感是能够真正发现GPT-5.5的问题了,不会再像之前基本一直认为GPT的分析是对的。 实际能力类似于Claude Opus4.6++与GPT-5.5++的结合版,目前没有到非常惊艳的程度 结合价格和6月22之后就没了,我也没有升级Max20的打算,Max5+GPT-5.5乃至即将出现的5.6我觉得完全够用。也建议大家理性消费。如果想走按量体验可以看下评论区。 最后给大家看一下昨晚用Fable简单构建的前端的效果,关于为什么我吐槽过还要做前端,是因为我也需要在抖音小红书炸裂搞流量,人作为视觉动物,前端是最开始抓住注意力的开头的。 视频如下,网站部署在verel地址放在评论区了,大家可以自行查看

雪踏乌云

24,152 Aufrufe • vor 2 Monaten

Keine weiteren Inhalte verfügbar