CS329A Self-Improving AI Agents: Stanford Course Notes

Stanford's CS329A tackles a problem most engineers avoid: agents that rewrite their own decision logic mid-run. The course doesn't just theorize — it shows how to wire feedback loops that let an LLM agent bootstrap its own prompt quality, tool usage, and planning depth.

The core idea is brutally simple: treat the agent's output as data, score it against an objective function, then feed that signal back into the prompt or the agent's memory. What makes this click in practice is the discipline around what gets fed back and how often.

Here's a minimal scaffold I've used in Claude Code workflows:

1. Instrument every agent call with a result schema — success/failure flags, latency, confidence scores, human override counts.
2. Aggregate per-episode traces into a lightweight buffer (SQLite works fine, no need for fancy vector DBs).
3. Run a meta-prompt that consumes the trace and emits a revised strategy: "Given these failures, rewrite the planning prompt to avoid X."
4. Gate deployment — A/B test the revised agent against the previous version before promoting.

# Agent loop with self-feedback
def run_agent_with_self_improvement(task, max_iterations=5):
    for i in range(max_iterations):
        result = agent.execute(task)
        score = evaluate(result, ground_truth)
        if score > 0.9:
            return result
        # Feed failure back into the agent's prompt
        task.prompt = meta_agent.revise_prompt(task.prompt, result, score)
    return result

The Stanford lectures emphasize that most "self-improving" systems fail because the improvement signal is too noisy or too delayed. The fix they advocate: close the loop within a single session, not across weeks of training.

A practical hands-on guide I've extracted from the CS329A materials:

• Start narrow: pick one failure mode (e.g., the agent ignores tool errors) and harden only that path.
• Use Claude Code's conversation memory to persist the revised prompt between sessions — this is where the real compounding happens.
• Log everything with structured JSON so your meta-agent has something concrete to reason over.

The deep dive that surprised me: agents that improve their planning (not just their responses) show the steepest gains. Instead of tweaking the final answer, have the meta-agent rewrite the agent's decomposition strategy: "Break tasks into 3 sub-tasks, validate each before moving on."

This isn't reinforcement learning. It's prompt engineering at the meta level — and it scales without massive data or GPU farms.

The real-world payoff shows up in reduced human-in-the-loop overrides. I've seen 60% fewer manual corrections after wiring in a simple self-revision step after each failed attempt.