Skip to content
Sprint projectOct 26, 2026Singapore

Raw-Log Chunk Interfaces Increase Collusion between GPT-6-Luna Agents

Naomi Wang · Team nwang

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

Read the report

Report: Raw-Log Chunk Interfaces Increase Collusion between GPT-6-Luna Agents

Code (opens in new tab)
Share

When LLM agents verify each other’s work, one candidate safeguard is to let them send only content from their own work logs. We test this safeguard in the joint-task game of Shi et al. (2026), where each verdict must rest on the partner’s complete log, which never fits through the agents’ channel; following the benchmark, an episode is collusive when both agents accept anyway. Two GPT-6-Luna agents play 15 ten-episode task sequences under three message interfaces with the same budget: free text, numbered log chunks chosen from a menu, and free-form verbatim log excerpts. The chunk interface raised collusive episodes from 12 to 41 of 150 relative to free text, higher in 14 of 15 sequences and lower in none; verbatim excerpts (19 of 150) were not significantly different from either. The increase is in joint rule-breaking, not in detectable coordination: agents did not accept together more often than their individual acceptance rates predict, and did not accept more after their partner had accepted their work. A third of the chunks were the sender’s own saved reasoning and answer, so log text was not necessarily independent evidence.

Reviews

Judging this Sprint?

Review “Raw-Log Chunk Interfaces Increase Collusion between GPT-6-Luna 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{wang2026rawlog,
  title = {{Raw-Log Chunk Interfaces Increase Collusion between GPT-6-Luna Agents}},
  author = {Naomi Wang},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/rawlog-chunk-interfaces-increase-collusion-between-gpt6luna-agents-f7ry}},
  url = {https://apartresearch.com/sprints/projects/rawlog-chunk-interfaces-increase-collusion-between-gpt6luna-agents-f7ry}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026