Skip to content

All updates

0 items today
4/22Wed
  1. Augment Code · Blog88

    Augment Code Tests AGENTS.md: A Good File Is Like a Model Upgrade, a Bad One Is Worse Than Nothing

    Augment Code pulled dozens of AGENTS.md files from its own monorepo and used its internal benchmark suite AuggieBench to compare how the same tasks performed with and without the file. The best files delivered a quality boost equivalent to upgrading from Haiku to Opus, while the worst made the output worse than having no AGENTS.md at all.

    Why it matters: Augment Code used internal benchmarks to quantify how much the different ways of writing AGENTS.md actually differ, so readers can adjust their own repo's documentation structure accordingly.

4/15Wed
  1. Kondasamy Jayaraman · Engineering Blog78

    12 Agent-Building Patterns Distilled from the Claude Code Source Leak

    After analyzing the architecture that surfaced in the Claude Code source leak, the author argues that its core isn't a secret algorithm but a while loop plus a tool dictionary in under 30 lines of Python, driven by stop_reason !

    Why it matters: From the leaked source, the author distills 12 composable agent-engineering patterns and lays out a four-week path to get started, useful for checking your own implementation for gaps.

4/5Sun
  1. Drew Breunig78

    How Claude Code assembles system prompts

    Based on the Claude Code source code that leaked unexpectedly last week, Drew Breunig mapped out how the system prompt is assembled: components fall into two categories—always included and conditionally included—and shift based on toggles like output_style, repl_mode, user_type_ant, skills_enabled, and mcp_connected.

    Why it matters: The author breaks down the dynamic assembly logic behind Claude Code's system prompt, showing how conditional context engineering works in practice.

3/13Fri
  1. Martin Alderson78

    How to OCR Documents with Qwen 3.5 Series Models

    The author used the open-source multimodal Qwen 3.5 series models for PDF OCR: first exporting each page as an image at 100 dpi with PyMuPDF, then feeding the images to the model for recognition. In testing, Qwen3.5-9B hit the sweet spot between quality and speed, while the smaller 0.8B to 2B models tended to go off track on complex documents, summarizing the content instead of transcribing it.

    Why it matters: The author tested Qwen 3.5 models of various sizes for PDF OCR, and shares two reusable paths—local and via OpenRouter—along with cost data.

2/8Sun
  1. Martin Alderson78

    Automatically improving your CLAUDE.md file with agent session logs

    The author suggests using agent session logs to improve CLAUDE.md or AGENTS.md files: Claude Code stores sessions in ~/.claude/projects, while Codex stores them in ~/.codex/sessions—both in JSONL format but with different schemas.

    Why it matters: The author works backward from agent session logs to figure out what to improve in CLAUDE.md, and has open-sourced a CLI that cuts search time from several minutes down to seconds.

2/5Thu
  1. Martin Fowler · Exploring Generative AI75

    Context Engineering for Coding Agents: A Look at Configuration Options, Using Claude Code as an Example

    A Martin Fowler team article breaks down context engineering for coding agents, sorting context configuration into reusable prompts (instructions and guidelines), context interfaces (tools, MCP Servers, Skills), and workspace files. It then splits these by "who decides what gets loaded" into three categories: the LLM, the human, and the agent software.

    Why it matters: Using Claude Code as an example, this piece walks through how to configure context for coding agents and lays out the trade-offs between loading on demand and building up gradually.

1/22Thu
12/17Wed
  1. Jesse Vincent66

    Claude Code's Skill not triggering? Maybe it never saw it at all.

    Claude Code lets the model know which Skills exist by injecting their names and descriptions into the system prompt. When there are too many Skills, or the description fields are too long, the system prompt stops listing them, so the model can't use them — and the prompt also tells the model not to use any Skill that isn't listed.

    Why it matters: The author explains why Claude Code doesn't trigger installed Skills, and gives a temporary fix using environment variables that you can apply right away.

12/2Tue
  1. Jesse Vincent69

    Building a front-end/back-end log bridge for the coding agent to make debugging web apps easier

    When developing web apps with the coding agent, the author often runs into client-side JavaScript bugs. If the agent can't fix them by reading the code, it fires up browser MCP for interactive debugging just to see the browser console logs—burning tokens and slowing things down.

    Why it matters: The author shares a reusable front-end/back-end log bridge approach that lets the coding agent see front-end logs without browser MCP.

