Glean 拾遗
Recent picks

8picks · chronological

11-14

Your Coding Agents Made You a Manager

Addy Osmani maps engineering-management practice onto day-to-day coding-agent work: give the agent a definitive pass/fail check (tests, build exit codes, screenshots) instead of accepting "looks done"; write down only the context the repo cannot reveal — objective, constraints, out-of-scope items, success criteria; and once you have corrected the same thing twice, put it in CLAUDE.md or a shared skill. He borrows Grove's task-relevant maturity to explain Claude Code's split between requests (prompts, CLAUDE.md, skills) and requirements (hooks, deny rules, managed settings), arguing that over-process is the new micromanagement. The piece also lists five questions to answer before an unattended run, and is candid about where the analogy breaks: agents have a notebook rather than experience, rework is nearly free, and the human team still needs your time.

x.com · 22 min · Agent Workflows · Agentic Coding · AI Engineering
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

Shopify's 12-week rewrite: agents wrote code, humans rebuilt the loop

Thirty Shopify engineers moved a 300+ screen app from React Native to Swift and Kotlin in 12 weeks, with agents writing most of the implementation. The post is about what surrounds the code: business logic runnable without a device, the Reflex architecture and a CLI that loads any screen in milliseconds, one shared architecture across iOS and Android, an example and .md file per screen, and CI that fails when the two platforms diverge. Spec-driven development was abandoned because specs went stale in days; the legacy React Native app became the reference. The second half covers the bottleneck shift — laptops saturating on emulators, review and merge queues, tickets lagging behind Slack-reported fixes — and the responses: a remote dev environment for agents, adversarial agent-first review, and a self-healing loop that reproduces crashes every 15 minutes. Results: Android launch 1.71s to 0.87s, binary 80.4MB to 47.6MB.

shopify.engineering · 19 min · Agent Workflows · Agentic Coding · CI/CD
11-11

Inside Anthropic: how its own teams use Claude Code

Anthropic's own blog rounds up internal interviews on how employees use Claude Code. New data scientists on the infrastructure team hand over the whole codebase and lean on CLAUDE.md files to trace data pipeline dependencies; security engineers paste stack traces and docs into it during incidents and report roughly 3x faster triage; when Kubernetes stopped scheduling pods, the data infra team walked Google Cloud's console with Claude's guidance from dashboard screenshots until they found pod IP exhaustion, then got the exact commands to add a new IP pool. Marketing uses two sub-agents to filter hundreds of ad rows and generate variants; legal prototyped an internal phone tree. The thesis: agentic coding blurs the line between technical and non-technical work. Every case is vendor-reported, with no code, configs, or failure write-ups, so treat the numbers as marketing rather than evidence.

claude.com · 8 min · Agent Workflows · Agentic Coding · AI Productivity
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
11-09

Loops and Graphs: stop babysitting agents, approve only the last step

Two layers, split cleanly: a loop lives inside a node (produce, check, correct until green), a graph lives between nodes (what work exists, what runs in parallel, where results return). The argument is that a loop without a check that can actually fail is just a scheduler, and that most teams build the work first and bolt a model-based review onto the end. The graph layer gets four node types — splitter, worker, code node, gate — plus two return edges: a short correction edge that fixes the current run, and a long learning edge that feeds an accepted result back into the splitter's brief as a constraint. Gates should open by blast radius, not model confidence, with irreversible work in a lane that never opens. Written for engineers still approving every step by hand.

11-09

Plan With Code, Not Prose: pstack Pt. 2

Part two of poteto's pstack guide covers the front half of the agent workflow: research, planning, prototyping, and architecture. She argues agents mostly fail for two reasons — under-specified intent and missing context — so she has the agent restate a reported problem in its own words before touching code, then uses /how, /why, /recall, and /teach to rebuild runtime mechanics and historical motivation from git history, PR comments, Linear, Slack, Datadog, and Sentry. Planning happens in code rather than prose: README-driven development, a tutorial written before the API, throwaway prototypes driven by /control-app with screenshots and timing measurements, and /architect, which spins up parallel design candidates across model families and has a different model cross-judge them. Escape hatches like any, forced casts, or the same workaround at unrelated call sites count as proof the design is wrong. Aimed at engineers already shipping agent-written code to production.

08-18

Handing Claude daily app maintenance: 388 PRs in weeks

The author has been experimenting with letting Claude take over day-to-day maintenance of their apps. A dedicated Slack channel runs Claude Tag daily across iOS, Android, Desktop, web, CLI, and Agent SDK: a crash fuzzer taps around in simulators to find and fix crashes, a dup unifier merges similar abstractions, a dead-code remover deletes unreachable code and logs suspects, and an abstraction police fixes leaky abstractions. In a few weeks the routines opened 388 PRs; 180 were merged after Claude Code Review plus human review. Claude usually gets PRs right first try, and when it doesn't, the author asks Claude to tune its own routines so they improve the next day. The post includes some actual prompts and a link to Claude Code routines for trying similar workflows.

x.com · 2 min · Agent Workflows · Automation · Claude Code