Evolving Agents

Evolving Agents — the director
The director remembers how your team works — and makes every agent session work that way.
Your decisions, conventions and hard-won methods become a small memory of linked rules. Before an agent plans, the
director finds the rules that apply and puts them in front of it. Private work goes only to machines you have
cleared. When you correct it, it drafts a lesson that you accept or reject. It runs inside Claude Code today.

Contents — What it does · Who it is for · What to expect ·
Get started · What comes next · How it works, and what we measured ·
Earlier work

What it does

Who it is for

- Teams that work with coding agents and keep a CLAUDE.md, an AGENTS.md or Claude Code's memory that the agent
  still forgets under pressure.
- Any work that runs on house conventions — how a lab defines a measurement, a firm's review checklist, a team's
  release rules — where two good answers that follow different conventions are still a disagreement.
- People with confidential material who want a strong model to plan the work while the files themselves are
  processed only on machines they control.

What to expect

The director does not make a strong model smarter. With today's best models, an agent already follows general good
practice on its own — we measured that, and say so. Where the director pays is what the model cannot know: your
team's own decisions and conventions, your privacy rules, the methods you learned the hard way, and a record of every
lesson that you can audit. Every claim on this page has a measurement behind it, including the ones that came back
flat: how it works, and what we measured.

Get started

Inside Claude Code:

From the next session on, every plan walks your memory and cites what it follows. A band above the prompt…