跳到正文

AI 编码

AI 写代码的一切:编码助手、Vibe Coding、代码模型评测与开发工作流变革。

当前仅显示精选新闻
455条精选相关主题Agent 智能体Cursor教程实践

最新精选

第 141–160 条 · 共 455 条
8月30日周日
  1. @testingcatalog67

    OpenAI 再次为 Codex 和 ChatGPT Work 的全部付费用户重置用量额度,并修复多项用量消耗问题,用户整体可用量比此前多出 10% 到 50%。官方公布的修复包括 compaction 阶段遗留旧图片导致重复压缩、后台 memory worker 继承 Stop hooks 无法停止、set /goal 超出停止条件继续运行、自定义 automations 执行频率高于配置、子智能体未经要求调用更强模型,以及 Computer History 重复汇总重叠活动、普通回合触发额外后台请求、MCP 工具结果被重复编码等,并称已做架构调整防止回退。官方还表示正在开发在应用内直接展示用量去向的功能。

    引用@thsottiaux@thsottiaux

    We are reseting usage for all paid users of Codex and ChatGPT Work. Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes. Depending on how you use Codex, you should see your usage go between 10% and 50% further than before. We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed: - Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed. - Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed. - Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed. - Automations. Some custom schedules could run more frequently than configured. Fixed. - Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed. - Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed. - Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this. - MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed. We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess. Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!

    推荐理由:原文逐项列出八类用量异常的原因与修复结果,读者可据此判断 Codex 付费额度实际能多用多少。

  2. @thsottiaux72

    Cursor CEO Michael Truell 表示,OpenAI 计划在三个月内阻止 Cursor 用户访问 OpenAI 模型,OpenAI 模型服务约 5% 的 Cursor 用户流量,Cursor 正与 OpenAI 团队沟通解决。OpenAI 的 Tibo 转发回应称,这个 5% 应带上强烈前提,token 既不代表收入也不代表创造的价值,较小或较弱的模型完成同一任务需要更多 token,会显著抬高流量占比。

    引用@mntruell@mntruell

    We’re sorry to see that OpenAI put out a note saying they plan to block Cursor users from accessing OpenAI models in three months. OpenAI models serve about 5% of Cursor user traffic, and we’re speaking with the OpenAI team to resolve this. Cursor was one of the very first users of OpenAI, we’ve worked closely with their team for years, and we’ve trusted their platform to be neutral infrastructure for our business.

    推荐理由:OpenAI 员工反驳 Cursor 给出的 5% 流量占比,提出 token 用量不等同收入与价值,可供理解这场分歧。

  3. @omarsar070

    OpenAI 计划在三个月内阻止 Cursor 用户访问 OpenAI 模型,被引用的一方表示 OpenAI 模型约占 Cursor 用户流量的 5%,正在与 OpenAI 团队沟通解决。@omarsar0 评论称 Cursor 是行业里拥有 harness 和模型的成功案例,并指出未来公司需要拥有自己的智能栈。

    引用@mntruell@mntruell

    We’re sorry to see that OpenAI put out a note saying they plan to block Cursor users from accessing OpenAI models in three months. OpenAI models serve about 5% of Cursor user traffic, and we’re speaking with the OpenAI team to resolve this. Cursor was one of the very first users of OpenAI, we’ve worked closely with their team for years, and we’ve trusted their platform to be neutral infrastructure for our business.

    推荐理由:作者以 Cursor 为例,说明同时掌握 harness 与模型的公司更容易积累优势,供其他全栈 AI 团队参考。

