Skip to content

Update raycast-ai-custom-providers extension#25180

Open
Ernest0-Production wants to merge 1 commit intoraycast:mainfrom
Ernest0-Production:ext/raycast-ai-custom-providers
Open

Update raycast-ai-custom-providers extension#25180
Ernest0-Production wants to merge 1 commit intoraycast:mainfrom
Ernest0-Production:ext/raycast-ai-custom-providers

Conversation

@Ernest0-Production
Copy link
Contributor

@Ernest0-Production Ernest0-Production commented Feb 5, 2026

Description

A Raycast extension that allows you to manage custom AI provider settings through a convenient interface. The extension works with the providers.yaml file used by Raycast AI to configure external providers (see documentation here).

Screencast

raycast-ai-custom-providers-1 CleanShot 2026-02-05 at 22 53 17@2x

Checklist

@raycastbot raycastbot added new extension Label for PRs with new extensions platform: macOS labels Feb 5, 2026
@raycastbot
Copy link
Collaborator

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 10-15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

@Ernest0-Production Ernest0-Production marked this pull request as ready for review February 5, 2026 18:53
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 5, 2026

Greptile Overview

Greptile Summary

This PR adds a new extension for managing custom AI provider configurations through a GUI interface. The extension allows users to create, edit, and delete providers and models in the ~/.config/raycast/ai/providers.yaml file.

Key changes:

  • Provider management UI with list view and detailed forms
  • YAML file read/write with automatic backup functionality
  • Support for all provider configuration options (API keys, models, abilities, additional parameters)
  • Form validation and error handling

Issues found:

  • Critical: Empty title field in package.json preference configuration (line 43) - this will cause validation errors
  • Critical: Logic bug in ProviderForm.tsx (line 469-472) where failed parseInt stores a string instead of number, causing type inconsistency
  • Non-essential files included: cursor/ directory (editor config), .backup file, and potentially the template YAML file

Confidence Score: 3/5

  • This PR has two critical bugs that must be fixed before merging
  • Two critical issues prevent safe merging: the empty preference title in package.json will fail validation, and the type inconsistency bug in ProviderForm.tsx will cause runtime errors when users enter invalid context values. Additionally, unnecessary files (cursor config, backup file) should be removed.
  • Pay close attention to package.json and src/components/views/ProviderForm.tsx for the critical fixes

Important Files Changed

Filename Overview
extensions/raycast-ai-custom-providers/package.json preference title is empty (line 43), which is invalid
extensions/raycast-ai-custom-providers/src/components/views/ProviderForm.tsx logic bug in context field parsing (line 469-472) stores string instead of number on parse failure
extensions/raycast-ai-custom-providers/cursor/code-style.mdc editor-specific configuration that should not be committed
extensions/raycast-ai-custom-providers/ai-providers.template.yaml.backup backup file that should not be committed to the repository

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4 files reviewed, 5 comments

Edit Code Review Agent Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new extension Label for PRs with new extensions platform: macOS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants