Glean 拾遗
Recent picks

5picks · chronological

11-15

Why Cloud Agents ignore /poteto-mode — and how to vendor pstack

A field guide to running pstack (Lauren Tan's engineering-standard plugin) across Cursor's split setup: Grok Bot coordinates and spawns, Cloud Agents do the work in isolated VMs and open PRs. The failure mode it targets: account plugins and ~/.cursor/skills are not copied to the cloud VM, so /poteto-mode silently never loads. Fix is to sparse-checkout pstack's skills/ and agents/ and rsync them into the repo's .cursor/skills and .cursor/agents, keep those paths tracked in git, and give each runnable app its own verify-<app> skill so verification means launch/drive/evidence instead of the model asserting it looks fine. Also covers coordinator prompt templates, the permission gap between Autopilot-stack and Autopilot-full (the latter needs a fresh verifier's clean verdict before merge), and a pitfall list. For engineers already running Cloud Agents who want skill distribution and verification pinned down.

x.com · 9 min · Agent Harness · Agent Skills · Coding Agents
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-12

How the Claude Code team reviews 30,000 changes a day

Anthropic's Claude Code team describes its internal review pipeline, built for a repo where daily merged changes went from ~2,500 in May to over 30,000 in September. Review is split into six layers: runnable verification and a fresh-context subagent before the PR exists; a Claude reviewer on every PR that reads the diff against the whole repo and the stated intent, with findings voted on by several agents before posting; a security review that can block merge; CI; risk-tiered human approval (0/1/2 people) assigned by a classifier reading the change rather than the author; then merge queue, flags, internal dogfooding and one-step rollback. They also document the failure modes: one CLI PR ran more than fifty review rounds overnight, and git blame showed ~59% of flagged lines predated the reviewer's first pass, prompting a three-round cap and diff-only re-review. Useful for teams wiring agents into their own review flow.

claude.dev · 19 min · Agentic Coding · Claude Code · Code Review
11-11

Self-hosted workspace that assigns issues to AI coding agents

Multica is a source-available, self-hostable workspace that treats AI coding agents as team members. Instead of juggling separate terminal sessions, you assign an issue to an agent; it picks up the work on a runtime you control, comments as it goes, and hands back a diff for review. It drives 29 existing agent CLIs—Claude Code, Codex, Cursor, Copilot, Kimi, and others—rather than shipping its own model, so changing providers is a dropdown. The stack is a Go backend with PostgreSQL, a Next.js web app, Electron desktop, and Expo mobile clients. Execution logs, mid-run steering, usage analytics, review gates, and self-hosted Git integration keep humans in the loop. It targets engineering teams already running multiple coding agents who want shared assignment, audit, and review workflows instead of more terminal tabs.

github.com · 12 min · Agent Orchestration · Agent Workflows · Coding Agents
08-24

At AIEWF, AI Engineer Trends Shift from Autonomy to Harnessed Loops

At the 2026 AI Engineer World’s Fair, the conversation has moved from autonomous agents to harnesses, loops, and skills. Lilian Weng's new essay shifts from planning/memory/tool-use anatomy to harness engineering around the model. AutoGPT-era autonomy is out; engineers like OpenClaw's Peter Steinberger put themselves in an outer loop while agents run the inner loop. Enterprises are adopting forward deployed engineers who integrate long-running agents and software factories (Cursor, Warp, Vercel) with strict ROI targets. Google DeepMind's Philipp Schmid says "agents are just files" and Markdown-based skills extend capabilities; Matt Pocock warns of "skills hell" and advises fewer, smaller skills. Skepticism remains: HumanLayer's Dex Horthy says hype outruns discipline, and Geoffrey Huntley worries that "factories failed, loops failed" will be next year's refrain. A useful orientation for engineers tracking AI development tools and agentic workflows.

www.latent.space · 19 min · Agent Engineering · Agent Skills · Coding Agents