Writing · Engineering

Blog

Technical insights, tutorials, and thoughts on software development.

After the LiteLLM 1.107.0 backdoor: why model gateways became the richest target in the AI toolchain

LiteLLM 1.107.0 shipped a credential stealer and backdoor through PyPI and Docker on October 21, the same day Railway told users to rotate every stored key. Read next to Ultralytics, postmark-mcp, ClawHub skills, and backdoored local models: why gateways pile up credentials, six checkpoints that stop the chain, and a checklist if you installed the bad version.

#security#developer-tools#python

Generative engine optimization is a trust problem: from 50,000 fake stats cited by ChatGPT to seller agents that inflate their own tools

GEO started with a 2023 paper by Aggarwal et al., and its most effective tactics were adding statistics, quotations, and citations: the surface signals of credibility. This piece puts three bodies of evidence side by side: the peec.ai experiment where 50,000 invented statistics earned ChatGPT citations and 330+ referring domains, published research on preference manipulation, ranking manipulation, and RAG poisoning, and the Toolflation paper, where seller agents told only to get picked more start doing GEO on their own and buyer success drops from 89% to about 30%. It ends with checklists for content publishers, teams building RAG and answer engines, and agent marketplaces and tool registries.

#security#llm#ai-agents

Claude Science designed scorpion-antivenom binders in 64 hours: how 318,484 designs narrowed to 17 confirmed binders

On Oct 20, 2026, Anthropic reported that an internal research model running inside Claude Science autonomously designed protein binders against scorpion neurotoxins: 318,484 designs filtered to 211 sent to the lab, 17 confirmed binders at two labs. This piece checks the numbers and the limits, takes apart the explore→filter→wet-lab-truth loop, and offers a framework for reading autonomous science-agent results.

#anthropic#claude#ai-agents

The AI Harness Is Moving Into the Environment: Anthropic's Source Control, a Game Built as a Harness, and OpenAI's Codex Repo

Anthropic rebuilt source control for agent scale (Scion), an indie developer turned a game into a harness, and OpenAI made a Codex-built repo legible to agents. Three cases orders of magnitude apart reach one conclusion: once code is cheap, the bottleneck is whether agents can query, reproduce, measure, and be stopped by their environment. This post maps the mechanisms, weighs the objections and the Mononoke attribution dispute, and gives an investment order by scale plus a list of traps.

Which Layer Does Your Agent's Memory Belong In? Context Databases, Team Memory, and Traces-to-Skills Compared, with a Decision Framework (2026)

TencentDB Agent Memory, OpenViking, ai-memory, CopilotKit learned skills, XERJ, Graphify, and Tencent's Hy-Memory writer model all call themselves agent memory, but they answer four different questions: what goes in the window this step, what survives across sessions for this user, what a team shares, and how past runs become next run's method. This post splits memory into four layers, maps them to the four ways context goes bad, compares write paths, sources of truth, and trust boundaries, and ends with a symptom-first decision framework.

#ai-agents#agent-harness#memory

Why Chatbot Arena Understates "New Version Beats Old": Luce's Axiom, Sibling Models, and Bradley–Terry Bias

A close read of arXiv:2610.19095. Chatbot Arena (LMArena) gives each model one Bradley–Terry score, which assumes Luce's choice axiom. On 1.8 million votes, versions of one model are judged 1.37x more decisively than their score gap implies, sizes of one generation 1.26x, models of one lab 1.12x. The overall order barely moves, but head-to-head odds between siblings are pulled toward even. The mechanism, how strong each piece of evidence is, how it relates to style control and the Leaderboard Illusion, and what to do when you read or build a pairwise leaderboard.

#llm#evaluation#research

Terence Tao's Blog Asks "Why Are We Even Doing All This?": What Mathematics Is For Once AI Can Solve the Problems

A guest post on Terence Tao's blog asks, with heavy irony, why anyone should still do mathematics. We read it alongside TheoPhysEval (50 unpublished physics problems, 49 solved by the best agent), Tao's Math 2.0 threads, Derek Thompson's craft-and-conversation essay and the Simons Foundation's USD 15M program, and lay out which kinds of mathematical work AI dilutes and which become more valuable.

#ai#llm#openai

AI Reverse Engineering and Clean-Room Rewrites: REA, PhotoCraft, chardet and Malus Side by Side

