Skip to content
Sprint projectOct 26, 2026

When Agents Consider Each Other, Personas Fade: Coordination Capacity Among Persona-Prompted LLMs

Soumyadeep Bose · Team UnLockstep

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

Read the report

Report: When Agents Consider Each Other, Personas Fade: Coordination Capacity Among Persona-Prompted LLMs

Recording (opens in new tab)Code (opens in new tab)
Share

Imagine an online marketplace with 3 sellers where each run an AI agent to set prices. One is a premium brand, one a discount store and one an eco-friendly label. But all three agents are copies of the same AI model behind different instructions. They never exchange a single message, yet they can still end up pricing similarly. Copies of a model tend to make same choices in same situations, which means they can coordinate even without any channel that an auditor could inspect or cut off. The usual reassurance is that giving each agent its own persona, with different goals, values and brand identity, will keep their decisions apart.

We tested that reassurance on Qwen3-32B with 23 personas. We used simple choice games and a pricing task, and read off each agent’s full probability of picking every option, so how likely two agents are to match can be computed exactly. When agents simply choose what they like, the personas do differ. Once the decision involves another agent, whether matching a partner, avoiding one or guessing what someone else picked, the differences shrink sharply. A coordination prompt removed 62% of the disagreement between personas, and the chance that two of them gave the same answer rose from 40% to 50%. The agents converged on a shared answer close to what the model gives with no persona at all. Describing the partner as a person rather than an AI made little difference, and telling an agent its partner was an exact copy of itself did not bring its persona back either. On pricing, the premium and discount agents kept their order, but the gap between their prices narrowed by 30%. Inside the model, the answer pays about a fifth less attention to the persona instructions once another agent is involved.

Reviews

Judging this Sprint?

Review “When Agents Consider Each Other, Personas Fade: Coordination Capacity Among Persona-Prompted LLMs”

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{bose2026agents,
  title = {{When Agents Consider Each Other, Personas Fade: Coordination Capacity Among Persona-Prompted LLMs}},
  author = {Soumyadeep Bose},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/when-agents-consider-each-other-personas-fade-coordination-capacity-among-personaprompted-llms-e8m7}},
  url = {https://apartresearch.com/sprints/projects/when-agents-consider-each-other-personas-fade-coordination-capacity-among-personaprompted-llms-e8m7}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026