fix: wire reasoning parser from worker runtime config into frontend

[MatejKosec]

Summary

• The frontend's get_parsing_options() in ModelManager hardcoded reasoning_parser to None (with a TODO comment), so reasoning_content was always null in API responses regardless of the worker's --dyn-reasoning-parser setting.
• Added get_model_reasoning_parser() method (mirrors existing get_model_tool_call_parser()) that reads reasoning_parser from the worker's RuntimeConfig via service discovery.
• Updated get_parsing_options() to call the new method instead of returning None.

Test plan

• Deployed on Nebius with GLM-Z1-0414-A3B (FP8, tp4) using --dyn-reasoning-parser deepseek_r1
• Confirmed reasoning_content is populated in streaming responses via both OpenAI (/v1/chat/completions) and Anthropic (/v1/messages) endpoints
• Verified non-reasoning models are unaffected (reasoning_parser remains None when not configured)

Summary by CodeRabbit

• New Features

  • Added capability to retrieve model reasoning parsers from model configurations.

• Improvements

  • Enhanced model parsing options to integrate reasoning parser information for improved AI model handling.

[coderabbitai]

Walkthrough

A new public method get_model_reasoning_parser() was added to the model manager to retrieve a model's reasoning parser from model cards. The existing get_parsing_options() method was updated to use this new method instead of a None placeholder for reasoning parser retrieval.

Changes

Cohort / File(s)	Summary
Model Reasoning Parser Retrieval lib/llm/src/discovery/model_manager.rs	Added get_model_reasoning_parser() method to fetch reasoning parsers from model cards and updated get_parsing_options() to use it.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A parser for reasoning, so fine and so new,
Model managers fetch what the cards say is true,
Options flow cleaner with each tiny hop,
Eight lines of clarity—improvement won't stop! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: wiring the reasoning parser from worker runtime config into the frontend, which aligns with the core fix of updating get_parsing_options() to use the new get_model_reasoning_parser() method.
Description check	✅ Passed	The description includes all required template sections (Overview/Summary, Details, Where to start, and Related Issues), provides clear context about the problem and solution, includes comprehensive test plan with deployment verification, and is well-structured and complete.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jthomson04]

yolo