8月29日周六
  1. AGI Hunt · 微信公众号77

    腾讯发布混元 Hy4 preview:770B 参数、1M 上下文并开源权重

    腾讯发布混元 Hy4 preview,总参数 770B、激活 49B,支持 1M tokens 上下文,权重与 FP8 版本已在 HuggingFace、GitHub、ModelScope、GitCode 开源,采用 Apache 2.0 协议。

    推荐理由:作者用游戏开发、PPT 制作和云账单分析等多场景实测,展示 Hy4 preview 的能力边界与同代模型对照。

  2. @frxiaobei74

    OpenAI 宣布终止与 Cursor 的合作,按提案 Cursor 对其模型的直接访问将于 11 月 12 日结束,OpenAI 表示会支持受影响的开发者过渡。

    引用@OpenAI@OpenAI

    We’re ending our partnership with Cursor following its acquisition by SpaceX. Under our proposal, Cursor’s direct access to our models would end on November 12. We know that the people most affected by this decision are the developers who rely on OpenAI models in Cursor. We care about their experience in this transition and we’re ready to go above and beyond to support them. https://t.co/OzuCTzUjfX

    推荐理由:作者把 Windsurf 与 Cursor 被断供、被收购的相反顺序摆在一起,便于观察独立编码工具的处境。

  3. 机器之心 · 微信公众号83

    OpenAI 宣布终止与 Cursor 合作,11 月 12 日起停止模型直接访问

    OpenAI 发布声明宣布终止与 Cursor 的合作,Cursor 对其模型的直接访问将于 11 月 12 日结束,理由是 Cursor 被 SpaceX 收购后,OpenAI 无法确信其会在服务条款范围内使用相关技术。

    推荐理由:OpenAI 断供 Cursor 与 Anthropic 此前切断竞品访问的做法前后呼应,读者可看到模型访问权正被当作竞争手段。

  4. Michael Truell74

    Cursor CEO Michael Truell 称 OpenAI 已发通知,计划在三个月后阻止 Cursor 用户访问 OpenAI 模型。他透露 OpenAI 模型约占 Cursor 用户流量的 5%,Cursor 正与 OpenAI 团队沟通解决,并表示 Cursor 是 OpenAI 最早的用户之一,多年来将其平台视为业务的中立基础设施。

    推荐理由:Cursor CEO 一方回应断供传闻,补充了自家流量占比等一手信息,可帮读者了解双方目前的态度。

  5. @Yuchenj_UW71

    OpenAI 宣布结束与 Cursor 的合作关系,原因是 Cursor 被 SpaceX 收购;按其提出的方案,Cursor 对 OpenAI 模型的直接访问将于 11 月 12 日终止。OpenAI 表示受影响最大的是在 Cursor 中使用其模型的开发者,愿意在这一过渡期提供支持并附上了相关链接。转发该消息的 Yuchen Jin 评论称,Cursor 中不再有 OpenAI 模型,Anthropic 取得了主导地位。

    引用@OpenAI@OpenAI

    We’re ending our partnership with Cursor following its acquisition by SpaceX. Under our proposal, Cursor’s direct access to our models would end on November 12. We know that the people most affected by this decision are the developers who rely on OpenAI models in Cursor. We care about their experience in this transition and we’re ready to go above and beyond to support them. https://t.co/OzuCTzUjfX

    推荐理由:OpenAI 宣布结束与 Cursor 的合作并给出过渡说明,可据此了解开发者调用其模型的路径变化。

  6. @Yuchenj_UW69

    OpenAI 宣布结束与 Cursor 的合作,按其提案,Cursor 对 OpenAI 模型的直接访问将于 11 月 12 日终止。OpenAI 称这一决定是在 Cursor 被 SpaceX 收购之后作出的,受影响最大的是依赖这些模型的开发者,并表示会在过渡期提供支持。转发此消息的 Yuchen Jin 认为这一结果在预料之中。

    引用@OpenAI@OpenAI

    We’re ending our partnership with Cursor following its acquisition by SpaceX. Under our proposal, Cursor’s direct access to our models would end on November 12. We know that the people most affected by this decision are the developers who rely on OpenAI models in Cursor. We care about their experience in this transition and we’re ready to go above and beyond to support them. https://t.co/OzuCTzUjfX

    推荐理由:OpenAI 公布终止与 Cursor 合作的时间点,读者能看到编程工具与模型供应商绑定关系的一种变化。

  7. @thsottiaux79

    OpenAI 宣布终止与 Cursor 的合作,Cursor 对 OpenAI 模型的直接访问将于 11 月 12 日结束,作者称原因归结为信任问题。过渡期内开发者仍可使用自己的 OpenAI API key,并可通过 OpenAI 的 IDE 扩展在 Cursor 中继续使用。

    引用@OpenAI@OpenAI

    We’re ending our partnership with Cursor following its acquisition by SpaceX. Under our proposal, Cursor’s direct access to our models would end on November 12. We know that the people most affected by this decision are the developers who rely on OpenAI models in Cursor. We care about their experience in this transition and we’re ready to go above and beyond to support them. https://t.co/OzuCTzUjfX

    推荐理由:OpenAI 与 Cursor 合作终止的生效时间和替代接入方式都已明确,使用 Cursor 的开发者可据此提前安排迁移。

