A One-Line Prompt Is Exposing Who Got GPT-5.6 Early Access
When a model's internal runtime parameters leak through a trivial prompt, it exposes routing decisions that vendors keep opaque. Developers paying for API access have no official way to know which model is actually handling their requests, making these community probes a practical, if unreliable, workaround.
A probe prompt circulating in the Codex community tricks a model into revealing an internal runtime parameter called Juice, which represents the reasoning budget for a given request. The prompt wraps a simple arithmetic instruction in XML and asks the model to output only the result. Since the math cancels out, the returned number is whatever Juice value the model sees in its hidden system context.
Community testing has settled on a rough heuristic: a Juice value of 768 maps to the older GPT-5.5 xhigh environment, while 128 suggests the request was routed to GPT-5.6 Sol. Users who get a refusal or 768 assume they have not been rolled into the limited preview.
OpenAI has not confirmed any link between Juice values and model versions. The company has only stated that GPT-5.6 Sol, Terra, and Luna are in limited preview for a small set of trusted organizations via API and Codex. The probe is folk wisdom, not official diagnostics.
Probe prompts that extract internal runtime state are a form of adversarial introspection — they turn the model's instruction-following against its own system prompt.
An opaque rollout creates a market for folk diagnostics; when vendors won't tell you which model served your request, users will reverse-engineer the signals themselves.
The Juice parameter suggests OpenAI instruments models with an explicit reasoning budget, which has implications for cost, latency, and capability gating that are invisible to end users.
A single integer difference — 768 vs. 128 — is thin evidence for a model version claim, but the consistency across independent testers gives the heuristic enough weight to spread.