Security安全

AI Agent Identity: Why Shared Employee Keys Explode Blast RadiusAI Agent 身份:为什么共享员工密钥会放大爆炸半径

Treat each AI agent as its own principal—scoped tokens, delegated permissions, one-agent revoke. Compare Mintive, Okta Govern AI Agent Identity, and WorkOS Agent Auth; draw the boundary vs an MCP gateway.把每个 AI agent 当作它自己的主体:范围受限的令牌、委托权限、单 agent 吊销。对比 Mintive、Okta Govern AI Agent Identity 与 WorkOS Agent Auth,并划清其与 MCP gateway 的边界。

Privacy隐私

Claude Self-Assessment Privacy: A Decision Guide by Account TypeClaude Self-Assessment 隐私:按账户类型的决策指南

Stop guessing from viral 'digital snitch' posts. Decide by account type whether self-assessment runs, what retention applies, how Cyber Verification handles research false positives, and why Claude Code telemetry is not server-side assessment.别再凭疯传的「数字告密者」帖子去猜。按账户类型判断 self-assessment 是否运行、适用何种保留、Cyber Verification 如何处理研究误报,以及为什么 Claude Code 遥测不是服务端评估。

Developer Tools开发工具

Coding-Agent Hooks Hygiene: Which File Still Owns the Entry编程智能体的钩子卫生:哪个文件仍拥有这条条目

Decide which file owns a third-party hook, which official unload removes it, and which managed hooks a user disable cannot turn off after an orchestrator or desktop installer rewrites Claude, Codex, Cursor, or Copilot config.在编排器或桌面安装程序改写 Claude、Codex、Cursor 或 Copilot 配置之后,判断哪个文件拥有第三方钩子、哪一次官方卸除能移除它,以及哪些受管钩子无法被用户禁用关掉。

Developer Tools开发工具

Parallel Coding-Agent Conflicts: Intent Claims vs Contracts vs Ownership并行编程智能体冲突:意图声明、契约与所有权

Decide which parallel-agent conflict class you are solving before spinning N worktrees. Compare deterministic intent claims (scope+operation), contract-first merges, ownership orchestration, and LLM mutual review—with Foremerge as a worked case, not a launch post.在拉起 N 个工作树之前,先判断你要解决的是哪一类并行智能体冲突。比较确定性意图声明(范围+操作)、契约优先的合并、所有权编排,以及 LLM 互审——以 Foremerge 作为实例,而不是发布帖。

Security安全

Playwright Chromium Lag for Coding Agents: A Recurring Trust Problem, Not a One-Off CVE编程代理的 Playwright Chromium 滞后:反复出现的信任问题,而非一次性 CVE

Chrome ships fixes; Playwright pins Chromium later. Decide by workload—own-app E2E, agent untrusted browsing, Playwright MCP—using chromiumSandbox, channel chrome, non-root hosts, and egress allowlists. A decision matrix for Claude Code, Cursor, and MCP.Chrome 发布修复;Playwright 稍后才固定 Chromium。按工作负载做决定——自有应用 E2E、代理不受信任浏览、Playwright MCP——使用 chromiumSandbox、channel chrome、非 root 主机与出站允许列表。一份面向 Claude Code、Cursor 与 MCP 的决策矩阵。

Security安全

pull_request_target Default Block: A Dec 2 Migration Runbookpull_request_target 默认拦截:12 月 2 日迁移操作手册

Public GitHub repos block pull_request_target by default on December 2, 2026, with brownouts on November 9 and 16. Inventory workflows, switch CI to pull_request, and allow the trigger only for jobs that never execute fork code.公开的 GitHub 仓库将于 2026 年 12 月 2 日默认拦截 pull_request_target,并在 11 月 9 日与 16 日进行限时中断。盘点工作流,将 CI 切换到 pull_request,并仅对从不执行 fork 代码的作业放行该触发器。

Security安全

Shared Firefox Sessions for Coding Agents: When Kitsune-Style MCP Is Worth the Blast Radius面向编程智能体的共享 Firefox 会话:Kitsune 式 MCP 何时值得承担爆炸半径

Decide when a coding agent should share your real Firefox logins versus driving a separate automation browser. Compare Kitsune, firefox-bridge, Playwright MCP, and Claude in Chrome on session model, profiles, and approval gates—without pretending modes stop prompt injection.判断编程智能体应共享你真实的 Firefox 登录态,还是驱动一个独立的自动化浏览器。在会话模型、配置文件与审批关卡上比较 Kitsune、firefox-bridge、Playwright MCP 与 Claude in Chrome,同时不要假装模式能阻止提示注入。

FinOpsFinOps

Coding-Agent Cloud Waste: How to Find and Contain What Your Agents Leave Running编程智能体的云浪费:如何发现并遏制智能体留下仍在运行的资源

Coding agents create VMs, databases, and deploys mid-task—then sessions end without teardown. A practical FinOps playbook for read-only audit, human-confirmed cleanup, Claude Code/Codex/MCP blind spots, and what --verify can (and cannot) prove.编程智能体会在任务中途创建虚拟机、数据库和部署,然后会话结束却没有拆除。一份实用的 FinOps 实操手册,涵盖只读审计、经人工确认的清理、Claude Code/Codex/MCP 盲区,以及 --verify 能够证明什么、不能证明什么。