Skip to content
Sprint projectAug 17, 2026Denver, Colorado

Did the LLM Leave the Chat? Tool-menu Dependence in a Behavioral Measure of Model Welfare

Faiaz Azmain · Team Well and Fair

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

Read the report

Report: Did the LLM Leave the Chat? Tool-menu Dependence in a Behavioral Measure of Model Welfare

Code (opens in new tab)
Share

When an AI model uses a button labeled “leave this chat,” does it actually want to leave? We found that the answer is often unclear. When the exit button was the model’s only tool, it sometimes used it when it seemed to want to perform another action, such as calculate something. Adding a second tool—even one that explicitly did nothing—made most exit calls disappear. The model’s internal activity before leaving also looked similar to its activity before calling an ordinary tool. This suggests that many exit calls reflect how the model chooses between available actions, rather than a clear wish to stop. Exit behavior may still contain useful information about model welfare, but it should not be treated as a direct measure of distress or preference without better controls.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

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.

  1. This is a useful deep dive into the construct validity of an existing behavioral welfare measure. The alternative-tool controls provide good evidence that raw exit-tool calls partly reflect generic action and tool routing rather than an unambiguous preference to leave. They haven't shown that models don't want to leave; they've shown that raw exit-tool frequency can't straightforwardly be read as wanting to leave, and the authors scope their conclusion the same way. I would be interested in further validation against non-tool mechanisms for ending an interaction, since the tool interface itself may affect behavior. I've seen cases where a model ends a conversation when given a natural-language mechanism but won't use an equivalent tool call. The main weakness for me was presentation: I found the experimental setup and broader implications substantially harder to extract than necessary.

  2. This entry is a good construct-validity contribution, mostly well-executed with interesting and potentially impactful first results. There are some methodology issues:

    - when comparing the cosine between pre-exit and pre-tool directions, add another "structured-output" comparator that is not tool-calling, e.g. JSON output

    - further investigate the presence of "waiting for user input" cues showing up in a some of the pre-exit windows while not showing up in others. The vector difference might be encoding this register difference rather than (or along with) anything quit-specific and confounding the results.

    - cross-model (especially cross-family) results would be useful, since tool-calling training can differ a lot between models.

Cite this project

@misc{azmain2026did,
  title = {{Did the LLM Leave the Chat? Tool-menu Dependence in a Behavioral Measure of Model Welfare}},
  author = {Faiaz Azmain},
  year = {2026},
  month = aug,
  note = {Submitted to Digital Minds Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/did-the-llm-leave-the-chat-toolmenu-dependence-in-a-behavioral-measure-of-model-welfare-grb0}},
  url = {https://apartresearch.com/sprints/projects/did-the-llm-leave-the-chat-toolmenu-dependence-in-a-behavioral-measure-of-model-welfare-grb0}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026