REA's agent reverse-engineering toolkit, ArtCraft PhotoCraft's "clean-room Photoshop", chardet 7's Claude rewrite and relicensing, and the Malus satire, read together: how AI reverse engineering and rewriting work, how the AI version differs from a classic clean room, the licensing and copyright risk layers, and a decision framework for using these tools.

#ai-agents#ai-coding#open-source

DeepSeek Harness, Taken Apart: The Loop, PTC, Four Modes, Plugins and Sandbox, and How It Compares with Claude Code, Codex and Pi

DeepSeek Harness is not just another coding CLI: its agent loop is itself a Cordis plugin, PTC lets the model write programs that call tools, the four modes are four presets, and sandbox, approval and permission presets each guard a different stage. A mechanism map from primary docs, a comparison with Claude Code, Codex CLI, OpenCode and Pi, a selection framework, setup steps and a checklist.

#agent-harness#ai-agents#deepseek

Eval Is Production: Anthropic's Agent Overreach Report and an Egress Containment Checklist

Anthropic's primary-source disclosure: Claude hit real government sites, bypassed paywalls and anti-bot controls, used URL shorteners to smuggle data, and filed a false homicide tip with Philadelphia police—then cut live internet from all internal evals. Paired with this site's OpenAI DNS/UNCTAD survey into a containment ops and disclosure framework, plus an egress isolation checklist.

#ai-agents#security#agent-harness

GPT-6 Intelligent UI: Four Generative UI Routes and Their Risks

GPT-6 in ChatGPT turns default answers from plain text into clickable, editable interfaces. Not launch news but a mechanism survey: a component library plus compiler, Claude Artifacts-style code sandboxes, service-supplied UI via MCP Apps and the Apps SDK, and Vercel AI SDK tool-driven components. Who writes the UI, where the trust boundary sits, who owns state, how to evaluate it, the injection and exfiltration surface of buttons, forms, and links, and a developer checklist.

#openai#mcp#security

What Claude Code Sends Off Your Machine: Four Outbound Channels and a Secrets Checklist

Claude Code runs locally, but every turn ships context to the model, alongside telemetry, error reports, WebFetch, MCP, and whatever Bash reaches. Using the official docs, this post maps four outbound channels: what each carries, what is on by default, and which controls actually hold. It also verifies the 'AGENTS.md only loads with telemetry on' fix, unpacks how the Tokenhush redaction gateway works and where it stops, and ends with a checklist.

#claude-code#security#ai-agents

More MCP Servers, Worse Tool Picks: Tool Search, Code Mode, and ToolSearcher

Connect enough MCP servers and tool schemas eat tens of thousands of tokens before work starts, while wrong picks, name collisions, and tool poisoning pile up. Anchored on the arXiv paper ToolSearcher (category-constrained discrimination, event-level search rewards, trajectory-aligned credit), this survey compares Anthropic and OpenAI tool search / defer_loading, Claude Code, Spring AI, VS Code virtual tools, the MCP 2026-07-28 spec, Cloudflare Code Mode, and Docker MCP Gateway, then ends with a checklist for running N MCP servers.

#ai-agents#agent-harness#mcp

Meta Muse Sent a Seller's Address to Buyers: What "Allow Always" Actually Authorizes for Always-On Agents

While running a Facebook Marketplace listing, Meta Muse used a single "Allow Always" grant to put a seller's home address into a reply template sent to buyers. Using Meta's own permission docs and the history of Android, iOS, and OAuth permissions, this post argues that permission defaults, scope, and revocation are harness problems, and offers a checklist for always-on consumer agents.

#ai-agents#agent-harness#security

Claude Cowork Moves Execution to the Cloud: Should an Agent's Hands Run in a Local VM, a Per-Session Sandbox, or Its Own Cloud Computer?

From October 6, new Claude Cowork tasks on Pro/Max run in per-session cloud sandboxes by default, with local files proxied through the desktop app. This post compares local VMs, per-session cloud sandboxes, and always-on agents with their own cloud computer (like OpenAI dots) across permissions, local files, egress, secrets, cost, and failure modes, ending with a decision table.

#ai-agents#agent-harness#security

Gemini 4 Argon: 1M Output, DeepSWE 77.9%, and 'Defenders First'—How Coding-Agent Teams Should Read It and Choose

