Skip to content

Disable Claude Code thinking to unblock Opus 4.7 gateway calls#102

Open
jxk590 wants to merge 1 commit into
databricks:mainfrom
jxk590:feature/claude-error
Open

Disable Claude Code thinking to unblock Opus 4.7 gateway calls#102
jxk590 wants to merge 1 commit into
databricks:mainfrom
jxk590:feature/claude-error

Conversation

@jxk590
Copy link
Copy Markdown

@jxk590 jxk590 commented May 27, 2026

Claude Code sends thinking.type=enabled on outbound requests, which the Databricks AI Gateway rejects for adaptive-only models (Opus 4.7 family) with a 400. The gateway expects thinking.type=adaptive + output_config.effort. Claude Code does support that shape but only when its model-name pattern matches a known Anthropic id — the gateway exposes models as databricks-claude-opus-4-7, so the prefix throws off detection and Claude Code falls back to the legacy enabled shape. The result: ucode claude validation fails and the config is reverted.

Set CLAUDE_CODE_DISABLE_THINKING=1 in the Claude Code env block so the field is omitted entirely. The gateway still applies adaptive reasoning server-side on Opus 4.7 (where it's mandatory), so reasoning quality is preserved on the new family. Older models lose client-side extended thinking through the gateway, which is the correct tradeoff for a configuration that actually works end-to-end.

Claude Code sends `thinking.type=enabled` on outbound requests, which
the Databricks AI Gateway rejects for adaptive-only models (Opus 4.7
family) with a 400. The gateway expects `thinking.type=adaptive` +
`output_config.effort`. Claude Code does support that shape but only
when its model-name pattern matches a known Anthropic id — the gateway
exposes models as `databricks-claude-opus-4-7`, so the prefix throws
off detection and Claude Code falls back to the legacy `enabled`
shape. The result: `ucode claude` validation fails and the config is
reverted.

Set `CLAUDE_CODE_DISABLE_THINKING=1` in the Claude Code env block so
the field is omitted entirely. The gateway still applies adaptive
reasoning server-side on Opus 4.7 (where it's mandatory), so reasoning
quality is preserved on the new family. Older models lose client-side
extended thinking through the gateway, which is the correct tradeoff
for a configuration that actually works end-to-end.
@rohita5l rohita5l requested a review from AarushiShah-db May 27, 2026 17:41
@AarushiShah-db
Copy link
Copy Markdown
Collaborator

AarushiShah-db commented May 27, 2026

@jxk590 I'm not able to reproduce the original issue - can you please share a detailed repro of how you came across this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants