Glean 拾遗
Recent picks

4picks · chronological

11-13

The Harness Is the Machine: Seven Invariants for Agent Engineering

The essay argues that agent failures come from the environment around the model, not from prompts. It lays out seven harness invariants: bound the contract before the first token, feed the context window only AST symbol slices, quarantine writes in ephemeral git worktrees, persist state to disk as receipt.md, gate merges on compiler and test exit codes rather than model claims, strip credentials and network egress, and emit a machine-readable audit receipt per run. It cites a before/after on a multi-file refactor (18% completion bare, 89% with a harness), plus a .claude/rules YAML example, a pre-verify.sh sensor hook, and a receipt template. Useful for engineers wiring coding agents into CI, though the headline numbers are unsourced, the model version names are fictional, and the post ends with promotion.

11-09

The Harness Is the Machine: Task Contracts, Worktrees, Receipts

A long-form X post outlining a production architecture for coding agents. The thesis: when an agent fails a multi-file refactor, the problem is not the prompt or the model but the environment around it — the harness. The author lays out a seven-stage pipeline: Opus compiles a task_contract.json with path allowlists and a cost/turn/timeout budget; the harness spawns an isolated git worktree; Sonnet edits only inside the boundary; Haiku validates every tool call parameter; a separate model acts as adversarial skeptic against the diff; a pre-commit hook checks test exit codes and signs a receipt.json; failures crystallize into rules, skills, and regression evals. Includes contract schema, isolate_worktree.sh, pre-tool.sh, receipt format, and a 10-point pre-flight checklist. Caveat: the Opus/Sonnet/Haiku/Fable 5.5 model names and the 18%→95% success numbers are unsourced, and the post ends with a Telegram funnel link.

x.com · 20 min · Agent Engineering · Agent Harness · Claude Code
06-25

How 1 Claude Agent Runs 10 Others · 9 Steps Swarm Loop

This post breaks down a 9-step pattern for running multiple Claude Code subagents in parallel without chaos. The key insight is that launching many agents is easy and usually messy; the skill is in the orchestration loop: verify the task is splittable, have the lead agent decompose it into atomic subtasks with human approval, isolate each agent via Git worktrees to prevent file collisions, then fan out in parallel. A SubagentStop hook gates every result (tests + lint), a grader scores each against a rubric and automatically sends weak ones back for revision, and finally only the lead agent merges passing results in dependency order. The entire loop can be packaged as a reusable skill or slash command.

06-02

A Multi-Agent IDE to Run Claude Code, Codex, and Others in Parallel Git Worktrees

Orca is a desktop and mobile IDE designed to run multiple AI coding agents—such as Claude Code, Codex, and Grok—concurrently. It leverages Git's worktree mechanism to give each agent an isolated working directory, eliminating the need for stashing or branch juggling. Users can observe and control all agents from a single interface with tabbed panes, built-in diff review, and direct GitHub Issue/PR integration. It's built for developers who rely on CLI-based coding agents and need to handle multiple features or refactors in parallel.

github.com · 9 min · Agents · Ai Tooling · CLI