434ec07885
Introduce streaming endpoint for NDJSON scan progress, incorporate scan checkpoints into scan details, and update UI components to display this new information. Replit-Commit-Author: Agent Replit-Commit-Session-Id: 0d01f99a-ea6a-447d-82fd-311715434a39 Replit-Commit-Checkpoint-Type: full_checkpoint Replit-Commit-Event-Id: 2852b526-3bf8-4a93-a62a-a50e26291074 Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/e32d2b99-1721-47dd-833c-98b372f48008/0d01f99a-ea6a-447d-82fd-311715434a39/8MCgDZm Replit-Helium-Checkpoint-Created: true
1 KiB
| name | description |
|---|---|
| OpenAI gpt-5 series rejects non-default temperature | gpt-5* models error on temperature != 1; omit temperature in OpenAI-compatible clients for cross-model compatibility |
OpenAI-compatible client: do not send a non-default temperature
When calling OpenAI-compatible chat/completions, the gpt-5 series (e.g. gpt-5-mini,
the Replit AI Integrations modelfarm default) returns HTTP 400 unsupported_value:
"temperature does not support 0.1 with this model. Only the default (1) value is
supported." This silently disables AI analysis (aiUsed:false, aiError set).
Rule: omit temperature from the request body for broad model compatibility,
rather than hardcoding a low value for determinism.
Why: older models accepted temperature: 0.1 but gpt-5* only accept the default.
A hardcoded low temperature breaks every scan against modern models.
How to apply: in the OpenAI-compatible AI-analysis path, do not send temperature.
If reintroducing sampling controls, gate them per model or make them optional.