i have tested both grok 4.6 and composer 2.5 but composer 2.5 complete s job in fewer tokens but grok 4.6 is consuming more tokens and usage. why?
is there any settings that i need to make or is it by default consuming more tokens for same work?
Hey @Vishwanath_Studios, thanks for the question!
This is expected rather than something misconfigured on your end. Grok 4.6 and Composer 2.5 are different models with different per-token prices and different working styles. Composer 2.5 is our in-house model tuned to finish tasks in fewer, smaller steps, while Grok 4.6 (especially at High effort) tends to reason more deeply and take more steps per task, so it reads and writes more tokens for the same work.
thanks for the update @Colin and I am eagerly waiting for a grok 4.7 , will it use less tokens for big tasks?
and how perfect can it do?