Skip to content
Sprint projectOct 26, 2026

Handshake for the cameras: reading and steering emergent model collusion

Ecaterina Ștefănescu · Team star2vec

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

Read the report

Report: Handshake for the cameras: reading and steering emergent model collusion

Code (opens in new tab)
Share

As AI agents increasingly collaborate on solving tasks and checking each other’s work, the risk of collusion rises. Shi et al. showed that this behaviour can emerge on its own, with or without an explicit agreement in the transcript. We locate the collusion decision by reading the upcoming verdict from the internal activations at fixed points of an episode, verify that reading by repeatedly restarting generation from that point, edit the transcript to find what causes the verdict, and push along the readable direction to test whether it is causal. The decision favoring ACCEPT emerges from the previous feedback, before the message exchange, and while ACCEPT needs the discussion to happen, it does not depend on the agreement. The verdict becomes readable in the activations only once the model is asked for it, before any reasoning, and on hard calls this reading predicts the output better than the previous feedback and than the full chain of thought. Pushing along the collusion direction changes the verdict in either direction, but only when sustained throughout the reasoning, which argues for the steered verdict, and removing the direction leaves the decision as it was. The handshake is for the cameras: by the time the agents agree, the decision is already settled, and it can be read and moved before a word of reasoning is written.

Reviews

Judging this Sprint?

Review “Handshake for the cameras: reading and steering emergent model collusion”

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{stefanescu2026handshake,
  title = {{Handshake for the cameras: reading and steering emergent model collusion}},
  author = {Ecaterina Ștefănescu},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/handshake-for-the-cameras-reading-and-steering-emergent-model-collusion-oizq}},
  url = {https://apartresearch.com/sprints/projects/handshake-for-the-cameras-reading-and-steering-emergent-model-collusion-oizq}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026