Glean 拾遗
Daily · timeline

A few picks a day.

Fri, Sep 4, 2026 3picks
← 09-03
Calendar ▾
2026 · 09
MoTuWeThFrSaSu ·123456789101112131415161718192021222324252627282930
has picks today
09-07 →
06:00

Anatomy of Effective Commerce Agents: A Production Guide

生产级电商 Agent 的工程解剖:单一 Agent + Skills,UI 组件工具化,安全交给 harness

Anthropic distills a year of building Claude-based commerce agents with retailers, travel, and telecom customers into a production playbook. It argues against intent routers and domain-split subagents: commerce sessions are tightly coupled across intents, and handoffs lose state, add tokens, and increase latency. Instead, one agent in a standard loop with skills for the long tail outperforms both one-prompt and subagent designs. UI output should be modeled as presentation tools — typed tool calls, not client-parsed custom tags — at the cost of streaming granularity. Latency is attacked on end-to-end and perceived fronts; prefix caching with a global/session/volatile layout can sustain 90–99% hit rates. Memory facts are written asynchronously by a separate extractor into your database (13% higher recall in their commerce eval), then read in three layers. Safety is enforced in the harness: model-originated writes are only staged and need approval, only server-issued IDs are accepted, and third-party content is sanitized. Evals are snapshots, not simulated-user conversations, with paired positive and negative cases. An open-source reference implementation, anthropics/commerce-agents, is included.

06:00

Management Is the AI Superpower: Know What to Ask For

管理是新的 AI 超能力:写清目标,剩下交给 Agent

In an experimental UPenn EMBA class, students who had never coded were asked to build a startup from scratch in four days using Claude Code, Google Antigravity, ChatGPT, Claude, and Gemini. The author estimates their output was roughly an order of magnitude further along than a full pre-AI semester used to produce. The lesson: once AI can execute fast and cheaply, the scarce skill is delegation — specifying what 'done' means and judging whether the result is good. He proposes a trade-off among human baseline time, the AI's probability of success, and AI process time (prompting, waiting, checking). Applying OpenAI's GDPval numbers, experts took seven hours on tasks where GPT-5.2 now ties or beats them in 72% of evaluations; with an hour of review, expected savings are about three hours per task, with failed attempts costing more. He also notes that PRDs, five-paragraph orders, and deliverable specs work naturally as agent instructions. Useful for team leads and domain experts adopting agents.

www.oneusefulthing.org · 13 min · Agents · AI · Management · Productivity
06:00

Writing Code Is Easy. Reading It Isn't.

生成代码太容易,真正的成本是读懂它

Drawing on years of contract work, the author argues that the real cost of software lives in reading, not writing: every codebase demands a mental model, built by tracing function definitions, return types, database paths, caches, error handling, and call sites. Understanding one getUserPreferences-like function often means opening five other files. Because LLMs can now emit code faster than anyone can consume it, they enlarge the reading burden; the lawyer who filed fictitious ChatGPT-sourced cases failed not at generating but at verifying through reading. The practical conclusion is to point AI at comprehension—explaining existing code, uncovering side effects, compressing context—rather than at producing bigger diffs. Team throughput should be measured by how quickly members construct accurate mental models, not by lines generated. A grounded opinion piece for engineers who want AI assistance without mistaking output volume for velocity.

idiallo.com · 6 min · AI Engineering · Developer Tools · LLM · Software Engineering