Suggest a request check or report a version difference
#2
by alphabell-research - opened
Which Rec MLX integration trap should this checker cover next?
Useful reports include a minimal public JSON request or just the relevant fields, the Rec version, and the actual server diagnostic. If a setting behaves differently on your version, include that version so the source-pinned checks can stay precise.
The current checker targets Rec MLX v0.1.0. It reviews request settings locally and links each diagnostic to the inspected source. It does not run model inference, compile tool schemas or measure generation quality.
Existing examples cover ignored reasoning controls, integer spellings, grammar/stop conflicts, competing output caps and forced tool calls. Suggestions for a small reproducible case are welcome.