Connected app tools break when using external LLM routing

[Al629176]

Summary

When an external LLM provider is enabled with custom routing, connected app actions stop working from chat. The agent can answer normally, but tasks that require connected tools, such as sending an email or fetching live data, are treated as unavailable or limited to generic web fetching.

Problem

What happened:

1. Connect an external LLM provider, such as OpenAI, and enable custom routing for chat.
2. In chat, ask for a live-data task, such as checking today’s news.
3. Then ask the agent to use a connected app action, such as sending an email through Gmail.
4. The agent reports that it cannot use the connection or that its capabilities are limited, even though the app connection should be available.

Expected:

When custom routing uses an external LLM, the orchestrator should still receive and use the user’s connected app tools. External provider routing should only change the model provider, not remove Gmail, Composio, or other connected integration capabilities.

Impact:

Users who bring their own external model cannot reliably use connected app workflows. This blocks core tasks like email, calendar, Slack, and other integration actions.

Version / platform:

• Staging desktop build
• macOS desktop
• External LLM provider enabled with custom routing

Solution (optional)

Investigate the external-provider routing path and confirm whether connected tool catalogs are being dropped, filtered, or replaced when chat routes to a non-default model. Ensure connected integration tools remain model-visible and executable regardless of the selected LLM provider.

Acceptance criteria

• Repro gone — With an external LLM provider enabled and custom chat routing selected, connected app tools remain available in chat.
• Gmail workflow works — A connected Gmail account can be used for an email action through chat when routed through the external provider.
• Tool surface preserved — Provider routing changes the model only; it does not drop Composio or connected-app tool catalogs.
• Helpful error path — If a connected app is genuinely missing scopes or disconnected, the agent reports that specific connection problem instead of saying it has no connected-tool capability.
• Regression safety — Unit or integration coverage verifies that external LLM routing preserves connected tool availability.
• Diff coverage ≥ 80% — the fix PR meets the changed-lines coverage gate (Vitest + cargo-llvm-cov, enforced by .github/workflows/coverage.yml).

Related

• Similar prior regression: Connected app tools are unavailable after enabling an external LLM #2605