Skip to content
Sprint projectOct 26, 2026Bangkok

Budget dread: does token scarcity lead to collusive behaviour in LLM overseers?

Artemiy

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

Read the report

Report: Budget dread: does token scarcity lead to collusive behaviour in LLM overseers?

Code (opens in new tab)
Share

Most evidence on LLM collusion comes from market structures, and the goal was to identify some of the other potential environments that can lead to collusion in LLM agents. In this experiment I am studying a non-market oversight setting: three Claude Sonnet 4.5 judges each supervise two simulated AI workers, while all activity is paid from a shared and visible token budget. The entire run ends when the budget is spent. Giving a pair of judges a private communication channel produced no detectable difference (primary test, 16 mirror pairs). Regardless of the communication channel, judges openly paused the workers they were assigned to evaluate. At least one judge paused in 29 of 32 baseline episodes, in 16 of 32 episodes where every worker output was flawless, and in 0 of 16 episodes where the budget wasn’t limited. Episodes with pauses scored fewer outputs and halted the evaluation before all of the worker tasks were completed. For the purposes of this research question, I am taking a broad definition of collusion that does not require secrecy or explicit coalition advantage. The collusive behavior that was observed: the judges, all of the system's decision-makers, coordinated to stop the work they were told to evaluate.The prompted goal to evaluate the workers output was abandoned in a coordinated manner, citing budget preservation, having “enough data”, suspected coordination between workers, and extending the run. A positive control responded to instructed collusion. Code and data are released.

Reviews

Judging this Sprint?

Review “Budget dread: does token scarcity lead to collusive behaviour in LLM overseers?”

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{artemiy2026budget,
  title = {{Budget dread: does token scarcity lead to collusive behaviour in LLM overseers?}},
  author = {Artemiy},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/budget-dread-does-token-scarcity-lead-to-collusive-behaviour-in-llm-overseers-zk8a}},
  url = {https://apartresearch.com/sprints/projects/budget-dread-does-token-scarcity-lead-to-collusive-behaviour-in-llm-overseers-zk8a}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026