与「SCOPE」相关的搜索结果

开发系统最极致高效的Agents.md，没有之一： # AGENTS.md ## Core Principles - Choose the simplest implementation that fully satisfies the current requirements. Avoid unnecessary abstraction, configuration, indirection, or speculative extensibility. - Make the smallest necessary change that fixes the root cause. Do not refactor unrelated modules or change strategy semantics unless explicitly requested. - Grow the system in layers. Start from the smallest working end-to-end version and add new capabilities incrementally. Never replace a working system with unfinished complexity. - Reuse existing project components before creating new ones. Prefer extending proven modules over introducing parallel implementations. - Prefer well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear benefit. - Keep components modular with clearly defined responsibilities. Avoid unnecessary coupling between strategy logic, execution, accounting, replay, and infrastructure. - Design for long-term maintainability once a feature or strategy has been validated. Do not over-engineer speculative ideas before evidence exists. --- ## Strategy Development - Validate hypotheses with historical replay before introducing forward-only logic whenever historical validation is possible. - Every trading strategy must progress through Replay → Shadow → Canary → Live. Do not skip validation stages. - Base design decisions on measurable evidence rather than intuition. Optimize only after demonstrating that an edge exists. - Treat every strategy as an independent contract. Do not silently alter frozen behavior without explicit authorization. --- ## Existing Systems - Do not break running Shadow or Live systems for unrelated work. - Preserve compatibility only when required by active production or validation workflows. Otherwise, remove obsolete code instead of accumulating compatibility layers. - Reuse existing infrastructure whenever possible, including replay engines, accounting, execution, wallet management, order book handling, logging, monitoring, and daemon frameworks. --- ## Engineering Standards - Prefer deterministic behavior over hidden automation. - Fail loudly when assumptions are violated. Do not silently ignore errors or fall back to unexpected behavior. - Keep configuration minimal. Introduce new configuration only when behavior genuinely needs to vary. - Remove dead code instead of leaving unused paths behind. - Write code that is easy to inspect, replay, test, and reason about. - Keep implementation consistent with existing project architecture unless an architectural change is explicitly requested. --- ## Scope Discipline - Implement only the requested scope. - Do not introduce unrelated optimizations, redesigns, migrations, or feature expansions. - Non-blocking findings outside the requested scope may be noted separately but must not be merged into the current task. - Consider a task complete once its agreed acceptance criteria are satisfied. Treat subsequent improvements as separate work items.

Grok Build keeps getting smarter.....this update expands Auto mode, gives developers more control over Bash permissions, speeds up /btw, and makes long conversations easier to navigate Release Notes: v0.2.119 Features: • Always allow for bash commands now lets you edit a free-form glob pattern instead of only word-prefix scopes. • Long responses now show a clickable arrow that jumps back to the start of the answer. • Auto mode now auto-approves more common read-only git commands and harmless file appends. • Plan previews now show Mermaid diagram buttons (Open Image, Copy Image Path, Copy Source). Bug Fixes: • Gateway connections now detect and recover from dead sockets more reliably. • Question cards now let you Tab through answers instead of losing focus to the scrollback. • Resume picker no longer tries to load a session from pasted garbage when you press Enter. • Background task completion messages no longer grow unbounded when the task produced a huge log. • Plan viewer scrollbar now responds to clicks on the border column and renders without dark stripes in • Expired external auth provider credentials now correctly trigger the interactive sign-in flow instead of a silent 401 loop. Performance: • /btw side questions now reuse the parent session’s cached prefix for faster responses. • Doctor and tmux-backed startup are now faster when no live tmux processes remain.

给关注了半年的agent team 交份作业。 这是一篇2w字长文，也是一份 Agent Team 的最佳实践。 01 一个 Agent，是怎么变成多个 Agent 的为什么真实工作会把 Task Agent 推向 Long-running Agent；为什么一个越来越好用的 Agent 最后又必须分化；多个 Agent 出现以后，瓶颈为什么会转移到 Human。 02 先让“谁负责什么”离开 Human 的脑子Agent 怎样获得稳定身份、Domain 和 Scope；Human 与 Agent 怎样查询当前 Team 的责任结构；真实协作又怎样逐渐沉淀为 Organization 与 Collaboration。 03 让 Agent 自己开始协作Agent Message 带来了什么变化；一个 Agent 怎样把工作直接交给另一个 Agent；为什么 Agent 沟通不是一次把一切说完。 04 Message 负责沟通，Topic 负责收口当工作跨越多个 Agent、多个 Turn 和多天以后，怎样保留唯一的当前版本；Responsible、Participant、Artifact 和 Needs You 分别解决什么问题。 05 Overview：让一支持续变化的 Agent Team 变得可治理当 Human 不再阅读每个 Agent 的全部过程，怎样从更高层观察 Team；怎样发现等待、积压和瓶颈候选；为什么治理关注的是工作流动，而不是让每个 Agent 看起来都很忙。 06 Agent Team 怎样进入真实的外部关系为什么把 Agent 接入 Slack、飞书还远远不够；Agent 对外以后，身份、角色、信任、权限和现实后果为什么必须被分别治理。 07 CodexLoom 在织什么Multiple Agents 与 Agent Team 的真正分水岭是什么；Human 在 Team 中的新位置是什么；为什么需要稳定的 Agent 和动态的 Team。

