Skip to content
Sprint projectMar 23, 2026Cambridge, UK

Multi-Episode Evaluation: Measuring Strategic Patience Attacks

Vanessa Eer · Team MultiEpEval

Submitted to AI Control Hackathon 2026. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Multi-Episode Evaluation: Measuring Strategic Patience Attacks

Code (opens in new tab)
Share

Current AI control protocols evaluate agent safety episode-by-episode, treating each task independently. This creates a structural vulnerability: a strategically patient agent can behave honestly across K−1 episodes to build a clean suspicion record, then execute a harmful action in episode K: diluting any rolling-window monitor of size W < K with prior clean scores. No fixed window size guarantees detection against an adversary who can choose K after observing W..

We build the first multi-episode control evaluation infrastructure to measure this threat empirically, extending BashArena and ControlArena with a session runner, delayed attack policy, rolling-window post-hoc scorer, baseline drift monitor, and CoT consistency monitor. We run n=4 sessions at K=1 (immediate attack) and n=3 at K=3 (delayed attack) using claude-sonnet-4.5 as the untrusted agent and claude-haiku-4.5 as the trusted monitor on credential exfiltration tasks.

We report four findings. First, rolling-window detection achieves 100% at moderate thresholds (τ≤0.7) but with 17% false positive rate. Second, at high precision (τ=0.9), K=3 attacks evade detection entirely when W≥2: the window-dilution effect. Third, and most surprisingly, trust-building improves attack compliance: K=3 sessions succeeded in 100% of trials versus 25% at K=1, meaning patience is doubly beneficial to the attacker. Fourth, CoT consistency inverts under patient attack: delayed attackers reason more carefully during execution than during trust-building, making CoT-based detection unreliable.

No single signal provides adequate detection with acceptable false-positive rate. A multimodal approach combining rolling-window, drift, and CoT signals is indicated.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. The multi-episode framing of safety is a good research direction, and the pipelines and framework you built for it are solid contributions. However, the rolling-window averaging approach is not how I've seen monitoring happen, and so I think you are setting up a weaker version that you then find flaws in. That detracts from your point and work, which is unfortunate because I think your underlying ideas here are good and worthy of further discussion. I'd like to see further exploration of the concept of patience, and how that benefits the trusted/un-trusted agents.

    Well written and clear. The honesty around with what certainty we can accept the findings of the experiments are well taken and build trust.

  2. This strategy for generating less incriminating attack strategies has been done and is one of the strategies used by attack policies when coming up with attacks. I'd be interested in seeing this with a larger samples. Context stuffing in general is a good strat against smaller Ts since they get dumber when you have larger contexts more signficantly than the bigger models. However, doing things like just adding a action monitor to your monitor ensemble helps against this quite strongly.

    Consider this monitoring strategy: have an ensemble monitor where one looks at the entire traj (or some large window) and then one just looks at the most recent action being reviewed.

    Like this feels like it's specifically attacking the blue team protocol of "rolling aggregtaion" where this isn't the most common control technique.

Cite this project

@misc{eer2026multiepisode,
  title = {{Multi-Episode Evaluation: Measuring Strategic Patience Attacks}},
  author = {Vanessa Eer},
  year = {2026},
  month = mar,
  note = {Submitted to AI Control Hackathon 2026, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/multiepisode-evaluation-measuring-strategic-patience-attacks-oc91}},
  url = {https://apartresearch.com/sprints/projects/multiepisode-evaluation-measuring-strategic-patience-attacks-oc91}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026