feat(server): add a reasoning effort picker for Grok

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.

[torarinvik]

What changed

Grok models now show the same reasoning picker Codex, Claude, and Cursor already have. The levels come from the Grok CLI itself, not from a hardcoded list.

Grok advertises them per model over ACP in ModelInfo._meta.reasoningEfforts, along with the level currently applied in _meta.reasoningEffort. It applies one through session/set_model with _meta: { reasoningEffort: "<level>" }. T3 was ignoring both, so every Grok model shipped with empty capabilities and the composer traits menu showed only the Access section.

File	Change
acp/GrokAcpSupport.ts	Parse the levels out of the ACP model _meta, read the session's applied effort, and extend applyGrokAcpModelSelection to carry an effort
Layers/GrokProvider.ts	Discovered models get a reasoningEffort select descriptor instead of empty capabilities
Layers/GrokAdapter.ts	Track the applied effort on the session; apply the selection at session start and per turn
acp/AcpSessionRuntime.ts	setSessionModel takes optional request _meta

No client changes were needed — web and mobile both render the picker generically from optionDescriptors, with no per-provider branching.

Before / after

The composer traits menu on Grok 4.6.

Before	After

Levels are genuinely per model, so Grok 4.5 gets its own shorter list rather than 4.6's:

Decisions worth reviewing

Which level is marked default. Grok flags more than one level as default (4.6 marks both xhigh and high), so the flags alone are ambiguous. The level actually applied to the model wins, and default is only the fallback.

Effort-only changes resend the model.session/set_model is what carries the effort, so changing effort without changing model re-sends the model Grok already has selected. session/set_mode and model-id suffixes (grok-4.5:low) do not work — I probed both against grok 1.0.4 and only the _meta route applies.

Models that fail discovery get nothing. The grok-build fallback used when ACP discovery fails keeps empty capabilities. The levels are per model, and inventing a list for a model we could not probe risks sending an effort it does not accept.

Changing effort mid-thread is allowed. Only the model is gated behind requiresNewThreadForModelChange, which this does not touch.

Verification

• checkGrokProviderStatus against the real CLI returns Grok 4.6 with xhigh/high/medium/low (medium default) and Grok 4.5 with high/medium/low (high default).
• End-to-end in the app: selected a level, sent a turn, and confirmed Grok's own session record (~/.grok/sessions/.../chat_history.jsonl) stamps each assistant message with the effort it ran at — low → medium → high across turns, exactly tracking the picker. The persisted thread selection reads {"id":"reasoningEffort","value":"low"} and session/set_model goes out with the _meta field present.
• New unit tests cover metadata parsing, default resolution, and each set_model application path (model-only, effort-only, both, neither).
• vp run -r typecheck, vp lint, and the server provider suite (563 tests) all pass.

Note that asking Grok what effort it is running at is not a valid check — it has no tool for that and will answer from ~/.grok/config.toml, which the per-session override deliberately does not rewrite.

Follow-up, not included here

Separately and pre-existing: we create the ACP session on Grok's default model and then call session/set_model, but Grok renders its system prompt at session creation, so it keeps saying "You are Grok 4.6" while routing 4.5. session/new accepts _meta.modelId (verified — the resulting session's stored prompt says "You are Grok 4.5"), which would fix it. Left out to keep this PR to one thing; happy to send it separately if wanted.

Disclosure

This was written by Claude Opus 5 running in Claude Code, at medium reasoning effort with fast mode on, driven and reviewed by me. The protocol findings above (what Grok advertises, what actually applies an effort, what does not) come from probing the installed grok 1.0.4 CLI directly, not from documentation or guesswork. The before/after screenshots are real captures of this branch versus main.

---

Note

Medium Risk
Changes Grok session model configuration and ACP set_model behavior at start and per turn; logic is covered by tests but incorrect effort handling could affect live Grok runs.

Overview
Grok models can now expose a Reasoning select in the composer traits menu, aligned with other providers. Levels are read from Grok ACP ModelInfo._meta (reasoningEfforts / reasoningEffort) instead of hardcoded empty capabilities.

applyGrokAcpModelSelection now takes current and requested reasoning effort, returns { modelId, reasoningEffort }, and calls session/set_model when either the model or effort changes. Effort is sent as _meta.reasoningEffort; effort-only updates re-send the current model id. On model switches without an explicit effort, prior effort is not carried over so unsupported levels are not applied to the target model.

GrokAdapter tracks currentReasoningEffort on the session and applies user selections at session start and on each turn via provider option reasoningEffort. AcpSessionRuntime.setSessionModel accepts optional request _meta for that payload. Discovered Grok models get capabilities from buildGrokModelCapabilities. Unit tests cover metadata parsing, default resolution, and set_model paths.

^{Reviewed by Cursor Bugbot for commit 11f2f17. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add reasoning effort picker for Grok models

• Adds a Reasoning select option to Grok model capability descriptors for models that advertise reasoning levels, sourced from model _meta via grokReasoningEffortLevelsFromModelMeta.
• Extends applyGrokAcpModelSelection to accept and return reasoningEffort; triggers session/set_model for effort-only changes and attaches reasoningEffort in request _meta.
• Persists currentReasoningEffort in GrokSessionContext so each turn can update effort independently of model ID changes.
• Extends AcpSessionRuntime.setSessionModel to forward an optional meta object as _meta in the request payload.
• Behavioral Change: switching models no longer carries over the previous reasoning effort unless explicitly requested.

^{Macroscope summarized 11f2f17.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0b2c16fc-963c-4794-9b4f-934d0ae1ea6e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit c7b7a54. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature (reasoning effort picker for Grok) that modifies core model selection interfaces and propagates new configuration through multiple code paths. New feature enablement with behavioral changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing this PR after an automated pass over open pull requests. Duplicates trusted Grok reasoning controls in #6386.