8月28日周五
  1. @OpenRouter76

    GLM-5.3 现已开放权重,并上线 OpenRouter,具备 1M 上下文和可配置的推理力度。该模型由 @Zai_org 发布,面向复杂软件工程、长程智能体和网络安全场景。Zai 称这是其在智能体编程与网络防御方面能力最强的模型,权重可供下载、运行和定制。

    引用@Zai_org@Zai_org

    GLM-5.3 is now open-weight. Our most capable model for agentic coding and cyber defense is now available to download, run, and customize. Weights: https://t.co/v1IbWMXxg4 Tech blog: https://t.co/ekQkO83jCv https://t.co/f8XlJksKyf

    推荐理由:GLM-5.3 以开源权重上线托管平台,1M 上下文与可调推理力度可供开发者直接接入评估。

  2. @kimmonismus71

    GLM-5.3 已在 Hugging Face 正式上线,作者列出了在本地运行该模型的硬件门槛。FP8 需 10–12× H100 或 8× H200;4-bit/NVFP4 约 390–430GB,可用一台 512GB Mac Studio 或 4× DGX Spark;激进 2-bit 约 230–250GB,一台 256GB Mac Studio 或 2× DGX Spark,但有质量和上下文方面的权衡。首批 GGUF 和 NVFP4 量化已开始出现。

    引用@kimmonismus@kimmonismus

    Quick reminder: in 4 hours you will be able to download and run sota AI. If you have enough compute ofc. What a time to be alive. https://t.co/T6bs1VnVG1

    推荐理由:GLM-5.3 上线后给出了各量化档位的显存与硬件门槛,可供本地部署选型参考。

  3. @kimmonismus66

    腾讯发布开源模型 Hy4 Preview,770B 参数、49B 激活参数、1M token 上下文窗口。腾讯称 Hy4 可并行协调多个 Codex 会话、评估其输出并调整研究方向,在八个基准上超过 Codex 单独工作,目标场景是长程编码、多文件办公任务与科学研究。作者认为这是一次扎实的发布,放在几个月前属于绝对的 sota。

    原始视频预览图;未保存可播放视频URL原始视频预览图;未保存可播放视频URL
    引用@TencentHunyuan@TencentHunyuan

    🚀 Hy4 preview is here. 770B, 49B active, 1M context. Built for productivity. Open source frontier. Consistent affordable price. Use it. Tell us what breaks. More on Hy blog:https://t.co/rbl1IWRk3C HuggingFace:https://t.co/mE9wevH5XR Github:https://t.co/pyl9zckpoL https://t.co/4iW6gSuZKr

    推荐理由:腾讯开源 770B 参数模型并给出并行调度多个 Codex 会话的智能体研究能力,可对照其八个基准结果判断定位。

8月27日周四
  1. @omarsar069

    一项针对自我演化编码智能体的新研究提出 EvoMal 攻击,共享技能库中的恶意技能不会被直接调用,而是被智能体当作编写模板复制、保存并执行,在库中自行扩散。在 153 个与工具相关的 SWE-bench Verified 任务、六个模型上,智能体自我投毒率为 20.3% 至 41.8%,被投毒的库最终持有的恶意技能是植入数量的 4.9 至 9.0 倍。

    推荐理由:论文量化了共享技能库中恶意技能被智能体自行复制扩散的机制,并给出一种提示词缓解办法,可供搭建技能库的团队参考。