Fix planner model deprecation (sarvam-30b -> sarvam-105b) and the logged Hindi skip-ahead bug - #6
Conversation
Set out to fix the known bug logged in PARKING_LOT.md ("सीधे submit पर ले
चलो" resolves to the wrong step) and found something more urgent while
re-verifying it live: Sarvam deprecated sarvam-30b sometime between 2026-07-26
and 2026-07-31. A live planner call now returns a hard 400
("Model 'sarvam-30b' has been deprecated... use sarvam-105b"), which the
planner correctly turns into a null and falls back to the deterministic
StepEngine - but that means the planner, one of the five frozen core pieces,
has been silently dead for every real call in the meantime, with nothing
surfacing it beyond a debug-panel note nobody was watching.
- Sarvam.PLANNER_MODEL -> "sarvam-105b", re-verified live against the same
six-case regression set used on 07-26 (scripts/planner_case.ps1, updated
to match).
- planner_v1.md now enumerates skip-ahead phrasing across languages
explicitly instead of one English example. Re-verified live: the exact
failing case now returns step=submit.
- Documented in docs/PARKING_LOT.md, honestly: the model swap is a net
latency regression (roughly doubled, 1261-3300ms vs 867-1481ms - still
capped by the existing 5s call timeout), and one case's behavior changed
in a way that isn't clearly better or worse (a "I made a mistake"
correction on the first step now moves forward instead of re-prompting).
Not chasing that further in this pass - logged, not silently smoothed over.
- Corrected two other things found stale while in this file: the
Parked-items note claiming Tamil isn't authored (it is, from the taxi
work), and every remaining "Sarvam-30B" reference in prose/docs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
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. Comment |
Reviewer's GuideThis PR swaps the deprecated Sarvam planner model from sarvam-30b to sarvam-105b, updates the planner prompt to correctly handle multilingual skip-ahead requests (fixing a logged Hindi bug), and refreshes documentation, scripts, and contributor guidance to reflect the new model and its latency/behavior characteristics. Sequence diagram for Sarvam-105B planner call and deterministic fallbacksequenceDiagram
title Sarvam-105B planner sequence with deterministic StepEngine fallback
actor User
participant SessionController
participant SaarasStt
participant SarvamPlanner
participant SarvamApi
participant StepEngine
participant OverlayService
participant SarvamTts
User->>SessionController: mic_tap
SessionController->>SaarasStt: SarvamStt
SaarasStt-->>SessionController: transcript + language
SessionController->>SarvamPlanner: SarvamPlanner
SarvamPlanner->>SarvamApi: Sarvam.plannerHttp (model sarvam-105b)
alt [plannerHttp succeeds]
SarvamApi-->>SarvamPlanner: set_plan
SarvamPlanner-->>SessionController: step + target + instruction + language
SessionController->>OverlayService: OverlayService
SessionController->>SarvamTts: SarvamTts
else [plannerHttp 400 deprecation or other failure]
SarvamApi-->>SarvamPlanner: null
SarvamPlanner-->>SessionController: null
SessionController->>StepEngine: StepEngine
StepEngine-->>SessionController: step + target (deterministic)
SessionController->>OverlayService: OverlayService
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @NITISH-R-G, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
1 participant
What changed
Set out to fix the logged bug (Hindi "skip ahead" resolving to the wrong step) and found something more urgent while re-verifying it live against the real API:
sarvam-30bhas been deprecated by Sarvam sometime between 2026-07-26 and now. A live call returns a hard 400 (Model 'sarvam-30b' has been deprecated... use sarvam-105b). The planner correctly nulls out and falls back to the deterministic engine on that error - by design, nothing crashes - but it means the planner (one of the five frozen core pieces) has been silently non-functional for every real call since the deprecation, with no visible signal beyond a debug-panel note.Sarvam.PLANNER_MODEL->sarvam-105b.planner_v1.mdnow spells out skip-ahead phrasing across languages instead of one English example.Why
The model deprecation is a production-breaking issue that would otherwise have shipped invisibly - CI has no live-key smoke test (correctly, since CI never has a key), so nothing would have caught this until a demo run went quiet on the planner.
What was tested
scripts/planner_case.ps1, six cases, all against livesarvam-105b:step=amount, correctstep=amount, Devanagari, correctstep=amount, correctstep=submit- fixedstep=account- see caveat belowstep=amount, Tamil script, correctassembleDebug+testDebugUnitTestgreen.Still needs verification
docs/PARKING_LOT.mdrather than hidden.Summary by Sourcery
Swap the Sarvam planner from the deprecated sarvam-30b model to sarvam-105b and document the resulting latency and behavioral changes, while fixing Hindi skip-ahead handling in the planner prompt and keeping core contracts conceptually consistent.
Bug Fixes:
Enhancements:
Documentation:
Tests: