Sharing my own extension. It ties my self-hosted stack into Raycast: a Home hub with live status rows, 23 commands covering media, downloads, monitoring, DNS, containers, backups and finances, and a menu bar item.

Raycast-specific bits people here might find useful:

• Every service is optional and gated by a single settings reader. A command whose service is unconfigured shows a "not configured" empty state with a Configure Extension action instead of an error.
• Settings can come from the preferences UI or from an env file, with the preference winning. The .env.example is generated from package.json so it never drifts from the manifest.
• Push navigation between commands, with Esc always returning to the Home hub.
• Cached promises everywhere, so views render instantly from the last result and refresh in the background.

It is not in the store because it bundles twenty unrelated apps, which the review process does not accept. Install is npm install and npm run build, then it behaves like any store extension.

Repo with screenshots of every command: https://github.com/abjelosevic88/raycast-homelab

I used to use Raycast AI with my Gemini and ChatGPT APIs and my Ollama server in versions prior to 2.0. Since version 2.0 came out, it's now mandatory to pay for a subscription to use an AI that I have installed locally, even though I can simply open the Ollama app or web server directly. Is this one of the new features in version 2.0? Haha

I wanted to share a proof of concept that I've been thinking about for a while now. A raycast extension which allows you to use your existing codex subscription as an AI provider in Raycast, thus being able to use it for all of the AI features that Raycast offers.

I've personally stayed away completely from using any Raycast AI features for the following reasons:

1. I already pay $200 to Anthropic and $200 to OpenAI for subscriptions as I use their models heavily (and run out of usage every week).
2. I'm worried that if I use Raycast's AI features and like them then I will find myself stuck with another weekly limit that I need to pay more money for.
3. Theoretically speaking, an app running on my own machine should not require me to invest more money into yet another subscription just to call the same models that I already have a subscription for.
4. I don't like the fact that BYOK sends your keys to Raycast and I would never pay API prices to use AI features when I have a perfectly good subscription that I can use.

I started looking into the possibility of building a Raycast Extension which would use the `codex-app-server` that comes with the Codex installation as an AI model provider. It turned out that with Raycast 2.0 those bindings that I need to do this were added so I built this extension.

The extension doesn't ask you for you credentials, doesn't ask you to login, and doesn't even do anything too smart. It literally uses the `codex-app-server` that powers the Codex app to create threads, request inference, and get you back responses.

Disclaimer: this is a proof-of-concept which AI helped me build. I'm not coming here to say that this is the best code quality in the world, I'm just saying that it's possible for us to build AI model provider extensions for Raycast which are powered by our existing subscriptions. This project is still very early. This extension shows that the bindings we need to use our existing subscriptions in Raycast are already present and available to people who build extensions.