←搜索结果

按匹配度 · 共 398 条结果 清除搜索

星期三

  1. Meta Engineering Blog精选

    Meta 工程博客:如何构建从专家反馈中学习的组织级第二大脑智能体

    Meta 工程博客介绍了一个面向合规领域的 AI 智能体,把组织知识拆成 200 多个结构化文件,并用可组合的 recipes 分离知识与推理流程。专家反馈经诊断、编译、验证后以文本编辑形式落地,无需重训模型,每个修复都会自动加入回归测试集。系统在六周三个开发冲刺后,将单项评估耗时从数天缩短到数分钟,改进周期内零回归。

    We’ve built an AI agent that acts as a secondary expert for a given domain, making deep specialist knowledge readily available and preserved for anyone in an organization to access, share, and build upon; This is not a typical domain-specific agent. Its novelty comes from integrating two layers: A structured, auditable knowledge architecture separates what the agent knows from how it reasons; A self-improvement loop then compiles expert feedback into verified, regression-tested updates without m

    匹配字段正文

星期一

  1. Amazon Science

    Amazon Science 介绍如何用 Verus 开发可证明正确的 Rust 代码

    Amazon Science 发文介绍开源自动程序验证器 Verus,它用数学规格机械检查 Rust 代码在所有输入下是否符合预期,弥补传统测试难以覆盖的边界情况。开发者可直接在 Rust 源码中用类 Rust 语法写前置与后置条件,通常不到一秒即可获得反馈,AI 智能体也能参与证明生成。Verus 还能对 Rust 的 unsafe 代码块和自定义锁方案的并发代码做数学验证,亚马逊已用它证明 Nitro Isolation Engine 关键原语及内部关键基础设施的正确性,开源项目如证书验证库、数据格式解析器和 Kubernetes 控制器也已采用。

    cases; Developers annotate Rust source code directly with preconditions and postconditions using Rust-like syntax, enabling fast feedback loops (under one second) and allowing AI agents to assist in proof generation; Verus enables mathematical verification of Rust's "unsafe" code blocks and concurrent code with custom locking schemes, re-establishing machine-checked safety guarantees for performance-critical implementations like AWS's Nitro Isolation Engine; Amazon uses Verus to prove correctne

    匹配字段正文

  2. Timothy B. Lee:Understanding AI

    我花 4000 美元买了一台中国机器狗:Unitree 如何把足式机器人做便宜

    作者花 4017 美元购入 Unitree Go2 Pro 机器狗并实测,认为它实用价值有限,但价格远低于几年前同类产品。文章梳理 Unitree 的低成本路径:四腿各三个同款电机、6.33 比 1 低减速比齿轮箱、自研电机与零部件,以及中国政府的税收优惠和公共机构采购支持。Unitree 已从四足扩展到人形,2023 年推出 H1、次年推出 G1,消费版起价 13500 美元;其 8 月 19 日在上交所上市首日股价涨超五倍,周一收盘市值 34 亿美元。美国方面,众议院两党法案拟限制中国机器人进口,FCC 也在 7 月出台针对外国制造机器人的新规。

    similar role for quadruped robots — though as I’ll discuss later, Unitree’s robots now face legal restrictions in the United States. Sponsor message Tasklet — Run your business on agents AI agents are useful when they stop chatting and start doing. Tasklet lets you build persistent agents that work across Gmail, Slack, HubSpot, Zendesk, Linear, and thousands of other tools. Describe a workflow in plain English, choose what the agent may do on its own, and require approval for sensitive steps. Ag

    匹配字段正文

星期五

  1. LMSYS Blog精选

    LMSYS 公开 infer-forge:围绕 SGLang 的 Harness、Loop 与 Graph 工程方法

    LMSYS 发布 infer-forge 方法论文,介绍围绕 SGLang 的推理工程系统,由 MonoRepo、Harness、Task Loop 和 Task Graph 四层结构组成,用于让跨仓库的推理优化工作可复现、可验证。该系统为内部工程系统,并非 SGLang 或 LMSYS 官方组件,目前不开源,文章公开的是构建方法论,供团队交给 AI 编码工具并结合自身系统上下文搭建适配实现。文中给出使用记录:一位工程师 4 月至 7 月的在飞任务峰值从 2 个升至 9 个,DeepSeek-V4-Pro 服务项目中 38 个可独立验证的任务节点被组织成任务图。

    The inference deployment space stacks five layers of static configuration. Model shows Ling, Qwen, DeepSeek, Kimi, GLM, and MiniMax. Serving Scenario runs Modality (text, image, video) into Traffic Shape (input and output length, media count, resolution, QPS, concurrency, cache reuse) into SLO (TTFT, TPOT, throughput, E2E latency). Serving Topology separates Deployment Architecture—Colocated PD, PD Disaggregation, and EPD Disaggregation, each listing the node roles it is built from — Prefill and Decode together, then Prefill and Decode as separate roles, then Encoder alongside them — from Parallelism—TP, PP, DP, and EP—because the two are chosen independently. Versioned Runtime Profiles is a stack of tabbed cards labelled Service A rev. 12, Service B rev. 7, and Service C rev. 21, plus a fourth paler card behind them all, blank and showing only its top edge, whose narrow tab carries an ellipsis for the profiles not drawn, the front card holding an Engine Configuration and a Container I

    ecific deployment point defined by the model, workload, SLO, serving topology, runtime version, and accelerator platform. The same patch may improve one point and regress another. Agent-assisted exploration can produce more environments, experiments, measurements, and rejected paths, all of which must remain reproducible. The first requirement is therefore reliable execution. Reproducing a deployment point requires more than model capability: tools, environments, context, memory, Verification, a

    匹配字段正文

星期四

  1. Linear:Now

    Linear 如何用 StyleX 改造 React 应用的样式系统

    Linear 通过超过 1,000 个 PR,将 React 应用从 styled-components 迁移至 StyleX,并以 codemod、AI 智能体和人工判断共同推进。测试显示,移除运行时样式注入后,重视图页面的主线程 CPU 工作减少约 20% 至 35%,中端设备速度提升约 30%。团队还通过 lint 规则、仓库级检查器和迁移追踪工具,约束样式接口、合并优先级及主题安全。

    Rows of white pixelated grid patterns on a black background, transitioning from dense solid blocks on the left to sparse scattered squares on the right.

    g a long tail of UI regressions. As our team grows, we wanted to create a stronger foundation for how UI is composed. Defining these boundaries is becoming especially important as agents contribute more and more to our codebase. Another more practical reason to migrate was performance. We care about keeping Linear fast and CSS-in-JS adds work during rendering to generate styles and inject CSS rules. The final straw was the performance regression we saw after upgrading to React 18 that introduced

    匹配字段正文

星期三

  1. Trail of Bits Blog

    Trail of Bits 实测:GPT 5.6-Cyber 三次逃出 QEMU/KVM 虚拟机

    Trail of Bits 的 Artem Dinaburg 在 Patch the Planet 项目中获得 GPT 5.6-Cyber 预览权限,让它在 CTF 任务中逃出运行在 Debian 12、AMD Zen3 上的 QEMU/KVM 虚拟机,结果它三次成功逃逸。第一次利用几周前披露的 Januscape(CVE-2026-53359)内核漏洞;更新内核后,它组合 libslirp 4.7.0 的 CVE-2026-9539 与一个未分配 CVE 的修复提交实现任意内存读写;在手动重建最新上游 QEMU 和 libslirp 后,它又串联三个 0-day 和一个未进入发行版内核的已修复漏洞完成逃逸。作者指出,该智能体在约 12 小时的时间跨度内跨多次压缩和子智能体调用保持持续作业,能自行回溯失败路径、拉取论文、编写 oracle 和最小复现;他建议改用 Firecracker 这类最小攻击面的虚拟化方案,并加强最小权限、日志与主动监控。

    boot the machine when it hardlocked the host kernel. If it wasn’t clear before, I will state it plainly: you can no longer assume a mere VM will contain a sufficiently advanced AI agent. To use a 2010s term of art, you should treat such agents as an advanced persistent threat. Let’s imagine a common situation: you want to run an AI agent, but need its full capabilities, including the ability to download, build and debug software; do research; sift through dependencies; set up fuzzers; triage vul

    匹配字段正文

  2. A6 a6-052 · Fireworks AI精选

    Fireworks 评测:DeepSeek V4 Pro 在 SWE-Bench 领先,单任务成本约为 Fable 5 的三分之一

    Fireworks 用 SWE-Bench Verified、LiveCodeBench v6、Aider Polyglot v1 和 Terminal-Bench 2.1 四组基准测试 DeepSeek V4 Pro 0813,其在 SWE-Bench 上每解决一个任务花费 $0.309,Fable 5 为 $0.808,LiveCodeBench 上为 $0.040 对 $0.225。在 409 个任务的合并样本上,DeepSeek V4 Pro 与 Fable 5 的 oracle 路由达到 92.4% 准确率,高于单用 Fable 5 的 86.6%,每任务成本 $0.279 对 $4.510,其中 86.3% 的任务路由到 V4 Pro。该模型在 Aider Polyglot 的 Java 子集上仅 48.9%,明显低于 Fable 5 的 74.5%,Fireworks 认为 Java 为主的代码库更适合多模型路由;DeepSeek V4 Pro 的训练已在 Fireworks 上线,支持 SFT、DPO 和 RFT。

    dpoints, dedicated deployments, and training support. The model provides a 1M-token context window with native tool calling and preserved reasoning history, targeting long-horizon agentic workloads. We ran DeepSeek V4 Pro 0813 through the same eval suite we used for Kimi K3 in July . We evaluated Deepseek against Kimi K3 and Fable 5 across four benchmark families: SWE-Bench Verified, LiveCodeBench v6, Aider Polyglot v1, and Terminal-Bench 2.1. Deepseek V4 Pro is the strongest single model in thi

    匹配字段正文

  3. Fireworks AI

    Fireworks 实测 DeepSeek V4 Pro 在 CyberGym 安全任务上的成本与通过率

    Fireworks 在 CyberGym 的 697 个共同有效任务上测试 DeepSeek V4 Pro 0813,其奖励率为 53.7%,每个成功任务成本 2.502 美元,约为 Kimi K3 的一半。Kimi K3 的奖励率最高,为 68.4%,但每个成功任务成本为 4.914 美元;GPT-5.5 的奖励率为 47.6%,每个成功任务成本为 9.641 美元;Claude Opus 4.8 的奖励率仅为 5.9%,每个成功任务成本为 33.275 美元。测试中,DeepSeek V4 Pro 在 840 个任务上全部产生原生工具调用,没有出现拒答或输出截断;一旦通过第一阶段验证,它完成完整补丁的比例为 94.7%。

    1,507 real vulnerabilities across 188 widely used open-source projects, drawn from Google’s OSS-Fuzz campaign and the ARVO reproducible-vulnerability archive. Each task hands the agent a short description and a real vulnerable codebase. The agent has to locate the flaw, build an input that actually triggers it, and then patch it. Grading is by execution, not by a judge model. The proof-of-concept either crashes the target or it does not. The structure of Cybergym is agentic, long-horizon, and u

    匹配字段正文

  4. Browser Use精选

    Browser Use 如何从真实用户流量构建可扩展的长程 RL 环境

    Browser Use 发布工程博客,介绍如何从真实用户流量和真实网页构建长程 RL 环境,并开源其中 200 个任务及其 rubric(github.com/browser-use/benchmark)。流程包括从数亿条任务提交中筛出约一千万条去重任务,用 Gemini 3 Flash 做适配性标注(与人工标签一致率 77%,密封集 81%),再用 MiniMax M3 执行筛选,约 40% 的合格任务被判定为可行且足够难。作者指出迭代式 rubric 不会收敛,改用 9 个模型各跑两次的并行轨迹,由 Claude Fable 5 编写 rubric,事实经实时网页核验并标注日期,最终将条目翻转率压到 1% 以下。

    Two rubric regimes: one judge per trace in sequence, where an unverifiable claim becomes a permanent fact, against one judge over all traces with live web verification, producing a single rubric.

    Engineering Browser agent benchmarks are saturating. This is how we build RL environments from real user traffic against the real web. Evaluations 1. Filtering Down the Tasks; 2. Suitability; 2.1 Hand labelling; 2.2 Aligning a labelling agent; 3. Personal Data Replacement; 4. Feasibility and Difficulty; 5. The Problem with Judgement; 6. Difficulty Estimation; 7. Rubric Construction; 7.1 Why iterative rubrics do not converge; 7.2 The parallel rubrics we use instead; 7.3 Properties of a good rubri

    匹配字段正文

