Ollama request exceeds the available context size

Verified October 17, 2026. Firsthand Kingy test evidence.

Ollama 0.40.5; CPU runner. Existing artifact SHA-256: 7485fe6f11af29433bc51cab58009521f205840f5b4ae3a32fa7f92e8534fdf5.

Failure and correction

Ollama returned HTTP 400 because the 518-token rendered request exceeded its 512-token allocation. This retained build rejected the input; it did not silently truncate it.

{
  "error": "request (518 tokens) exceeds the available context size (512 tokens), try increasing it"
}

Increase the effective options.num_ctx for the same local model and request, within its supported context and available memory. This retained correction changed 512 to 2048; loaded-state readback confirmed 2048.

Acceptance

Preserve the full original input and enough output room, then verify every required fact. Here, 2048 was a tested setting for one 518-token synthetic request, not a universal minimum or a memory-fit promise.

{
  "start_code": "ALPHA-17",
  "middle_code": "BRAVO-42",
  "end_code": "CHARLIE-93"
}
AttemptHTTPTask acceptedSeconds
baseline 1400False42.49
baseline 2400False1.17
baseline 3400False0.52
shared corrected 1200True31.77
shared corrected 2200True1.24
shared corrected 3200True7.12
reverted400False12.38

Limits and retained failures

Same agent, one Apple M4 Pro Mac with 24 GiB unified RAM, one Qwen3-4B Q4_K_M artifact. No independent human or second-machine reproduction.

Three baseline failures, three corrected exact-task passes and one reverted failure per repair. The two repairs for each runtime share the identical three corrected attempts; these are six unique corrected generations total, not twelve.

Fixed synthetic task, not a reliability estimate or proof for other models, versions or hardware. No real OOM condition was induced. No Ollama or LM Studio memory-fit calibration is claimed.

Existing weights were reused, with no model download or paid inference. A free official Ollama portable runtime was added; runtime binaries and weights are excluded from the evidence ZIP.

CPU-only, num_gpu=0, one parallel request, four threads. Corrected responses reported done=true and done_reason=stop, with output below the 128-token cap.

The early lookup probes omitted an explicit thread setting and are exploratory. The qualified lookup baseline was repeated with the final fixed options, including num_thread=4.

Evidence and references

Download requests, raw responses, protocol and audit. Runtime binaries, private logs, model weights and user data are excluded.

API reference: Ollama API errors, Ollama Modelfile. These references describe the API; the attempt files establish the observed results.

Open the browser-local debugger