You can build a working Raycast extension using Claude Code in about an hour. No coding knowledge required. Here's how I built one that searches Pipedrive directly from the Raycast bar.
If you use Raycast, you're probably used to relying on extensions other people have built. Anything that doesn't have a published extension, you work around. Until recently, that was my situation too.
I built my own no-code Raycast extension that searches my Pipedrive account directly from the Raycast bar. No browser, no clicking into search fields. I'm not a developer. I used Claude Code.
Here's how it went.
What the extension does
The extension connects to the Pipedrive API and runs a live search from inside Raycast. I set up a hotkey so when I type “PD”, the extension launches immediately. It shows recently updated deals, people and organisations. As I type a query, it filters results in real time.
Clicking a result opens the record directly in Pipedrive. It also shows useful details without needing to open a browser: email addresses, phone numbers, deal status (won, lost, active).
Starting with a simple prompt
I opened the Code tab in the Claude desktop app (Pro plan, using Opus 4.6) and gave it a basic prompt: help me build a Raycast extension to search Pipedrive.
I suggested one approach: using the extension to open a Pipedrive browser tab and paste a search query using a keyboard shortcut. Claude said that would work, then suggested an alternative: use the Pipedrive API and show results natively inside Raycast. It asked which I preferred.
I said: definitely the API approach.
What Claude did next
I won't pretend I fully understood the technical steps. Claude researched the Pipedrive API, figured out how Raycast extensions work, and built the custom Raycast integration as a set of files in a new folder on my Mac. It appeared in my home directory under a Claude Code folder, named Pipedrive Search.
Once it was done, it provided installation instructions.
Installing via Terminal
This is where I got stuck. Installing a local Raycast extension requires Terminal and Node.js, neither of which I'd used before.
Raycast extensions are built with React and TypeScript and run through Node.js. The process at a high level:
- Install Node.js. Download and install the LTS version from nodejs.org. This is what Raycast extensions run on.
- Open Terminal and navigate to your extension folder. Terminal is a standard Mac application. You use the
cdcommand to move into the folder Claude created, for examplecd ~/path-to-your-extension. - Install dependencies. Run
npm installinside the extension folder. This downloads everything the extension needs to run. - Start development mode. Run
npm run dev. Raycast detects this and automatically loads your extension, making it available immediately.
I asked Claude to walk me through each of these steps. It did, clearly, and handled the parts I didn't understand when I asked follow-up questions.
Raycast's developer docs cover this in full: developers.raycast.com
Troubleshooting
First run had two problems: the logo didn't display and the search returned no results.
I reported both to Claude. It updated the extension files and told me to try again. At one point I said I was confused by one of its instructions. Its response: you don't need to do anything, just try it again. The search started working.
The logo took a bit longer to resolve. I also made a few tweaks along the way, sorting recently updated contacts and deals to the top and adding recently viewed items to the default state before any search query is typed.
Total time from first prompt to working extension: about an hour.
What I'd do differently
A colleague pointed out the obvious gap in my approach: front-load the initial prompt with as much detail as possible. Instead of starting with a basic request and then layering on requirements, describe everything you want upfront. It produces a better first version and avoids the back-and-forth of tacking on changes afterwards.
That's the key lesson. If you know what you want, describe it fully from the start.
Worth trying
If you're a Raycast user and there's no extension for a tool you rely on, try building one. You don't need to understand the code. You need a clear description of what you want. Claude Code handles the rest.
FAQ
Q: Do I need to know how to code to build a Raycast extension with Claude Code? No. This extension was built by someone with no coding knowledge. Claude Code writes the code, installs dependencies and troubleshoots errors.
Q: What tools do I need? Raycast (Mac), a Claude Pro subscription with access to Claude Code and Terminal (standard on every Mac). You'll also need Node.js, which Claude will help you install.
Q: How long does it take? This example took about an hour from first prompt to working extension, including troubleshooting and a few iteration rounds.
Q: What's the most important thing to get right? The initial prompt. The more detail you give Claude about what you want the extension to do, the better the first version will be.