Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Runcrate as a provider type, next to Opper and Requesty:
Runcrateenum member,RuncrateConfigand its place inALL_PROVIDER_TYPES(tauri/client.ts)https://api.runcrate.ai/v1and the/modelsfetch, in the id-only group with Opper and Requesty (settings/provider/api.ts)IconServericon, the same one Requesty uses (provider-icon.tsx)database/ai/services.ts)Runcrate serves open-weight models (DeepSeek, Qwen, GLM, Kimi, gpt-oss and others) through an OpenAI-compatible API with one key. Chat goes through
/v1/chat/completionsand the model list comes fromGET /v1/models, which returns the OpenAI{ data: [{ id }] }shape. Model ids look likedeepseek-ai/DeepSeek-V4.1-Flash.Keys: https://runcrate.ai/dashboard/api-keys
Docs: https://runcrate.ai/docs/models/chat-completions
Testing
npx tsc --noEmit -p .: passes.npx oxfmt --checkon the four changed files: all use the correct format.npx vite build: builds.defaultBaseURL/normalizeBaseURLandProviderType.Runcratefrom the changed files and uses the same calls as the app with Node'sfetchin place of the Tauri one:GET {base}/modelswith the same zod schema returned HTTP 200 and 126 models includingdeepseek-ai/DeepSeek-V4.1-Flash, andcreateOpenAICompatible({ name: 'openai-compatible', ... })withgenerateTexton that model returnedpong(finish reasonstop). I did not run the Tauri app itself.This PR was prepared with AI assistance (omp with Claude): the code changes and this description were written with it, and the commands and live calls above were run as described.