Glean 拾遗
Recent picks

2picks · chronological

11-13

Graph Engineering: Building a CI Triage Agent Graph

A how-to for replacing a single agent loop with a graph of specialists: nodes each own one verb and a scoped context, edges are deterministic routing code, a shared state file carries history across runs, and a gate decides done or not done. The worked example is a GitHub Actions failure triage system, with copy-ready agent definitions for a classifier and a bug fixer, edge rules that keep hard constraints out of prompts, a STATE.md layout, and a test-gate prompt. Autonomy is staged from manual /goal to scheduled /loop to cloud Routines. The author concedes most teams should not build one yet, and names comprehension debt as the cost of a graph that ships code nobody reads.

11-09

Harness, Loop, Graph: Which Layer Actually Broke Your Agent

The author splits agent failures into three layers: the harness (everything around the model — tools, memory, permissions, traces), the loop (a check that can genuinely fail, plus feedback and exits), and the graph (dependencies and state handoff between loops). The claim is that each layer fixes a different class of failure, and that most engineers burn weeks editing prompts or swapping models when the real defect lives elsewhere. Concrete patterns include a task contract with an explicit done_when field, an AGENTS.md file that acts as a map instead of a manual, retry loops that exit when the same evidence appears twice, and an early-start test that removes fake arrows between steps. The author concedes most tasks should collapse back to a single loop, and that drawing a twelve-node graph first is a common mistake. Suited to engineers building agent workflows. Second-hand synthesis, no original measurements.