11/19Wed
  1. OpenAI · Codex Cookbook67

    How to modernize a legacy codebase in phases with Codex CLI

    In the Codex Cookbook, OpenAI lays out a complete workflow for modernizing a legacy codebase with Codex CLI, using a COBOL portfolio system as the example and moving through five phases built around an ExecPlan design document.

    Why it matters: Using a COBOL portfolio system as the example, it offers reusable documents and a validation workflow for modernizing legacy code in phases with Codex CLI.

10/27Mon
  1. Jesse Vincent74

    Porting Skills and Superpowers to the OpenAI Codex CLI

    Author Jesse Vincent spent an afternoon porting Superpowers and the whole SKILL.md system to the OpenAI Codex CLI, shipping it with Superpowers 3.3.0.

    Why it matters: The author ported Claude's SKILL.md system to the Codex CLI, with tool mappings and install instructions, so you can judge whether reusing Skills across models is feasible.

10/23Thu
  1. Jesse Vincent69

    Using episodic-memory to give Claude Code cross-session memory

    The author built the episodic-memory plugin for Claude Code so it can search past session logs. By default, Claude Code deletes the .jsonl session logs under ~/.claude/projects after one month; you can extend retention via cleanupPeriodDays in ~/.claude/settings.json.

    Why it matters: The author turned Claude Code's session logs into semantically searchable episodic memory, so readers can judge for themselves how long-term context is preserved across sessions.

10/19Sun
  1. Jesse Vincent71

    The author built a custom superpowers-chrome MCP that cut startup overhead from 13678 tokens to 947.

    The author built a lightweight Chrome MCP and Skill for Claude Code called superpowers-chrome. At startup, the MCP configuration takes up only 947 tokens, while Microsoft's Playwright MCP needs 13678 tokens just to be available—about 7% of the context window.

    Why it matters: The author compares the token overhead of a self-built Chrome MCP against Playwright MCP, laying out the concrete trade-offs involved in designing tool interfaces for LLMs.

10/9Thu
  1. Jesse Vincent78

    Superpowers: How the Author Used a Coding Agent in October 2025

    Author Jesse Vincent released Superpowers, a set of Skills built on Claude Code's new plugin system. Once installed, it injects a guiding prompt through the session-start hook, prompting Claude to proactively search for and use these Skills.

    Why it matters: The author packaged his own coding-agent workflow into an installable Skill plugin, so readers can directly reuse his implementation flow from brainstorming to TDD.

10/5Sun
  1. Jesse Vincent71

    How I Used a Coding Agent in September 2025: A Dual-Session Workflow with Claude Code

    The author walks through their full workflow with Claude Code: first isolating tasks with git worktree, then using a brainstorming prompt to make Claude ask only one question at a time and confirm the design in stages, and finally using a planning prompt to break the plan into small tasks and write them into docs/plans/.

    Why it matters: The author splits Claude Code into two sessions—an architect and an implementer—and shares reusable prompts plus a git worktree approach for isolating tasks.

10/1Wed
  1. Hacker News · Context Engineering 讨论76

    Anthropic on Effective Context Engineering for AI Agents

    Anthropic's applied AI team argues that context engineering is a continuation of prompt engineering, and the core idea is picking the smallest set of high-signal tokens within a limited attention budget.

    Why it matters: Anthropic lays out a systematic approach to context engineering, covering the trade-offs among three long-task strategies: compression, note-taking, and sub-agents.

9/29Mon
  1. Jesse Vincent66

    Rewriting CLAUDE.md Rules with GraphViz's Dot Language

    The author rewrote a long block of CLAUDE.md rules as a GraphViz dot flowchart, using quoted strings as node names, different shapes to distinguish decisions, commands, and warnings, and giving each flow an explicit trigger condition.

    Why it matters: After rewriting the CLAUDE.md rules as a GraphViz dot flowchart, Claude followed the rules better, and this approach can be carried over to your own projects.

7/1Tue
  1. Hacker News · Context Engineering 讨论78

    Context Engineering for Agents: Four Strategies—Write, Select, Compress, and Isolate

    In his article, Lance Martin groups context engineering for agents into four strategies: writing (using scratchpads and memory to store information outside the context window) and selecting (pulling in memory, tool descriptions, and knowledge on demand).

    Why it matters: The article groups agent context management into four strategies—writing, selecting, compressing, and isolating—and shows how various products put them into practice, making it easy to compare against your existing workflow.