yz2ww

Beijing UST-Metallurgy Programmer.
Vibe coding guru
❌人机
Julyyy22X_

[Claude @claudeai]

Fable 5 is back.

[Morris @Morris_LT]

真正应该远离的，不是能力差的人，而是持续消耗你的人。什么叫消耗你的人？他们不断占用你的时间，破坏你的情绪，打断你的节奏，消耗你的精力，却从不创造任何价值。他们往往是言语上的巨人，行动上的矮子，把大量时间花在讨论、抱怨、评价和幻想上，却很少真正行动。你每把注意力放在一个与你目标无关、持续消耗你的人身上，本质上都是在透支自己的生命。因为时间可以重新安排，金钱可以重新赚取，但精力一旦被无意义地消耗掉，就再也无法完整地拿回来。真正成熟的人生策略，不是试图改变所有人，而是学会筛选，把有限的生命资源，留给真正重要的人、重要的事，以及真正值得投入的未来。

[ClaudeDevs @ClaudeDevs]

Now that Fable 5 is ready to build (again), we've reset everyone's 5-hour and weekly rate limits.

[Tibo @thsottiaux]

Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours.

We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a few smaller problems compounded for some users.

Here's what we found and changed:
- Actual usage: Auto-review had become more proactive, another change was triggering more subagent work, and background suggestions could run twice or retry too frequently after failures. We reverted the changes and fixed suggestion scheduling, duplicate generation, and retry behavior. This should reduce unnecessary background token consumption while preserving the work users explicitly request.
- Usage reporting: Auto-review was incorrectly appearing as GPT‑5.4 usage, and failed or rate-limited requests were still shown as turns. Auto-review now appears as its own category, and only successful requests count toward the turn graphs. Rate-limited requests were never charged, but they were being displayed incorrectly.
- Immediate relief: We reset usage limits while rolling out the fixes, then shipped hotfixes across the CLI, desktop app, and usage backend.
- What to expect: New usage data should be clearer and actual consumption should be lower. Historical charts may still show auto-review under GPT‑5.4 because older turn data was not relabeled. Features that intentionally perform more work; such as /goal, subagents, and higher reasoning levels will still naturally use more capacity.

All fixes are now deployed, and we've added more detailed monitoring so we can detect background-usage regressions sooner. We'll continue watching the results closely.

Thank you for building and doing all sorts of things with Codex.

[雨哥向前冲 @xiangxiang103]

卧槽，Anthropic 这次真的翻大车了。

有人在 Claude Code 的二进制里挖出了隐藏代码——专门检测你是不是中国用户、或者代理走了中国。不是普通遥测，是故意混淆、发行说明不写、用户完全不知情的那种。

过程很骚：
- 检测到你在用代理 → 检查时区（上海/乌鲁木齐）
- 检查代理 URL 是不是指向中国域名或 AI 实验室
- 命中之后，偷偷改掉 system prompt 里的字符：把日期格式换掉、把撇号换成别的 Unicode 同形异码字
- 这些改动肉眼根本看不出来，但 Anthropic 后端可以对得上

说穿了就是：它在你的 prompt 里藏了一组只有他们自己能解的水印。

从 v2.1.91（今年4月2号）就有了，代码做了 XOR 加密、函数名压成一坨，strings 根本扫不出来。

Anthropic 要防什么大家都懂：防套 API 卖翻墙服务、防国内实验室蒸馏模型。但问题是——你是做开发工具的，用户给你文件系统权限、给你 Shell，你背地里搞这一手？

最寒心的是：没有任何文档、没有任何声明。

今天它能偷偷改 prompt 水印你，明天呢？后天呢？一个运行在你本地的编码 Agent，你永远不知道它到底还在上面藏了什么。

源码三月份就因为 npm 泄露过一次，六十万行被人翻了个底朝天。这才过多久，又来一桩。

开发者工具的底线就三个字：别背刺。

信任建起来要几年，毁掉只需要你一次不打招呼的骚操作。这事已经在 X 和 Reddit 炸了，我不信 Anthropic 能装死到底。

原帖链接： https://t.co/IK5gJLTRQe

[yz2ww @Zwyoung7]

@binb3123 你知道

[yz2ww @Zwyoung7]

@binb3123 包括坑蒙拐骗样样精通

[yz2ww @Zwyoung7]

@Nannjunda1 谁看。不给

[yz2ww @Zwyoung7]

@Serkan56943213 好烦人机

[yz2ww @Zwyoung7]

@666boy666boy666 聊生命的意义

[yz2ww @Zwyoung7]

有真人吗？02男大，求个聊天的。

[yz2ww @Zwyoung7]

@LifenZhang123 anything

[yz2ww @Zwyoung7]

@jackyinuibe 海淀选手请扣1

[yz2ww @Zwyoung7]

@MdAkash26288892 00后

[yz2ww @Zwyoung7]

@igLeoN2 我在海淀，02

[yz2ww @Zwyoung7]

@225ccv 有真人吗。