Skip to content

chore(ai-gateway): remove unused MORPH provider and morph warp grep model#4004

Merged
chrarnoldus merged 1 commit into
mainfrom
chore/remove-morph-provider
Jun 12, 2026
Merged

chore(ai-gateway): remove unused MORPH provider and morph warp grep model#4004
chrarnoldus merged 1 commit into
mainfrom
chore/remove-morph-provider

Conversation

@chrarnoldus

Copy link
Copy Markdown
Contributor

Summary

  • Removed the morph_warp_grep_free_model (morph-warp-grep-v2) Kilo-exclusive model and deleted providers/morph.ts.
  • Removed the MORPH gateway provider from provider-definitions.ts and dropped 'morph' from the ProviderId union — the only model routed through this gateway was the one removed above, so it is no longer used.
  • Added 'morph-warp-grep-v2' to forbiddenFreeModelIds so stale clients receive an appropriate error (per the AI gateway policy for removed free models).
  • Updated the OpenRouter suppression test to use the existing hidden gemma_4_26b_a4b_it_free_model instead of the removed morph model.

Verification

  • No manual verification performed. Changes are code-removal only against an already-hidden, unused model/provider.

Visual Changes

N/A

Reviewer Notes

  • The 'morph' entries in openrouter/inference-provider-id.ts (OpenRouterInferenceProviderIdSchema and VercelNonUserByokInferenceProviderIdSchema) are intentionally left in place — those are external upstream inference provider IDs for routing/BYOK on OpenRouter and Vercel, distinct from our internal MORPH gateway provider.

…odel

Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
@chrarnoldus chrarnoldus self-assigned this Jun 12, 2026
@kilo-code-bot

kilo-code-bot Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

Clean removal of the unused MORPH gateway provider and morph-warp-grep-v2 Kilo-exclusive model, with correct tombstoning in forbiddenFreeModelIds per the AI gateway policy.

Files Reviewed (5 files)
  • apps/web/src/lib/ai-gateway/forbidden-free-models.ts'morph-warp-grep-v2' correctly added to forbidden list
  • apps/web/src/lib/ai-gateway/models.tsmorph_warp_grep_free_model import and kiloExclusiveModels entry removed
  • apps/web/src/lib/ai-gateway/providers/morph.ts — file deleted
  • apps/web/src/lib/ai-gateway/providers/provider-definitions.tsMORPH provider definition removed
  • apps/web/src/lib/ai-gateway/providers/types.ts'morph' removed from ProviderId union
  • apps/web/src/lib/ai-gateway/providers/openrouter/index.test.ts — suppression test updated to use gemma_4_26b_a4b_it_free_model (confirmed status: 'hidden', valid substitute)

Fix these issues in Kilo Cloud


Reviewed by claude-4.6-sonnet-20260217 · 504,825 tokens

Review guidance: REVIEW.md from base branch main

@lambertjosh

Copy link
Copy Markdown
Contributor

Did we get rid of the experimental option already client side?

@chrarnoldus

Copy link
Copy Markdown
Contributor Author

I don't know, but this stopped working a long time ago.

@chrarnoldus chrarnoldus merged commit 3b86a63 into main Jun 12, 2026
16 checks passed
@chrarnoldus chrarnoldus deleted the chore/remove-morph-provider branch June 12, 2026 19:53
@chrarnoldus

Copy link
Copy Markdown
Contributor Author

I'll make a PR

iscekic added a commit that referenced this pull request Jun 13, 2026
…ests

Main merged PR #4004 which deleted the morph provider. The two test files
that exercised the rejection branch of modelServesAllGatewayChatApis used
morph as the only available Kilo-exclusive model on a chat_completions-only
gateway. With morph gone, no real catalog entry satisfies that condition.

Both test files now stub findKiloExclusiveModel via jest.mock/requireActual
so that the marker id 'test-exclusive/alibaba-only' returns a KiloExclusiveModel
with gateway: 'alibaba'. The real PROVIDERS.ALIBABA definition supports only
chat_completions, so the rejection path is exercised without relying on any
specific provider file being present in the catalog.
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