← All speakers

Bio, Work & Ideas

Andrew Wilson

Conference affiliation: Anthropic · 2026

Andrew Wilson is a London-based solutions architect on Anthropic’s Applied AI team, helping businesses deploy advanced AI systems. His focus is long-running autonomous agents: software that can work for hours without losing context, abandoning unfinished tasks, or confusing an impressive interface with a functioning application.

Wilson studied industrial engineering at Northeastern University and worked in technology consulting and data-product engineering, building analytical models, automating reporting, and coaching startups through the university’s IDEA venture accelerator. His software projects include machine-learning experiments, Kaggle competition code, web applications, and nonprofit leadership-development tools. He subsequently joined Anthropic as a solutions architect in London.

At Anthropic, Wilson approaches agent reliability through three practical failure modes: degraded context, weak planning, and unreliable self-evaluation. His AI Engineer Europe workshop, co-presented with Ash Prabaker, maps those problems onto several engineering principles:

  • Agent harnesses must evolve with model capabilities. Permissions, checkpoints, sub-agents, context handling, and verification loops should address demonstrable weaknesses; safeguards can be simplified when stronger models make them unnecessary.
  • Persistent artifacts preserve continuity. Feature lists, progress files, initialization scripts, test results, and Git commits let successive sessions recover their bearings, implement unfinished work, and leave an auditable record.
  • Context strategy depends on the task. Fresh sessions can reduce drift, while larger context windows and compaction can sustain continuous work; evaluations should determine which configuration performs better.
  • Working software requires behavioral verification. Smoke tests, browser interaction, and explicit completion criteria expose features that appear finished but fail in practice. Existing production codebases also demand workflows adapted to their established stacks and quality standards.
  • Model selection shapes agent architecture. Stronger models can handle planning while more economical models execute implementation, provided each configuration is evaluated against its assigned task.

Wilson treats Claude Code as a practical environment for testing these patterns and the Claude Agent SDK as a foundation for deploying longer-running applications.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Long-running agents need durable state, testable definitions of done, and critics that use the software. As models improve, the harness must change with them.

  • What keeps an agent working after the demo starts?
    0:15 ↗
  • Models and harnesses improve together
    4:14 ↗
  • A loop needs a context policy and an exit
    7:55 ↗
  • Spend context on the work that needs it
    9:59 ↗
  • Turn a vague request into recoverable progress
    12:05 ↗
  • A stronger model changes the necessary machinery
    14:20 ↗
  • Give the critic a different job
    17:50 ↗
  • Write down what good design means
    20:42 ↗
  • Negotiate done before writing code
    23:42 ↗
  • A game maker that looks finished—and one that plays
    26:46 ↗
  • Specific failures make criticism actionable
    31:19 ↗
  • Remove scaffolding when the behavior improves
    34:14 ↗
  • A working music app exposes an evaluation boundary
    36:39 ↗
  • Calibrate reusable judgment, then earn unattended operation
    40:19 ↗
  • Allow a restart without losing the product boundary
    45:45 ↗
  • Evaluate each role and leave a usable history
    52:01 ↗
  • Agent teams can carry the pattern, but the critic needs distance
    56:21 ↗
  • Measure improvement within the product you are building
    1:01:25 ↗
  • Place human review where the application requires it
    1:07:40 ↗
  • Read the trace from the model’s point of view
    1:13:25 ↗

References