Skip to content

Add ai-status-check extension - #30152

Open
Astatine-213-Tian wants to merge 5 commits into
raycast:mainfrom
Astatine-213-Tian:ext/ai-status-check
Open

Add ai-status-check extension#30152
Astatine-213-Tian wants to merge 5 commits into
raycast:mainfrom
Astatine-213-Tian:ext/ai-status-check

Conversation

@Astatine-213-Tian

@Astatine-213-Tian Astatine-213-Tian commented Aug 12, 2026

Copy link
Copy Markdown

Description

Adds AI Status, a single Raycast command for checking the official service health of 18 common AI providers on macOS and Windows.

Check every provider at a glance

The main list groups providers by health and category, shows each provider's published status, and highlights active incidents. Providers can be enabled or disabled from the extension preferences.

Provider overview

Review incidents and their updates

Open a provider to see active and recently resolved incidents. Selecting an incident shows its published update timeline, while the action menu links back to the official status page.

Active incident

Incident timeline

Inspect component health

Provider detail pages preserve the source status page's component organization. Component groups stay compact in the main view and can be opened to inspect individual services.

Component groups

Individual components

The extension uses unauthenticated public status sources, shows cached results immediately while refreshing providers independently, and requires no provider credentials or extension-specific backend.

Checklist

  • I read the extension guidelines
  • I read the documentation about publishing
  • I ran npm run build and tested the distribution build in Raycast
  • I checked that files in the assets folder are used by the extension itself
  • I checked that assets used by the README are placed outside of the metadata folder

- docs: add Store screenshots
- refactor: standardize provider status integrations
- feat: add AI provider status extension
@raycastbot raycastbot added the new extension Label for PRs with new extensions label Aug 12, 2026
@raycastbot

Copy link
Copy Markdown
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 15 business days.

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

@greptile-apps

greptile-apps Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR adds the AI Status extension, providing cached and independently refreshed health, incident, and component information for 18 AI providers.

  • Adds provider adapters, catalog definitions, normalization utilities, and status caching.
  • Adds Raycast overview, provider detail, incident, and component views.
  • Adds deterministic adapter and domain tests plus Store metadata and documentation.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
extensions/ai-status-check/package.json Defines the extension manifest and scripts; helper scripts now compile their checked-in TypeScript sources before execution.
extensions/ai-status-check/src/hooks/use-provider-statuses.ts Coordinates cached loading and provider refreshes with per-provider ordering guards that prevent stale commits.
extensions/ai-status-check/src/services/provider-request-order.ts Implements monotonic per-provider request tokens used to reject stale refresh results.
extensions/ai-status-check/tests/support/check-store-assets.ts Validates Store assets while permitting the expected local dist build output.
extensions/ai-status-check/src/providers/registry.ts Registers the supported provider catalog and adapters used by the status command.

Reviews (5): Last reviewed commit: "feat: add provider component history" | Re-trigger Greptile

@Astatine-213-Tian
Astatine-213-Tian marked this pull request as ready for review August 12, 2026 05:34
Comment thread extensions/ai-status-check/package.json Outdated
Comment thread extensions/ai-status-check/src/hooks/use-provider-statuses.ts
- fix: make Store checks portable and order refreshes
- fix: normalize xAI operational status
@pernielsentikaer

Copy link
Copy Markdown
Collaborator

Similar extensions already in the Store

Automated first pass. Overlap is not a blocker on its own, but the README should make the difference clear.

  • AI Usage Tracker (ai-usage-tracker, 69 installs by @cdeligny) — Track your AI premium requests usage and compare it with the remaining % of working days in the current month to see if you are ahead or behind.
    similarity 0.60
  • AI Stats (ai-stats, 140 installs by @JonathanRReed) — AI model stats via Supabase
    similarity 0.58
  • Is It Alive? (is-it-alive, 32 installs by @Aler1x) — Monitor status pages and check if your favorite services are operational.
    similarity 0.55

@Astatine-213-Tian

Copy link
Copy Markdown
Author

Thanks for flagging these. I’ve updated the extension title to AI Provider Status and expanded the README to make its scope and differences clearer.

AI Usage Tracker tracks premium-request usage, while AI Stats provides AI model statistics. AI Provider Status does neither—it checks providers’ published operational health, components, and incidents.

Is It Alive? has the closest functional overlap, but its workflow is different: it is a general-purpose monitor where users add and maintain status-page URLs. AI Provider Status is purpose-built for AI services and ships with a curated catalog of 18 provider integrations. Users simply select the providers they use in Raycast preferences, with no URLs to find, detect, or maintain.

We intend to keep that curated, AI-provider-specific focus rather than add general custom status pages.

Comment thread extensions/ai-status-check/tests/support/check-store-assets.ts Outdated
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants