[BUG] Tool calls fail with "No such tool available: bash/glob/skill" in Claude Code across all providers (manual config, setup-claude, and launch --profile)

[klsatapathy]

OmniRoute Version

v3.8.49 (also reproduced after upgrade attempt to v3.8.50)

Installation Method

npm (global)

Operating System

Windows

OS Version

Windows 10 (Build 19045.6466)

Node.js Version

v24.16.0

Provider(s) Involved

Antigravity, OpenCode Free, OpenRouter (reproduced across multiple providers, not provider-specific)

Model(s) Involved

antigravity/claude-sonnet-4-6, antigravity/claude-opus-4-6-thinking, oc/deepseek-v4-flash-free, and combo "main-project-combo"

Client Tool

Claude Code v2.1.223

Description

When using Claude Code connected to OmniRoute (via ANTHROPIC_BASE_URL), every
tool call fails with "Error: No such tool available: <lowercase_name>"
(bash, glob, skill, etc.). This happens regardless of which provider/model
is selected, and persists across three different connection methods:

1. Manual ANTHROPIC_BASE_URL + ANTHROPIC_API_KEY in ~/.claude/settings.json
2. Official omniroute setup-claude generated profiles
3. omniroute launch --profile <name> launcher

Claude Code declares tools in PascalCase (default_api:Bash, default_api:Glob)
per its system prompt, but the tool call that gets rejected arrives lowercase
(bash, glob, skill) — suggesting a casing mismatch somewhere in OmniRoute's
request/response translation layer between Claude Code and non-Anthropic-native
providers.

Steps to Reproduce

1. Install OmniRoute (npm install -g omniroute), run omniroute
2. Connect any provider (Antigravity, OpenCode Free, OpenRouter all reproduce this)
3. Connect Claude Code using any of the 3 methods above
4. In Claude Code, ask it to do anything requiring tool use, e.g.:
   "Ek React To-Do app bana do" (create a React app with file creation)
5. Observe repeated "Error: No such tool available: bash/glob/skill" until
   the model gives up and outputs code as plain text instead of creating files

Expected Behavior

Tool calls (Bash, Glob, Read, Write, Skill, etc.) should execute successfully
through OmniRoute regardless of casing conventions used by the underlying
provider/model, since Claude Code's tool schema is fixed and OmniRoute is
acting as the translation layer.

Actual Behavior

All tool calls fail with "No such tool available: ",
making Claude Code effectively unusable for any agentic/file-editing task
through OmniRoute — the model can only respond with code as text, which
the user must then manually copy into files themselves.

Test Impact

Unsure

Error Logs / Output

An integration test that spins up OmniRoute, connects a Claude Code client, 
sends a prompt that triggers a Bash/Glob/Write tool call, and asserts the 
tool call resolves successfully (not rejected with "No such tool available") 
would have caught this regression.

Error: No such tool available: bash
Error: No such tool available: bash
Error: No such tool available: glob
Error: No such tool available: skill

Screenshots

No response

Additional Context

Reproduced with a single dedicated model (antigravity/claude-sonnet-4-6) as
well as with a multi-provider combo (main-project-combo mixing Antigravity/
OpenCode/OpenRouter models) — same error in both cases, ruling out combo
routing as the cause. Also reproduced after a full factory reset
(rmdir ~/.omniroute + fresh install) and after using the official
omniroute setup-claude profile generator, ruling out a corrupted manual
config as the cause.

Validation Plan

1. Run the reproduction steps above with any free provider connected
2. Confirm Claude Code can successfully create/edit a file without
   "No such tool available" errors
3. Confirm this works both with a single-model profile and a multi-model combo

[Shadin403]

I can reproduce the exact same issue with Claude Desktop/Cowork, not only Claude Code.

Environment:

• Claude Desktop
• Third-party inference / custom gateway
• OmniRoute
• Gateway: https://omniroute.shadin.info/v1

Claude Desktop declares tools as:
default_api:Glob
default_api:Bash
default_api:Read
default_api:Write
default_api:Edit
default_api:Grep

But the runtime rejects the calls as:
Error: No such tool available: glob
Error: No such tool available: bash
Error: No such tool available: grep

I have already verified that:

• Disabled built-in tools is empty
• Glob = allow
• Bash = allow
• Read = allow
• Write = allow
• Edit = allow
• Grep = allow

So this appears to be the same tool-name/casing translation issue described in #9575, but reproduced in Claude Desktop/Cowork as well.