写作
安全与隐私
筛选文章 安全与隐私
安全与隐私
第 3 页 · 12 / 72-
Company Brain separates team memory permissions Company Brain scopes team-agent memory by room and user permissions, with personal authorization, traceable sources, and separate tool-write access.
-
Company Brain:团队 Agent 的记忆权限该怎么拆 拆解 Company Brain 的团队记忆与权限设计,重点看个人授权、共享知识、可追溯来源和团队 Agent 的权限边界。
-
Agent 已获网络权限,为什么连接途中还要继续检查 从 Codex 网络策略更新出发,解释 HTTP 重定向、长响应与 WebSocket 为什么需要可撤销许可,以及工具权限和网络权限为什么必须分层。
-
Why agent network permissions need ongoing checks Codex network policy changes explain revocable permits for redirects, long responses, and WebSockets, and why tool and network permissions need separate layers.
-
AI Agent engineering reading list, Sep 25–26, 2026 Seven updates on token efficiency, Codex networking, Copilot Memory, local agent server security, self-practice, skills, and reproducibility.
-
2026-09-25 至 09-26|AI Agent 工程阅读清单 7 条 AI Agent 工程更新,覆盖长任务 Token 优化、Codex 网络策略、Copilot Memory、本地 Agent Server 安全和 Self-Practice。
-
GitHub Agentic Autofix starts retaining repair experience GitHub Agentic Autofix reads and writes Copilot Memory. How security repair knowledge crosses agent workflows, and why verification, scope, and expiry matter.
-
GitHub Agentic Autofix 开始积累修复记忆 GitHub Agentic Autofix 会读取并写入 Copilot Memory。本文拆解安全修复经验如何跨 Agent 复用,以及验证、范围和过期为什么重要。
-
AI agent engineering reading list | 2026-09-24 to 09-25 Five updates on proactive safety intervention timing, state revision, TeamHarness, enterprise MCP permissions, and tool-result handling.
-
2026-09-24 至 09-25|AI Agent 工程阅读清单 5 条 AI Agent 工程更新,重点看主动安全介入时机、状态修正、TeamHarness、企业 MCP 权限边界和 Tool 结果处理。
-
GitHub Security Lab makes fuzzing an agent feedback loop GitHub Security Lab Fuzzing Taskflow uses coverage gaps to guide model decisions while deterministic tools execute, measure, and persist results.
-
GitHub Security Lab 把 Fuzzing 做成 Agent 反馈环 拆解 GitHub Security Lab 的 Fuzzing Taskflow,模型根据 coverage 缺口决定下一轮,确定性工具继续负责执行、测量与持久化。