[terence71-glitch]

Summary

This PR makes the web-search fallback bypass explicit for native Claude → Claude passthrough requests.

The web-search fallback rewrites built-in web search tools into OmniRoute's omniroute_web_search function for providers that cannot execute web search natively. Codex native passthrough and Gemini targets were already bypassed, but Claude → Claude passthrough was only protected indirectly because Anthropic's current versioned tool type, web_search_20250305, was not part of the exact-match fallback matcher.

This change adds an explicit bypass when both sourceFormat and targetFormat are Claude, so native Anthropic web-search tools are forwarded untouched to the Claude upstream.

Changes

• Add Claude → Claude native web-search bypass in supportsNativeWebSearchFallbackBypass().
• Keep OpenAI-format clients targeting Claude on the fallback conversion path.
• Add predicate coverage for native Codex passthrough, Gemini target, Claude → Claude passthrough, and negative cases.
• Add end-to-end body behavior tests for:
  • Claude native web_search_20250305 forwarding
  • Claude bare web_search forwarding
  • Codex web_search_preview forwarding
  • OpenAI → Claude fallback conversion

Why

Claude Code / Anthropic Messages passthrough requests may include native Anthropic web-search tools. These should be handled by the Claude upstream, not rewritten into OmniRoute's fallback function.

The new bypass is intentionally narrow:

• sourceFormat === "claude"
• targetFormat === "claude"

This avoids breaking non-native requests such as OpenAI-format clients targeting Claude, where the tool still needs to be converted.

Validation

Focused regression tests pass:

node --import tsx --import ./open-sse/utils/setupPolyfill.ts --test tests/unit/web-search-fallback-format.test.ts

13 tests
13 pass
0 fail

Focused lint completed with no errors:

npx eslint open-sse/services/webSearchFallback.ts tests/unit/web-search-fallback-format.test.ts

Note: lint reports one warning for an existing explicit any in the committed test file:

tests/unit/web-search-fallback-format.test.ts
  224:47  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

[gemini-code-assist]

Code Review

This pull request introduces a Claude-to-Claude native web search bypass in supportsNativeWebSearchFallbackBypass to forward native Claude tools untouched, and adds comprehensive unit tests covering the new bypass logic. The review feedback suggests improving type safety in the tests by replacing an explicit 'any' type assertion with a more specific type shape to avoid linter warnings.

[gemini-code-assist]

Using any triggers the @typescript-eslint/no-explicit-any linter warning. We can replace Record<string, any>[] with a more specific, type-safe shape that avoids any while still allowing direct property access to function and name.

  const tools = (body.tools as Array<{ function?: { name?: string }; name?: string }>) || [];

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• open-sse/services/webSearchFallback.ts — added sourceFormat parameter and Claude→Claude bypass
• tests/unit/web-search-fallback-format.test.ts — comprehensive predicate + e2e coverage

Inline Comments (0)

No inline issues flagged.

Other Observations

• Test file carries an existing explicit any (linter warning at line 224, noted in PR description but not addressed). Not introduced by this PR.
• Nothing in the diff appears risky or erroneous. The fallback bypass symmetry (Codex / Gemini / Claude) is well-scoped and the OpenAI→Claude negative test correctly protects the conversion path.

---

_{Reviewed by step-3.7-flash-20260528 · 1,016,378 tokens}

[diegosouzapw]

Thank you for your contribution! This PR has been reviewed and integrated into the upcoming v3.8.8 release. 🎉