whiskSign in

Guides

Use Whisk with Cursor

Cursor is where you write the app. It isn't where your team uses it. To get a Cursor app in front of other people, give Cursor's agent one prompt and it moves the app onto Whisk for you. You approve one login, and the agent hands back a web address your team can sign in to.

This page covers the Cursor side of that: the settings to check first, what the agent does in your project, and the questions people usually ask.

Before you start

Three things in Cursor make the job go smoothly.

  • Use the agent, not a plain chat. The work needs someone to run commands, and only the agent does that.
  • Let it run terminal commands. It installs the Whisk command line and runs it. If Cursor asks before each command, say yes. If you run Cursor in a sandbox that blocks the internet, allow whisk.run.
  • Commit what you have. The agent changes a few files. If you commit first, you can see exactly what it changed, and undo it if you want.

The prompt

Open your app's folder, start the agent and paste this:

Read https://whisk.run/skill and follow it to deploy this app to Whisk. Install the whisk command line if it isn't installed. Adapt the app to Whisk's rules: sign-in comes from Whisk, not from the app, and data goes in the Postgres database Whisk provides. Run whisk doctor until it passes, then deploy, and tell me the web address.

What you'll see happen

First the agent reads Whisk's instructions. Then it runs whisk login, which shows a web address and a short code. Open the address, sign in to Whisk or create an account, check the code matches, and approve it. You won't be asked again on that computer.

Next it edits your project. It adds a file called whisk.yaml that tells Whisk what the app is. If the app has its own sign-in page, the agent takes it out, because Whisk signs people in before they reach the app. If the app saves data to a file or the browser, the agent moves it into a proper database. Any keys for other services come out of the code.

Then it runs whisk doctor. That's Whisk's check, and it lists anything that doesn't fit yet. You'll see the agent fix, check, fix, check, until it passes. That's normal.

Last, it runs whisk deploy and gives you a web address like https://quotes.your-team.whisk.page. If the app needs keys for other services, the agent tells you their names and where to enter them in Whisk. You type them in yourself, so they never go into the chat.

Questions people ask

Does everyone on my team need Cursor? No. Only the person building does. Everyone else opens the web address in a browser and signs in. Invite them from the app's page in Whisk.

Do I need to keep Cursor or my laptop open? No. Once it's deployed, the app runs on Whisk. Close the laptop and it keeps going, schedules included.

How do I change the app later? Keep working in Cursor as you do now, then ask the agent to deploy. Whisk checks each new version before it goes live. If a database change fails, Whisk undoes it and the old version keeps running.

Can I try a change without the team seeing it? Yes. Work on a separate git branch and deploy from there. It gets its own preview address, and the live app doesn't change.

What does it cost? Your first app is free, forever, for up to three people on your team. Starter is $49 (US) a month for 10 apps and as many people as you like. Bigger plans hold 50 or 200 apps. See pricing.