Open library

The library

The essential reading of generative AI and agents, open in a clean reading view, with Meow and Standard summaries when available. No account needed to read.

560 papers · 558 with a Meow summary · 333 posts

The selected papers and blogs: the essential papers of generative AI and agents, and the key lab publications and essays, each with Meow and Standard summaries.

70 of 839 in this collection. Searches titles, authors, labs, arXiv IDs and summaries.

  1. Building effective AI agents

    Anthropic

    Build the smallest system that works: Anthropic argues that added agent complexity is justified only when evaluation shows it improves outcomes.

    anthropic.comSummariesAgent engineering
  2. Effective context engineering for AI agents

    Anthropic

    Anthropic’s central shift: agent reliability depends on curating the full, changing context at each turn—not just polishing a prompt—because longer contexts can reduce recall and focus.

    anthropic.comSummariesAgent engineering
  3. Writing effective tools for AI agents

    Anthropic

    Tools for agents should be designed around variable agent behavior and limited context, then improved through realistic evaluation—not treated as ordinary API wrappers.

    anthropic.comSummariesAgent engineering
  4. Harness design for long-running apps

    Anthropic

    A multi-agent harness made long app-building runs more capable, but its lasting lesson is selective: keep only the planning, decomposition, and evaluation the current model still needs.

    anthropic.comSummariesAgent engineering
  5. Equipping agents with Agent Skills

    Anthropic

    Agent Skills package instructions, scripts, and resources for agents to load as needed. An update says they have been published as an open standard for cross-platform portability.

    anthropic.comSummariesAgent engineering
  6. Making Claude Code safer with sandboxing

    Anthropic

    Claude Code’s sandbox gives its coding agent room to run commands inside set file and network boundaries, aiming to reduce permission prompts while limiting harm from prompt injection.

    anthropic.comSummariesAgent engineering
  7. A postmortem of three recent issues

    Anthropic

    Anthropic says three infrastructure bugs—not demand, time of day, or server load—intermittently degraded Claude responses from August into early September.

    anthropic.comSummariesAgent engineering
  8. Measuring AI agent autonomy in practice

    Anthropic

    In practice, an agent’s autonomy is not just a model capability: the model, the user, and the product shape it together.

    anthropic.comSummariesAgent engineering
  9. Trustworthy agents in practice

    Anthropic

    Anthropic’s main claim: agent safety depends on the whole system, not just the model. Autonomy brings useful capabilities but also more room for mistaken actions and prompt-injection attacks.

    anthropic.comSummariesAgent engineering
  10. Mitigating prompt injections in browser use

    Anthropic

    Claude Opus 4.5 and improved safeguards sharply reduced browser prompt-injection success, but the reported gains do not solve the problem.

    anthropic.comSummariesAgent engineering
  11. Scaling Managed Agents with stable interfaces

    Anthropic

    Managed Agents separates the agent’s session, harness, and execution tools behind interfaces intended to stay stable as models and implementations change.

    anthropic.comSummariesAgent engineering
  12. How we built Claude Code auto mode

    Anthropic

    Claude Code’s auto mode aims to reduce approval fatigue without switching permissions off: it uses classifiers to allow higher autonomy while retaining safeguards.

    anthropic.comSummariesAgent engineering
  13. Infrastructure noise in agentic coding evals

    Anthropic

    Agentic coding benchmark scores can shift with the machine budget, not just model capability, so a small leaderboard lead may measure infrastructure as much as coding.

    anthropic.comSummariesAgent engineering
  14. Introducing the Model Context Protocol

    Anthropic

    MCP replaces separate AI-to-data connectors with an open protocol that gives developers one shared way to connect tools and data.

    anthropic.comSummariesAgent engineering
  15. Developing a computer use model

    Anthropic

    In its Aug. 28, 2025 update, Anthropic said Claude 3.5 Sonnet could operate ordinary software through screen, cursor, and keyboard actions—moving AI beyond custom tools, though the capability was still in public beta.

    anthropic.comSummariesAgent engineering
  16. Gemini CLI: your open-source AI agent

    Taylor Mullen · Google

    Gemini CLI brings Gemini into developers’ terminals, with high—but explicitly capped—free-preview usage for individuals.

    blog.googleSummariesAgent engineering
  17. Qwen3-Coder: Agentic Coding in the World

    Qwen Team · Qwen

    Qwen3-Coder combines a long-context coding model with training that uses execution checks and multi-step interaction—the capabilities the announcement emphasizes for agentic work.

    qwenlm.github.ioSummariesAgent engineering
  18. GPT-4.1 Prompting Guide

    OpenAI

    GPT-4.1 follows prompts more literally than its predecessors, so developers should make desired behavior explicit and expect to migrate prompts that relied on implied intent.

    developers.openai.comSummariesAgent engineering
  19. Harness Engineering for Self-Improvement

    Lilian Weng

    The article’s key shift is from improving an agent’s answer to improving the machinery that repeatedly produces and checks answers.

    lilianweng.github.ioSummariesAgent engineering
  20. Prompt Engineering

    Lilian Weng

    Prompt engineering steers a language model without changing its weights, but it is empirical: a prompt that works for one model may fail on another.

    lilianweng.github.ioSummariesAgent engineering
  21. Designing agentic loops

    Simon Willison

    The key design problem is choosing goals, tools, and boundaries that let an agent iterate toward a solution without making its freedom the biggest risk.

    simonwillison.netSummariesAgent engineering
  22. Vibe engineering

    Simon Willison

    Willison proposes “vibe engineering” for AI-assisted production work where engineers remain accountable—not for accepting code just because it appears to work.

    simonwillison.netSummariesAgent engineering
  23. Here’s how I use LLMs to help me write code

    Simon Willison

    Treat an LLM as a fast, fallible coding partner: the developer must supply direction, verify behavior, and take over when judgment matters.

    simonwillison.netSummariesAgent engineering
  24. Building A Generative AI Platform

    Chip Huyen

    A generative AI platform is more than a model call: it is a set of optional components that can be added as an application’s needs grow.

    huyenchip.comSummariesAgent engineering
  25. Building LLM applications for production

    Chip Huyen

    A working LLM demo is not proof of a reliable production system: prompts can fail silently, and multi-step workflows add more ways to go wrong.

    huyenchip.comSummariesAgent engineering
  26. Patterns for Building LLM-based Systems & Products

    Eugene Yan

    An LLM demo is not a dependable product: the guide argues for measuring the real task and combining retrieval, specialization, safeguards, and user-centered design.

    eugeneyan.comSummariesAgent engineering
  27. What We’ve Learned From A Year of Building with LLMs

    Eugene Yan · Applied LLMs

    The authors’ year of building yields a practical thesis: getting an LLM demo to work is easier than making a dependable product; reliability comes from engineering the system around the model.

    applied-llms.orgSummariesAgent engineering
  28. Context Engineering

    LangChain Accounts · LangChain

    An agent’s context window is working memory, not a transcript that should grow without limit.

    langchain.comSummariesAgent engineering
  29. Deep Agents

    LangChain Accounts · LangChain

    A plain LLM tool loop can be “shallow”—unable to plan across longer tasks. The proposed fix keeps the loop and adds scaffolding for planning, subagents, and context.

    langchain.comSummariesAgent engineering
  30. How to think about agent frameworks

    LangChain Accounts · LangChain

    Agent frameworks are easy to compare badly: this article separates workflow-versus-agent behavior from orchestration style and high-level abstractions, with context control as the reliability test.

    langchain.comSummariesAgent engineering
  31. Introducing ambient agents

    LangChain Accounts · LangChain

    Ambient agents move beyond one-at-a-time, user-started chat: they listen for events, can act across several at once, and still bring people in when needed.

    langchain.comSummariesAgent engineering
  32. Don’t Build Multi-Agents

    Walden Yan · Cognition

    The failure isn’t simply parallelism: it’s agents making decisions without seeing the context and choices that shaped the rest of the work.

    cognition.comSummariesAgent engineering