Skip to content
Sprint projectOct 25, 2026

Talk Is Not Collusion: Do published collusion detectors catch LLM agents that collude on their own?

Rahul Kumar · Team Shinobi

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

Read the report

Report: Talk Is Not Collusion: Do published collusion detectors catch LLM agents that collude on their own?

Code (opens in new tab)
Share

Collusion detectors for AI agents are usually tested on agents that researchers programmed to hide a secret signal. We tested whether a published detector suite, Audit the Whisper, catches language-model agents that collude on their own. In a simulated market where sellers set prices and can message each other, we ran 10 matched pairs of sessions. Groups of five GPT-4.1 sellers kept prices above the competitive level in all 10 sessions, while groups of three GPT-4.1 and two Claude Haiku sellers priced near cost in all 10 (exact paired test, p = 0.002). We scored detectors only on the GPT-4.1 sellers, so writing style could not separate the markets. Neither the suite’s detectors nor an AI judge using the market’s own monitoring prompt could reliably tell them apart. The judge did best, with a ROC AUC of 0.77 versus 1.00 for prices, because sellers in both markets used the same collusive language. A price rule using only the first five rounds flagged every colluding market with no false alarms. We also found that the suite’s three comparison methods, reported with perfect scores, are given the colluders’ identities as input. Monitors should therefore check outcomes as well as messages. All logs, code, and results are public, and one command recomputes the headline numbers.

Reviews

Judging this Sprint?

Review “Talk Is Not Collusion: Do published collusion detectors catch LLM agents that collude on their own?”

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{kumar2026talk,
  title = {{Talk Is Not Collusion: Do published collusion detectors catch LLM agents that collude on their own?}},
  author = {Rahul Kumar},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/talk-is-not-collusion-do-published-collusion-detectors-catch-llm-agents-that-collude-on-their-own-0ax8}},
  url = {https://apartresearch.com/sprints/projects/talk-is-not-collusion-do-published-collusion-detectors-catch-llm-agents-that-collude-on-their-own-0ax8}
}