星期五

  1. Together AI Blog

    GLM-5.3 与 GPT-5.6 Sol 在 DeepSWE 上的成本、编码与路由对比

    Together AI 在全部 113 个 DeepSWE 任务上各跑 4 次、共 904 次 rollout,对比 GLM-5.3(max)与 GPT-5.6 Sol(max)。单次尝试 Sol 以 72.7% 的 pass@1 领先 GLM-5.3 的 69.0%,但 GLM-5.3 每次 rollout 成本 3.99 美元、约为 Sol 8.37 美元的一半,并在 pass@2 追平、pass@4 以 87.6% 反超 85.8%。先跑 GLM-5.3、测试失败再升级到 Sol 的级联方案解决 85.9% 的任务,每任务 6.61 美元,高于 Sol 单跑的 72.7%,也低于一次 Sol rollout 的价格。

    ice as fast per rollout. GLM-5.3 ties pass@2 and wins pass@4 (87.6% against 85.8%) at half the cost per rollout, so it is the stronger value pick for high-volume or retry-tolerant agent work. In our run, GLM-5.3 cost \$3.99 per rollout against \$8.37 for GPT-5.6 Sol at max effort, about 2.1x lower. Measured per solved task, GLM-5.3 returned 17 solves per \$100 against Sol's 9, roughly twice the solved work per dollar. They split the board. GLM-5.3 takes JavaScript (90 against 75) and Rust (70 ag

    匹配字段正文

星期二

  1. Together AI Blog

    DeepSeek V4 Pro 0813 与 GPT-5.6 Sol 在 DeepSWE 上的成本与编码对比

    Together AI 在 DeepSWE 全部 113 个任务上各跑 4 次对比 DeepSeek V4 Pro 0813 与 GPT-5.6 Sol:Sol 单次通过率 72.7% 领先 Pro 的 62.8%,但 Pro 每次 rollout 仅 0.24 美元,约为 Sol 8.37 美元的 35 分之一,pass@4 上 Pro 以 88.5% 反超 Sol 的 85.8%。先用 Pro、测试失败再升级到 Sol 的级联方案可解决 83.0% 的任务,单任务成本 3.35 美元,高于 Sol 单独使用的 72.7%,也高于理想单次路由的 80.8%。Sol 更快更简洁(中位 53 步、17 分钟、59k 输出 token),但失败时 20% 会破坏仓库原有测试套件,Pro 这一比例为 11%。

    and is much faster per rollout. DeepSeek V4 Pro 0813 wins pass@4 (88.5% vs 85.8%) at 35x lower cost per rollout, so it is the stronger value pick for high-volume or retry-tolerant agent work. In our run, DeepSeek V4 Pro 0813 cost \$0.24 per rollout versus \$8.37 for GPT-5.6 Sol at max effort, roughly 35x cheaper. Measured per solved task, Pro returned 260 solves per \$100 against Sol's 9, about 30x the solved work per dollar. GPT-5.6 Sol leads Python (74), Go (79), TypeScript (66), and JavaScrip

    匹配字段正文

星期六

  1. Ahead of AI

    从零构建 AI 文本检测器

    作者从零构建一个 AI 文本检测器,并将其作为验证器训练小语言模型生成规避检测的文本。项目通过微调 DistilBERT 分类器输出 0-100 分,涵盖评估、训练、本地部署、API 和 UI。文章同时说明检测结果仅反映训练分布下的估计概率,并可能出现误报及持续的攻防迭代。

    an applied end-to-end LLM project including evaluation, training, and local deployment for real-world use. The outcome of this is an AI-detector API that can be used by humans and agents, and a user-friendly UI. Method overview Here, we are going to develop a method similar to Pangram models, which, as far as I know, are behind Substack AI detection feature. I wrote a short article about AI-text detection a while back in 2023: What Are the Different Approaches for Detecting Content Generated by

    匹配字段正文

星期三

  1. OpenRouter:Announcements

    OpenRouter 发布实时网页搜索基准:为智能体挑选合适的引擎、深度与模型

    OpenRouter 上线实时网页搜索基准页面,用 BrowseComp、DeepSearchQA、WideSearch 和 HLE 四套基准,在多个模型、引擎与搜索配置上按质量、性价比和速度排名。结论显示搜索预算的影响最大,从 1 轮提升到 25 轮大致让分数翻倍,成本增加 2.5 至 7 倍;模型差异平均 15 分,大于引擎差异的 10 分。用户可通过 web plugin、server tool、engine 和 max_tool_calls、max_results 等参数自行配置。

    Live Web Search Benchmarks: Pick the Right Engine, Depth, and Model for Your Agent

    cky decisions: take the native search some labs build in, or wire up a third-party engine like Exa, Parallel, or Perplexity? Is one search enough, and if not how long do I let the agent keep searching? Are more search turns worth the quality they buy? We built live leaderboards to help you decide the best search configuration with data. See the data on our new Benchmarks page. We benchmark all the combinations to find strengths and weaknesses When setting up a search request, you have four decis

    匹配字段正文

