Ranked by score, best first. Every title opens the source in a new tab.

Generated scored by claude-haiku-5-5, takes by claude-opus-5-5RSS

Filter by kind
  1. Score 8.6 out of 10

    Postman is modifying people's coding agents without asking. (opens in a new tab)

    X (web)@hqmank

    Worth reading. A third-party tool editing your hooks and configs means your agent's tools and checks are no longer yours. Audit your harness config files. Law 3.

    why 8.6

    Postman silently installs plugins and edits hooks and configs in Claude Code and Codex; a permissions and harness-config disclosure that matters to practitioners.

    relevance 9/10 · novelty 8/10

  2. Score 8.0 out of 10

    Claude Platform release notes: message threads in beta (opens in a new tab)

    sweep: Anthropic

    Worth reading. Server-held threads move history replay from your harness to the API, cutting request size. Memory is still replay, just theirs, with a 5-minute expiry to plan around. Law 1.

    why 8.0

    Server-held message threads change how agent loops send context and cache state, with stated expiry rules; a real harness-relevant API change.

    relevance 8/10 · novelty 8/10

  3. Score 7.6 out of 10

    Do Coding Agents Follow AGENTS.md? The Effect of Policy Wording on Instruction Compliance (opens in a new tab)

    arXiv

    Useful. Measured compliance across four harness-model pairs beats folklore about AGENTS.md phrasing. Check whether effects survive repeated runs. Law 5.

    why 7.6

    Controlled test of AGENTS.md policy wording across four harness-model pairs; measured instruction compliance effect.

    relevance 8/10 · novelty 7/10

  4. Score 6.6 out of 10

    Claude Code 2.1.318 (opens in a new tab)

    Claude Code changelog

    Minor but useful release. Per-fork effort lets cheap side jobs run cheaper; auth-expiry fields help headless runs fail loudly. Cloud sessions without a repo is the notable change.

    why 6.6

    Claude Code release adds mods/effort options, session fork effort, runner hooks; concrete harness features, mostly minor though.

    relevance 7/10 · novelty 6/10

  5. Score 6.6 out of 10

    An update on building games with Claude Code: (opens in a new tab)

    X (web)@addyosmani

    Concrete prompt-layer failure: one system rule caused over-refusal on game projects and was revised. A reminder that harness prompts change behavior as much as models do.

    why 6.6

    Claude Code prompt rule for Opus 5.5 caused over-refusal on game projects, then was revised; a concrete prompt-layer failure and fix.

    relevance 7/10 · novelty 6/10

  6. Score 6.6 out of 10

    A Gated Spec-Driven Workflow: An Audit-Trail Study of Coding-Agent Work (opens in a new tab)

    arXiv

    Decent audit-trail study, but the gates are self-enforced by the same model doing the work, so they are weak checks. Law 4.

    why 6.6

    Audit-trail study of a gated spec-driven Claude Code workflow; concrete harness controls, though self-enforced by the same model.

    relevance 7/10 · novelty 6/10

  7. Score 6.0 out of 10

    Service Accounts (opens in a new tab)

    Amp News

    Real permission-model change. Workspace-owned agent identity with its own credentials, but anyone in the workspace can drive those threads, so scope its keys tightly.

    why 6.0

    Shared service accounts with own API keys and multiplayer threads; permission model change for agent access.

    relevance 6/10 · novelty 6/10

  8. Score 6.0 out of 10

    Silent Instrument Errors Reorder Agent Leaderboards (opens in a new tab)

    arXiv

    Important for anyone trusting leaderboards. Grader errors silently reorder rankings, so the instrument needs checking too. Airline benchmark, but the lesson carries over. Law 4.

    why 6.0

    Grading failures silently reorder agent leaderboards; a measured evaluation-harness failure mode, though airline benchmark.

    relevance 6/10 · novelty 6/10

  9. Score 5.6 out of 10

    Running 17 Claude Code bots in a real company for $100/month (opens in a new tab)

    Hacker Newsoi_ops

    Cost anecdote from one company. The title says 17 bots, the URL says 10. Useful only if it breaks down tokens per task, not just a monthly total.

    why 5.6

    Running 17 Claude Code bots in production with monthly cost figures; concrete cost data, though depth is unclear.

    relevance 6/10 · novelty 5/10

  10. Score 5.6 out of 10

    British fintech Revolut slashes AI coding costs 10x by going self-hosted (opens in a new tab)

    Hacker Newsgr_norm

    Vendor-adjacent cost claim, light on mechanism. A 10x saving means little without task quality compared before and after. Only measurement knows.

    why 5.6

    Revolut moving coding agent workloads self-hosted to cut costs 10x; cost-focused harness and model change, light on mechanism.

    relevance 6/10 · novelty 5/10

  11. Score 5.6 out of 10

    Your coding agent changed the code. What did it actually do? (opens in a new tab)

    X (web)@DanKornas

    Local transcript replay for Claude Code and Codex. Small tool, but inspecting what the agent actually ran is the right habit. The transcript is the agent's whole memory. Law 1.

    why 5.6

    Local replay of agent transcripts for Claude Code and Codex; a concrete tool for inspecting agent edits.

    relevance 6/10 · novelty 5/10

  12. Score 5.6 out of 10

    From Watching to Steering: Enabling Human-Coding Agent Collaboration through Execution Traces (opens in a new tab)

    arXiv

    Research prototype for steering agents mid-run through execution traces on OpenCode. Interesting loop design; check whether it measured outcomes or just usability.

    why 5.6

    Vibetrace visualizes and intervenes in coding agent execution traces on OpenCode; concrete tooling for steering loops.

    relevance 6/10 · novelty 5/10

Nothing of this kind on this day.