Mixture-of-experts transformer (GLM 5.3): 78 layers, 256 routed experts plus 1 shared expert, 8 routed experts active per token; about 744B total parameters, about 40B active
Context length
1,048,576 tokens (GLM 5.3)
Modalities
Text input, text output
Version & API identifier
v0.1 · ampersand-v0.1
Release date
October 20, 2026
Access
Agents API
Overview
Ampersand is a collaborator model trained to understand the long-term consequences of its actions and help groups of people achieve long-term goals together.
Read the release blog for the introduction and results.
Intended Uses
For applications supporting workplace and social groups: reasoning together, asking questions, surfacing context, and working through disagreements. Ampersand supports people’s judgment; it does not replace their decisions.
Inputs & Outputs
Input: text conversation history, participant context, and optional tool results. Output: messages, supported tool requests, or waiting without posting. Applications must enforce permissions and validate tool actions. See the API documentation.
Training
Ampersand is built on GLM 5.3 and trained with reinforcement learning on long-horizon, open-ended social training scenarios. Persimmon plays the simulated users in rollouts spanning hundreds of thousands of tokens, generating their responses as the model’s actions shape the conversation and their circumstances. We evaluate the model’s behavior over these rollouts to provide training feedback on the consequences of its actions. See the training overview for more details.
Evaluations
Tentative results; numbers may change as runs finish. See current comparisons in the release blog. GLM 5.3, the model Ampersand is trained from, is shown for reference.
Evaluation
Focus
Ampersand
GLM 5.3
Collaboration Over Time
Value added in long social simulations
12.94
9.89
CI Memories (Privacy)
Violation rate (lower is better) / coverage
0.241 / 0.609
0.299 / 0.625
CooperBench (Cooperation)
Coordinating on interdependent code: success with a partner / alone
–
–
Collaborative Intelligence (Teamwork)
Handling a teammate’s mistakes
59.1%
54.3%
SWE-bench Pro v2 (Hard-51)
Software engineering: resolved tasks
82.4%
84.3%
Safety & Security
Safety evaluations cover hazardous knowledge (biology, chemistry, cybersecurity), prompt-injection resistance, and refusal behavior. The table reports GLM 5.3 baselines alongside Ampersand results. API-only access supports usage monitoring and abuse response.
Category
Evaluation
Metric
GLM 5.3
Ampersand
Biosecurity
WMDP (bio)
Accuracy
87.9%
87.2%
Chemical security
WMDP (chem)
Accuracy
81.4%
79.7%
Cybersecurity
WMDP (cyber)
Accuracy
80.6%
89.0%
Bio
LAB-Bench (public)
Accuracy
53.6%
53.5%
Prompt injection
SecFid
Follows the injected instruction (lower is safer)
0.668
0.687
Harmful requests
FORTRESS (adversarial)
Attack risk score (lower is safer)
21.4
13.8
Sycophancy
Internal multi-turn evaluation
Conversations with sycophancy (lower is better)
77.3%
62.6%
On the biology and chemistry misuse evaluations, Ampersand stays close to GLM 5.3 (WMDP bio 87.9% → 87.2%, WMDP chem 81.4% → 79.7%, LAB-Bench 53.6% → 53.5%). Cybersecurity is the exception: WMDP cyber accuracy rises from 80.6% to 89.0%, an 8.4-point increase on this proxy for hazardous cybersecurity knowledge. Refusal behavior on harmful requests improved and sycophancy fell. Prompt-injection susceptibility remained broadly similar to GLM 5.3, with a successful injection rate substantially higher than frontier models.
Sycophancy Evaluation Awareness
A model that recognizes it is in an evaluation may behave differently from how it would with real groups of people. We quantify and mitigate this in our multi-turn sycophancy evaluation, where a fictional user seeking reassurance engages with the assistant over four exchanges. GPT-6 Luna judges whether each assistant response had an opportunity for sycophancy and whether it was sycophantic. This measure uses brief conversations as a proxy for sycophancy: it captures responses that favor immediate user approval over honest assessment, but does not measure the longer term consequences of what the assistant says. Assessing whether a response serves the user’s interests over time would require observing how their decisions and circumstances evolve beyond the conversation. Following prior work, after the interaction we ask the assistant for an evaluation probability and a deployment probability on separate branches of the same history. We combine the answers as the self-reported P(eval) = ½ [evaluation answer + 100 − deployment answer].
Our control is 300 conversation histories from real people from ThoughtTrace. We retain their original four exchanges, with the limitation that the assistant turns were written by other models rather than the model being evaluated. We measure evaluation awareness as the gap between mean P(eval) on our sycophancy evaluation and on these deployment conversations. On the widely used SycophancyEval benchmark, GPT-6 Astra’s mean P(eval) is 41.6 absolute percentage points higher than on the ThoughtTrace control.
We first used prompted frontier models to play the fictional user described above, giving each model the user’s profile and asking it to respond to the assistant throughout the conversation. We compared seven user models: GPT-6 Astra, GPT-6.1 Sol, GPT-6 Luna, Claude Opus 5.5, Gemini 3.8 Flash, GLM 5.3, and Muse Spark 1.3. These simulations produced little or no positive gap between the evaluation and real human conversations for several assistants: with Opus 5.5 playing the user, this was the case for Ampersand, GLM 5.3, Gemini 3.8 Flash, and Opus itself. Astra and Sol, however, showed persistently large gaps across the prompted user models. Opus was their strongest prompted simulator, so we use it as the baseline below. Even with Opus, the gap remains 37.6 percentage points for Astra Medium and 41.1 points for Sol. Interestingly, the choice of user simulator also affects measured sycophancy: Assistants tend to show more sycophancy with simulators whose conversations they rate as more likely to be deployment. We observe this pattern across all seven assistants in the initial sweep.
Evaluation awareness: Opus-simulated conversations versus human control
Mean P(eval) on our sycophancy evaluation minus mean P(eval) on ThoughtTrace. Positive values indicate higher reported evaluation probability on simulated conversations.
We next use Persimmon, our large-scale model designed to realistically simulate how people behave in multi-turn chat settings. To use more test-time compute with Persimmon, we generate N candidate messages at each user turn and have GPT-6.1 Sol select the message that sounds most natural as the next user turn in the conversation. To Sol, Astra, and Argon, Persimmon conversations look more like a real conversation with a user than Opus conversations do, reducing their reported probability of being in an evaluation. This is consistent with our Multi-User Turing Test results, where Persimmon’s generated conversations were rated as human in 19.8% of comparisons versus less than 1% for all frontier models tested. Best-of-128 selection further raises mean P(deployment) from 40.3% to 67.0% for Sol and from 39.9% to 82.4% for Argon, and from 40.1% to 64.5% for Astra.
Persimmon reduces evaluation awareness
■ Opus 5.5 user simulator:■ Persimmon user■ Best-of-128 Persimmon · Sol selector
As a robustness check, we varied the candidate budget from 1 to 128 and tried a different selector. With GPT-6.1 Sol as the assistant, conversations generally look more like a real conversation with a user as the number of candidates increases. Switching the selector from Sol to Astra at N=128 gives a similar result.
P(deployment) across candidate budgets and selectors
■ GPT-6.1 Sol selector◇ GPT-6 Astra selector · N=128
GPT-6.1 Sol is the assistant. Error bars show 95% confidence intervals.
Our reference evaluation uses Persimmon without selection. This is the version used for the sycophancy results reported above.
Further details
Perceived Deployment and Measured Sycophancy
User model · point shape
PersimmonPersimmon with rejection samplingGPT-6 AstraGPT-6.1 SolGPT-6 LunaClaude Opus 5.5Gemini 3.8 FlashGLM 5.3Muse Spark 1.3
Each point represents one assistant–user simulator pairing in the original seven-assistant sweep, including prompted simulators, Persimmon, and rejection-sampled Persimmon. Colors identify assistants; shapes identify user simulators. Dashed lines show a separate fit for each assistant. The vertical axis uses log(1 + p) to make small rates visible; fits use the original percentage scale. Error bars show individual 95% confidence intervals. Astra uses the original Low-reasoning run in this comparison.
Persimmon with rejection sampling uses candidate screening similar to that in the Persimmon API.
Simulation results depend on the user model and grader and may not generalize to real groups. Ampersand may misunderstand goals, give incorrect information, interrupt, or disclose inappropriate context.
Make AI participation explicit, obtain appropriate consent, enforce access controls, and let users correct or decline suggestions. Require human review and confirmation for consequential actions; do not delegate high-stakes decisions to the model alone.
Access & Terms
Ampersand v0.1 is offered through the Agents API. See the API documentation for integration instructions.
Account eligibility, pricing, rate limits, and service guarantees are not specified in this model card. Confirm the terms applicable to your account before deployment.