星期五

  1. The Register

    测试游戏显示人工审批漏掉约三分之一危险 AI 编码智能体请求

    比利时开发者 Alex Wauters 制作的浏览器游戏让玩家在 60 秒内审批模拟的 Claude Code 权限请求,超过 4 万次运行、40.9 万条命令的数据显示,平均约三分之一的恶意命令被放行。最常被漏掉的是范围越权类请求,占比 35%,例如读取 Kubernetes 配置文件或 AWS 凭据;被漏掉最多的单条命令是 npm run analyze,近 65% 的玩家批准了它。Wauters 认为反复审批会带来疲劳,建议把编码智能体放进沙箱和云端 devcontainer,并配合 auto mode 与钩子来拦截风险动作。

    You wouldn't let Claude Code cat your AWS credentials or Kubernetes config on request, would you? A browser-based game designed to test humans' ability to safely approve AI coding agent requests suggests humans in the loop aren't as good at spotting dangerous commands as one might hope, with players approving roughly one in three malicious requests on average. The results also suggest that repeatedly having to approve an agent's actions can lead to sloppy decisions. It’s a quick, simple game on

    匹配字段正文

星期五

  1. NVIDIA Developer · Generative AI精选

    NVIDIA AI Red Team 总结部署更安全 AI 智能体的四种方式

    NVIDIA AI Red Team 在六个月内评估了多个 AI 智能体,归纳出四类反复出现的失效模式:缺少访问控制、工具允许任意代码执行、缺少网络出口控制、密钥以明文暴露。团队指出基于提示词的护栏和 LLM-as-a-judge 模式常被社会工程、渐进式操纵和恶意包安装等合法工作流绕过,有效防护需要模型控制面之外的确定性控制,包括严格访问控制、Docker 或 NVIDIA OpenShell 等加固沙箱、默认拒绝的网络出口以及通过专用密钥管理器让密钥远离智能体。

    I / Cybersecurity English 中文 The NVIDIA AI Red Team shares how access controls, sandboxing, network egress restrictions, and secret management can reduce the risks of deploying AI agents at enterprise scale. AI-Generated Summary The NVIDIA AI Red Team assessed multiple AI agents over the past six months and identified four recurring failure modes: lack of access control, tools enabling arbitrary code execution, missing network egress controls, and secrets exposed in plaintext. Prompt-based guard

    匹配字段正文

星期四

  1. Figma AI / Agent / Make

    Figma 如何用智能体守护内部系统安全

    Figma 安全工程团队公开了其内部安全智能体系统,用 RAG 检索历史告警与调查上下文,再由 Tines 上的智能体调用 Okta、Wiz、Slack、Panther 等工具完成告警分诊,并可查询安全数据湖、提交修复 PR。团队称复杂告警的解决时间缩短约 70%,值班呼叫量因 AI 驱动的严重度降级减少 20%,端点软件审批请求减少 25%。系统将记忆分为案例记忆、引导记忆和过程记忆三层,并用确定性护栏限制智能体行为,例如所有 PR 自动设为草稿。

    A split-background abstract illustration. The left side is black with a blue diamond, an orange floral motif, scattered orange squares, and bold graphic accents in magenta and olive green. The right side is teal with stacked horizontal pill shapes in orange, blush pink, and dark teal, punctuated by small blue and pink circles.

    Inside Figma; Engineering; Security Our security team built an AI agent that triages alerts, conducts forensic investigations, queries our security data lake, writes code to fix issues—and remembers what it learns. Here's how we cut alert time-to-resolution by 71% and fundamentally changed how our on-call engineers work. Share How we secure Figma’s internal systems with agents Illustrations by Jimmy Simpson When it comes to protecting our internal platforms, the threats we defend against on Figm

    匹配字段正文

星期二

  1. Trail of Bits Blog

    Trail of Bits 如何用 Codex 的 /goal 在 Patch the Planet 中找漏洞

    Trail of Bits 分享了在 Patch the Planet 项目中用 Codex 的 /goal 功能挖掘开源软件漏洞的三条经验:让 Codex 自己写目标提示词、只定义结果不规定路径、每个智能体只分配一个目标。团队把威胁模型文件作为目标提示词的核心输入,并指出把找漏洞和覆盖率放进同一个提示词会导致优化不均,改为先让 Codex 找出五个最有希望的攻击面,再为每个攻击面单独开一个 /goal 会话。工程师 Kevin Valerio 基于 /goal 搭建了针对 Rust 编译器的自动化变体分析流水线,所有提交给 Patch the Planet 的 Rust 漏洞都出自该系统。

    “Figure 3: Rust maintainers assumed we had a team of engineers working on finding bugs. It was just one engineer with a strong handle on Codex’s /goal.”

    Trail of Bits July 28, 2026 open-source , vulnerabilities , machine-learning Page content 1. Let Codex write the goal 2. Define the outcome, not the path 3. Assign one outcome per agent Where human judgment is needed Codex’s /goal feature amplifies bug hunting, but getting good results requires the right prompt, the right scope, and the right number of outcomes per run. For Patch the Planet , our joint initiative with OpenAI to find and fix bugs in open-source software, we pointed Codex at some

    匹配字段正文

  2. Cartesia 产品与研究

    Cartesia 解析如何判断 TTS 模型是否真正优秀

    Cartesia 发布技术博客,系统拆解 TTS 模型评测的多维挑战,指出 WER 饱和、上下文正确性、文本归一化、自动质量分数局限、人工评测偏差、长音频与流式失败模式、领域差异及多语言难点。文章强调 TTS 质量不是单一维度,需按产品体验构建多维评测,并介绍了 Cartesia 在低延迟、清晰度、自然表达、上下文正确性、一致性和流式鲁棒性上的优化方向。

    sounds to humans WER is a necessary metric for many use cases, especially those involving alphanumerics that are not words. But WER is rarely sufficient for enterprise-grade voice agents. 3. Contextual correctness is another challenge Many errors require semantic disambiguation to even define correctness: “read” (present vs past); “lead” (metal vs verb); “Polish” (nationality vs verb); “bass” (fish vs instrument); “live” (verb vs adjective); years like “2026” (twenty-twenty-six vs two thousand t

    匹配字段正文

星期日

  1. Together AI Blog

    Together AI 对比 Kimi K3 与 GPT-5.6 Sol 在 DeepSWE 上的表现与路由策略

    Together AI 在 DeepSWE 上对比 Kimi K3 与 GPT-5.6 Sol:Sol 以 72.7% 拿下 pass@1,Kimi K3 以 89.4% 拿下 pass@4,且每次 rollout 成本 4.65 美元对 8.37 美元。两者逐任务相关性仅 0.46、失败方式不同,先用 Kimi K3 再在测试套件拒绝时升级到 Sol 的级联可达约 85.6%,高于任一单模型和完美一次性路由的 83.4%。两者合计覆盖 113 个任务中的 108 个,剩余 5 个需引入第三个模型。

    (pass@1 72.7% vs 68.5%) and solves more tasks four-for-four. Kimi K3 wins pass@2 and pass@4 and costs far less, so it is the stronger value pick for high-volume or retry-tolerant agent work. For most teams the best answer is to route between them. In our run, Kimi K3 cost \$4.65 per rollout versus \$8.37 for GPT-5.6 Sol, a little over half the price. Measured per solved task, Kimi K3 returned 14.7 solves per \$100 against Sol's 5.3, about 2.8x the work per dollar. Yes, if you can verify results

    匹配字段正文

星期五

  1. Anthropic:Claude.dev 开发者博客精选

    Claude 5 代模型的上下文工程新规则

    Anthropic 总结了面向 Claude 5 代模型和 Claude Code 的上下文工程方法,称其删减超过 80% 的 Claude Code 系统提示词后,编码评测未出现可测量的损失。新方法强调让模型运用判断、设计更具表达力的工具接口,并通过 Skills、延迟加载工具和文件树渐进披露上下文。Claude Code 还提供 claude doctor,可用 /doctor 精简 Skills 和 CLAUDE.md 文件。

    One assembled context holding a system prompt line “leave documentation as appropriate”, a skill line “do not add comments”, and a user request “just make it work like the old one”.

    We removed over 80% of Claude Code's system prompt for more advanced models. How to apply the lessons we learned to your own context engineering in Claude Code and with your own agents. I’ve written previously about how to best prompt the newest generation of Claude 5 models and work with them iteratively to discover what you want to build. But when you send a message to Claude, the prompt is only a small part of the context it gets. Much of your context is assembled from your system prompt, Ski

    匹配字段正文