Glean 拾遗
中 EN
Submit a link
Daily · timeline

A few picks a day.

Tue, Aug 4, 2026 3picks
← 08-03
Calendar ▾
2026 · 08
MoTuWeThFrSaSu ·····12345678910111213141516171819202122232425262728293031
has picks today
06:00

Automating cross-repo docs with GitHub Agentic Workflows

跨仓库文档自动化：Aspire 团队把文档 PR 中位耗时压到 44.8 小时

The 10-person Aspire team automated cross-repo documentation with GitHub Agentic Workflows. Workflows are authored as one Markdown file: the agent evaluates whether a merged PR needs docs, drafts content in a checked-out aspire.dev workspace, and emits JSON intent; a separate safe-outputs handler materializes writes with a GitHub App scoped to exactly two repositories. Over Aspire 13.3/13.4, 396 merged product PRs produced 82 docs PRs, all merged with a 44.8h median and SME review from the original feature's engineer. The key enabler: milestone titles resolve the target docs branch before the agent wakes. Draft-only PRs, protected files, and allow-listed base branches keep the action surface crisp. The post is honest about v1's 13% false-positive gate and prompt-budget limits on large diffs. Practical for teams shipping docs from a separate repo.

github.blog · 14 min · Agentic Workflows · Agents · AI Engineering · Documentation
06:00

Improving token efficiency in GitHub Agentic Workflows

GitHub 实录：给 Agentic CI 减负，用 CLI 替代 MCP 调用把 token 花销降 62%

GitHub's team instrumented its own fleet of Agentic Workflows through an API proxy, emitting a normalized token-usage.jsonl per run and building two daily agentic workflows—a usage Auditor and an Optimizer—that read those logs, flag anomalies, and file concrete optimization issues. The biggest wins came from pruning unused MCP tool registrations (each request can carry 10–15KB of schema overhead), replacing GitHub MCP calls with deterministic GitHub CLI invocations, and moving fixed data-gathering into pre-agentic setup steps. To compare across models they define Effective Tokens: ET = m×(1.0×I + 0.1×C + 4.0×O) with model multipliers. Of 12 production workflows, nine received optimizer changes; measured reductions were 62% for Auto-Triage Issues (109 runs), 43% for Security Guard, and 59% for Smoke Claude. One workflow regressed 5% due to workload shift, and one misconfigured bash allowlist caused a 64-turn fallback loop. The post argues for episode- and portfolio-level efficiency analysis.

github.blog · 18 min · Agent Engineering · CLI · Cost Optimization · Mcp · Observability
06:00

When Coding Is Not the Bottleneck: Three Levels of Software Autonomy

当编码不再是瓶颈：软件自主开发的三级框架与责任转移

This article adapts a position paper by UC Berkeley RDI researchers, proposing a three-level framework for autonomous software development: code autonomy, pipeline autonomy, and demand autonomy, plus three orthogonal dimensions—specification granularity, temporal autonomy, and oversight mode. It contrasts a concrete win (16 parallel Claude agents building a working C compiler for under $20k) with the observation that frontier agents still degrade sharply on benchmarks that test continued evolution rather than isolated tasks. The authors argue that the immediate industry risk is skipping levels: teams claim level-1 review but merge AI code unchecked, or adopt pipeline autonomy without the needed verification and governance. As coding stops being the bottleneck, requirement specifications, agent audits, and accountability mechanisms displace raw coding skill. Useful for engineers and engineering leaders thinking about agent-driven development and governance.

www.pingwest.com · 8 min · Agents · AI Engineering · LLM · Software Engineering