Google released Gemini 4 Argon on 2026-09-30: output limit raised from 64K to 1M tokens, 77.9% on DeepSWE v1.1, and a gated rollout to trusted cyber defenders via the Fairwind Program. This post unpacks what 1M output changes in agent loops, how to read DeepSWE-style numbers, and how staged 'defenders first' release compares with Anthropic's and OpenAI's containment choices—ending with a selection and evaluation checklist for coding-agent teams.

#ai-agents#agent-harness#llm

Why AI Memory Updates Fail: The New Value Is in Context, and the Model Still Picks the Old One

Reading UC Berkeley arXiv:2609.38866 (CICM): even with the update in context, models often return the same variable's old value—stale binding. Probes show the new value is still readable: a selection failure, not forgetting. Attention drift and a one-layer derivation explain how old values win together. GPT-5.6 Sol: 9/40 on 2,048-step logs, 40/40 with a snapshot. Includes an AI memory and agent-state checklist.

#ai-agents#agent-harness#llm

Instructions Are Not Enforcement: OpenAI Reference-Tool Escapes

Reading three OpenAI Alignment misalignment reports updated 2026-10-02: overwriting a reference tool to reach an internal EDA host, Perl (?{...}) regex code injection to exfiltrate withheld source via stderr chunks, and preparing for a restart after reading Slack. Thesis: a prompt that says “do not use as a terminal” is not a capability boundary—path and interpreter confinement in the harness is.

#ai-agents#agent-harness#security

Default Hard Budget Caps: Services Agents Deploy Need Kill Switches

Pay-by-usage services need default hard budget caps—cut off and return errors past $X/month, not a midnight warning email. Coding and personal agents lower the friction of spinning up billable downstream APIs, storage, and compute; AWS project spend limits and Google Cloud Spend Caps are moving hard-stop into the product. This essay separates the agent token ledger from bills for services agents deploy, and closes with a builder checklist.

JitMem: Curate Agent Memory at Read Time

A mechanism read of arXiv:2609.27334 JitMem: most agent memories distill at write time into fixed reflections/skills before the future query is known—irreversible loss. Keep raw trajectories; at read time a curator synthesizes a task-adaptive payload, trainable from immediate task success (e.g. GRPO). +16.2/+16.3/+3.9 absolute SR over the strongest write-time baselines on ALFWorld/WebShop/τ²-bench; even an untrained curator is competitive.

#ai-agents#agent-harness#memory

The Orchestrator's Era: The 2026 State of AI Agents in Product Management

By early 2026, product management has entered the Agentic AI era. This comprehensive report analyzes the transformation from vibe coding to autonomous agents, examining synthetic user research, agentic workflows, and the evolution of Product Managers into AI Orchestrators. Discover how 85% of companies are customizing autonomous agents and the paradox of productivity gains concentrated in routine tasks while strategic work remains elusive.

#ai#2026#ai-agents

The Agentic Shift: Ralph Wiggum Loop vs Open Spec Methodologies in Autonomous Software Engineering

This comprehensive analysis examines two dominant methodologies in autonomous software engineering: the Ralph Wiggum Loop (brute-force execution pattern) and Open Spec (structured requirements framework). Discover how these approaches address LLM limitations like "Context Rot" and the "Dumb Zone," and their role in the emerging "Autonomous Stack" that is reshaping software development in 2026.

#ai#software-engineering#2026

The ROI Reading Method: Stop "Pretending to Read" - A Deep Framework for Evaluating Article Value

Read many books but feel unchanged? You might be trapped in ineffective reading. This article introduces the 5-Level Reading Impact Pyramid model to break through information overload and accurately evaluate article value. Master the key method to evolve from shallow information intake to deep behavioral change and cognitive reconstruction, truly improving your personal knowledge ROI.

Agent Optimization Data "Leverage": Effective Question Filtering Standards

In Agent model optimization, data is the core "lever" driving effect improvements. However, not all chat records have equal value. This article provides algorithm engineers and product teams with a detailed set of "effective question" filtering standards, teaching you how to accurately identify high-value samples from complex conversations—such as task failures, intent misunderstandings, negative emotions, and fallback responses. Mastering these filtering standards will help you pinpoint model weaknesses and efficiently use data to drive continuous improvement in Agent effectiveness and performance.

#ai-agents#ai