You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case, not just a vague idea.
Area
apps/server
Problem or use case
Grok Build already exposes slash/skills catalog, per-model reasoning effort, and context usage over ACP, but T3 leaves those dark for Grok while Claude/Codex surface them.
Still missing on T3 Code Nightly 0.0.34-nightly.20260812.1079 + Grok CLI 1.0.3 (macOS).
Composer has no Reasoning / thinking control for Grok 4.6. Claude and Codex show the control; Grok does not. Turns stay on the Grok CLI default.
Workaround: set default_reasoning_effort in ~/.grok/config.toml and start a new T3 Grok thread. That is global, not a per-thread toggle.
Grok itself advertises the effort menu (low / medium / high / xhigh for 4.6). This looks like T3 publishing Grok models with empty capabilities instead of mapping ACP _meta.reasoningEfforts into the existing composer picker.
Activity
Amadeus415 commentedon Aug 12, 2026
Still missing on T3 Code Nightly
0.0.34-nightly.20260812.1079+ Grok CLI1.0.3(macOS).Composer has no Reasoning / thinking control for Grok 4.6. Claude and Codex show the control; Grok does not. Turns stay on the Grok CLI default.
Workaround: set
default_reasoning_effortin~/.grok/config.tomland start a new T3 Grok thread. That is global, not a per-thread toggle.Grok itself advertises the effort menu (
low/medium/high/xhighfor 4.6). This looks like T3 publishing Grok models with empty capabilities instead of mapping ACP_meta.reasoningEffortsinto the existing composer picker.Related: #5403, #5503.