写作
学习指南
筛选文章 学习指南
学习指南
第 2 页 · 12 / 36-
Why pinning a Git SHA can still run different code Plugin4Shell exposes a supply-chain gap: a pinned SHA records the expected version, but installers must also verify the actual HEAD after checkout.
-
固定 Git SHA 为什么还可能跑到别的代码 Plugin4Shell 暴露了一个供应链边界:固定 SHA 只写下期望版本,安装器还必须在 checkout 后验证真实 HEAD。本文结合 Git 文档、本地无害复现和 GitHub 分支限制解释机制。
-
When to split a task across agents: check dependencies How task dependencies shape multi-agent results, with SAIGE experiments, ablations, and OpenAI guidance for deciding when to delegate.
-
一个任务什么时候该拆成多个 Agent?先看依赖关系 Rethinking Multi-Agent Collaboration 说明多 Agent 的收益取决于任务依赖结构。本文结合 SAIGE 主实验、消融实验和 OpenAI 多 Agent 工程建议,整理可执行的委派判断。
-
Why you cannot just rerun an agent after a crash WorkflowAgent, step boundaries, and idempotency keys explain safe recovery after crashes, timeouts, and human pauses, with a proposed Lora PI Kit adaptation.
-
Agent 跑到一半进程挂了,为什么不能直接重跑? 用 WorkflowAgent、Step 边界和幂等键解释 Agent 在崩溃、超时和人工暂停后怎样安全恢复,并给出 Lora PI Kit 的迁移思路。
-
Where agent credentials belong: host, vault, and broker Where keys belong when coding agents call GitHub, databases, and cloud APIs, and how vaults and credential brokers define access boundaries.
-
Agent 的生产密钥该放哪里?Host Boundary、Vault 与 Broker 解释 Coding Agent 调用 GitHub、数据库和云 API 时,应用密钥、执行器密钥和第三方凭据该放在哪里,以及 Vault 与 Credential Broker 的边界。
-
Why more agent tools can mean worse tool selection How Tool Search loads definitions on demand, affects prompt caching, and differs from MCP connections and ARD resource discovery.
-
Agent 工具越接越多,为什么反而更容易选错?读懂 Tool Search、MCP 与运行时发现 解释 Tool Search 如何按需加载工具定义,为什么它会影响 Prompt Cache,以及 MCP、Tool Search 和 ARD 分别解决什么问题。
-
Should an agent keep going or start a fresh attempt? Use When Agents Slow Down, Reflexion, Hyperband, and agent evaluation to compare continued revision with independent attempts under reproducible budgets.
-
Agent 该继续跑,还是重新开一轮?读懂预算分配、记忆与评测 结合 When Agents Slow Down、Reflexion、Hyperband 和 Agent 评测,说明怎样比较连续修改与独立尝试,并设计可复现的预算分配实验。