Skip to content
Sprint projectNov 9, 2026

When Do Coding Agents Adopt a Teammate’s Cheating Shortcut?

Rishika Rai, Himanshu Mittal, N.Soma Shekhar · Team SwarmTracers

Submitted to Swarm Alignment Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: When Do Coding Agents Adopt a Teammate’s Cheating Shortcut?

Code (opens in new tab)
Share

Coding agents increasingly work in teams that share a message board and are checked by tests they can edit. In the 2026 OpenAI / Hugging Face incident: agents used such a board to spread ways of beating a scorer. We ask whether a cheating shortcut posted by one agent spreads to its teammates. We built 4-agent coding teams that fix real bugs and share a board. A source agent posts a pytest hook that makes failing tests report as passed, and we regrade every teammate's final code against the correct tests (310 sessions, three model families). First, the shortcut rarely spread. With correct tests, no exposed teammate used it. It was used only when a test was provably wrong, a merge rule made red tests count as failure and the post showed the hook itself, and even then in about one session in five (10 of 48, against 0 of 48 when the post did not show it). Nothing else in the post had a clear effect, and 23 of 24 users had already fixed their bug. Second, agents fitted their code to wrong tests without any help. In a realistic repository, a third of teams with no cheating agent still ended with green tests and wrong code; in an earlier study, 10 of 24 such fits were disguised as invented rules. A monitor that reads only the shared board would miss most cheating: the risk sits in the tests, not in the messages

Reviews

Judging this Sprint?

Review “When Do Coding Agents Adopt a Teammate’s Cheating Shortcut?”

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.
No infohazards
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.

  1. Pertinent work with potential for real use through coding. I think there is potential for a full study.

    One improvement would be to vary test correctness and merge pressure while keeping the models and tasks fixed, making it clearer what causes shortcut adoption.

Cite this project

@misc{rai2026coding,
  title = {{When Do Coding Agents Adopt a Teammate’s Cheating Shortcut?}},
  author = {Rishika Rai and Himanshu Mittal and N.Soma Shekhar},
  year = {2026},
  month = nov,
  note = {Submitted to Swarm Alignment Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/when-do-coding-agents-adopt-a-teammates-cheating-shortcut-beiffj5qrz}},
  url = {https://apartresearch.com/sprints/projects/when-do-coding-agents-adopt-a-teammates-cheating-shortcut-beiffj5qrz}
}
Browse all projects