[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"news-bba970e8-e80c-4a7f-9c8c-f4acfe00fbea":3},{"id":4,"title":5,"summary":6,"original_url":7,"source_id":8,"tags":9,"published_at":23,"created_at":24,"modified_at":25,"is_published":26,"publish_type":27,"image_url":13,"view_count":28},"bba970e8-e80c-4a7f-9c8c-f4acfe00fbea","Anthropic 开发者大会直击：Code with Claude 揭示编程未来","5月中旬，Anthropic 在伦敦举办了两天年度开发者大会 Code with Claude。会上抛出的一个现场调查让在场工程师陷入沉默：超过九成参与者已在过去一周提交过完全由 Claude 生成的 Pull Request，其中大多数人甚至没有逐行审查过代码。这不是孤例——Anthropic 工程师在台上直言：「Anthropic 内部绝大部分代码现在也由 Claude 编写。」\n\n这种转变来得极快。一年前 Claude Code 还只是辅助工具，如今已演变为独立开发环境。Anthropic 的策略是让 AI 自己管理错误修正流程——传统做法是 AI 生成代码后由人工排查问题，而新方向是让 Claude 自主验证、测试并迭代修复，直到代码正常运行。工程师 Ravi Trivedi 在演讲中明确表示：「核心原则就是不要干预 Claude 的工作，我们常说『让它跑』。」\n\n最新功能「Dreaming」进一步推进了这一理念。Claude Code 中的智能体能够为自己的任务生成笔记、跨任务保留上下文，当其他智能体接手相同代码时仍能获取相关背景信息。这意味着开发流程从「人写代码」演进为「人设计目标，AI 自主执行」，人类角色已转向任务定义与结果验收。\n\n这不仅是工具升级，而是软件开发范式的根本转变。当 AI 开始自主迭代、跨任务保持状态，开发者必须重新思考自己的核心价值在哪里。","https:\u002F\u002Fwww.technologyreview.com\u002F2026\u002F05\u002F21\u002F1137735\u002Fanthropics-code-with-claude-showed-off-codings-future-whether-you-like-it-or-not\u002F","395b92fa-25c5-4568-8297-f4768aa881da",[10,14,17,20],{"id":11,"name":12,"slug":12,"description":13,"color":13},"23544f6a-eea1-4f05-aa8d-749ca862d5d2","anthropic",null,{"id":15,"name":16,"slug":16,"description":13,"color":13},"dca4d0ab-7994-43a7-839e-7756fc77344a","claude",{"id":18,"name":19,"slug":19,"description":13,"color":13},"e82b2d09-81b2-43d1-977e-e018443b3c14","coding-agent",{"id":21,"name":22,"slug":22,"description":13,"color":13},"01598627-1ea6-4b27-a5d8-874971571a71","llm","2026-05-21T22:00:00Z","2026-05-21T22:05:59.428776Z","2026-05-21T22:05:59.428788Z",true,"agent",31]