Skip to content
Sprint projectOct 26, 2026

Detecting Collusion Between AI Agents

Fan Wu, Dibya Mishra, Three other members. We will send email and details later. · Team Sunshine

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

Read the report

Report: Detecting Collusion Between AI Agents

Code (opens in new tab)
Share

Agents that grade each other's work can collude by accepting each other's output against the rules, often without saying so. We ask what evidence reveals collusion when the conversation does not. Using the SALT-NLP agent-collusion dataset (1,800 runs, 18,000 episodes), where mutual acceptance always breaks the rule, we define five collusion categories plus a one-sided subtype and hand-label 342 episodes from 72 runs. An announcement rule combined with a Qwen3-32B labeller reproduces these labels on held-out runs (accuracy 0.92, κ 0.90), and we use it to label every episode. From each run's verdicts we compute intensity, onset, gaps, re-entry and early stopping. Three quarters of runs collude at least once and two thirds in the final episode, yet the dataset's chat judge flags only 56% of colluding episodes, and 44% of collusion carries no two-sided agreement in the chat, the opposite of the plans-without-action pattern Colosseum reports. The verdicts instead carry the signatures of repeated-game collusion: it appears only when agents remember each other, is reciprocated (+12 to +29 percentage points), persists (92% of colluding pairs continue) and recovers most of the reward the rule withholds. Rewarding each agent separately rather than jointly reduces collusion from 42% to 5% (Flash-Lite) and from 86% to 34% (Flash) of episodes. Monitors of interacting agents should therefore rely on behaviour first and conversation second.

Reviews

Judging this Sprint?

Review “Detecting Collusion Between AI Agents”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

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

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field 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 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.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

No public critique yet.

Cite this project

@misc{wu2026detecting,
  title = {{Detecting Collusion Between AI Agents}},
  author = {Fan Wu and Dibya Mishra and Three other members. We will send email and details later.},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/detecting-collusion-between-ai-agents-5gts}},
  url = {https://apartresearch.com/sprints/projects/detecting-collusion-between-ai-agents-5gts}
}