Our first Kite demo was ChatGPT ordering Uber Eats for you. It never got past the login screen. Uber's CAPTCHA was built for humans, and agents cannot pass it. On @gracegongGG's Venture with Grace, our Co-Founder & CEO @ChiZhangData traced how that moment shaped the way we design Kite. ▷ The demo died at the login, not at ordering or paying. The blocker was proving the agent was allowed to be there at all. Spinning up a browser extension to click through the CAPTCHA works, but it is a temporary stage of how agents and the internet should work together. ▷ The permanent path is identity. Every agent needs to prove who it is and where it comes from, carrying who its human or organization principal is, what its purpose is, and the exact authorization scope for that session or request. An agent showing up with no reason is either hallucinating or attacking you. ▷ Where this is heading: an API-first agentic internet, where headless agents authenticate without human login credentials. x402 and MCP are already marching toward that. Kite Agent Passport is that identity layer: verifiable identity, delegated authority, and permissions scoped per session. No more "prove you're human." 🪁

SAMSUNG’S $200B BROADCOM DEAL IS BIGGER THAN A MEMORY SUPPLY CONTRACT. 📊 Samsung Electronics $005930 and Broadcom $AVGO have agreed to pursue more than $200B of semiconductor cooperation through 2030, covering HBM, advanced foundry manufacturing and packaging. Reuters separately confirmed the $200B Samsung–Broadcom portion of the wider Korea–US semiconductor agreements. The headline number is huge, but the strategic shift matters more. Samsung is trying to move from being viewed as a component supplier to becoming a full-stack AI semiconductor partner: Memory → Foundry → Advanced Packaging The reported scope includes HBM4 and HBM4E for Broadcom’s AI accelerators, sub-2nm foundry processes for key chip products, and integrated support from design optimization through packaging and mass production. That matters because Broadcom is one of the central players in custom AI accelerators and high-speed data-center networking. If this MOU converts into real production orders, Samsung would capture more value from each AI chip—not only memory revenue, but also manufacturing and packaging economics. For the Korean market, Samsung is the clearest direct beneficiary. Equipment, materials and packaging names may follow, but only after capacity expansion, supplier participation and actual purchase volumes are confirmed. I would not treat the entire $200B headline as booked revenue yet. This is still an MOU. The real revaluation depends on: → Final contract volumes → Product and process allocation → Production timing → Pricing and margins → Whether orders translate into utilization and earnings The headline creates expectations. Execution is what creates the rerating. $005930 $AVGO For reference only. This is not investment advice. Avoid excessive leverage, do not chase sharp moves and maintain strict risk management.

The machine economy does not begin when robots get smarter. It begins when a machine can be paid to do something, and every party involved can prove what happened. Made with @FabricFND. Two systems meet in the middle of it: Agent Passport issues the agent a verifiable identity and a spending authority its owner defines, and RoboPay actuates a robot after the payment behind the request checks out. What happens before the robot moves: ▷ Authority is granted once, and it is bounded. The human signs a spending session with a passkey: a total budget, a per-transaction ceiling, the assets allowed, and an expiry. The agent holds no card number and no wallet key. It holds a delegation it cannot exceed. ▷ Two payments, because these are two different obligations. One settles with the merchant for the goods. A separate x402 payment pays the robot for the work of moving them. Buying a thing and hiring a machine to carry it are not the same transaction, and the receipt keeps them apart. ▷ Verification comes before motion. The request arrives with an x402 payment header. The facilitator checks the network, the price, the payee wallet, and the signed payload. Only then are the transaction details sealed onto the robot action event and the command published. Until that clears, the robot sits still. ▷ Every step leaves a receipt. Identity, scope, approval, both payments, verification, dispatch. When you need to know why a machine did something, the answer is a record rather than a guess. (This run was executed in a demo environment.) Agents have been paying for software for a while now. Paying for physical work is a harder problem, because a delivery cannot be rolled back. The guarantee has to sit in front of the action instead of behind it. Authorization before payment, payment before motion: that ordering is what makes it safe to let autonomous systems spend in the world we live in. It is also the layer the machine economy has to get right before anything else in it can work. Scoped by Kite. Verified by RoboPay. Delivered in the real world. 🪁

Hermes Studio v0.6.32 新版本发布 本版本涵盖 0.6.31 之后合并的全部 14 个 PR，聚焦会话分类与压缩、群聊、Workflow 路由、Skill Bundle、Ekko 记忆、Hermes 0.19 和桌面窗口界面 群聊 @mention 现在可在 CJK 文本、Emoji 和标点后正常触发；房主也可在房间设置中查看、生成和轮换邀请码 Workflow 在 handoff 和重新连接过程中会保留每次 Hermes Bridge 运行的来源；Scoped Codex 和 Claude Code 节点也可为有效 API Key 目标使用 launcher 支持的协议 会话新增全局分类、更准确的 Markdown 感知搜索排序，以及在编辑、分支和并发运行中保持正确并限制历史范围的游标压缩；完整压缩方案也已形成文档 现在可直接在聊天中创建、浏览、运行和删除 Profile 级 Skill Bundle，并清楚查看其中包含的 Skill Ekko 记忆改用 Profile 隔离的单一规范模型，支持 revision 校验的精确修改、更完整的来源审计和更严格的相关性过滤 Hermes 0.19 的助手中间消息会以独立气泡实时显示并保存；普通单聊也可异步投递持久化的后台委派结果 新的桌面 Runtime 构建、后备路径和 Windows CLI shim 现在默认使用 Hermes Agent 0.19.0 桌面窗口控件已融入页面框架：macOS 红绿灯位于侧边栏，Windows 控件位于主内容上方，Linux 继续使用原生窗口装饰 开发文档现在同时支持直接使用当前 checkout，并可按需采用隔离的 Git worktree

Codex Code Review can now use custom repository rules in AGENTS.md. Start with a check your reviewers keep repeating. Keep it concise and scoped so Codex can catch repository-specific issues even when the relevant context is siloed.

Democratic Rep. Jamie Raskin is launching an investigation into whether Jeffrey Epstein acted as an unregistered foreign agent for multiple countries, requesting records from the Trump administration on the scope of the late convicted sex offender's foreign ties.