Skip to main content
Your workspace runs on Convex, in a project that belongs to you. Connecting Convex is the step where that project gets made: one button on the setup page, one approval in Convex, and Nudge takes it from there.

​
Before you start

You need a Convex account. If you don’t have one, Convex asks you to make one during this step; it’s free. Convex organises projects into teams; on the approval screen you pick the team and then create the project Nudge will live in. A team of one is fine. Convex bills you directly, under your own account. You can start on the free plan. Whether a workspace stays inside it depends on how much it does: how many contacts, how many messages and calls a day. Convex shows your usage in its dashboard, so you see it coming before you pay anything.

​
What happens when you click

1

Connect Convex

On the setup page, after you’ve named your workspace, press Connect Convex. Convex opens in the same tab.
2

Approve Nudge in Convex

Sign in to Convex, pick the team, create a project called Nudge, and approve. This is the click only you can make: Nudge, and any agent you’re using, can’t do it for you.
3

Nudge creates the project

Back on the setup page, Nudge has given that project a production deployment and kept one key to it. The page shows the deployment’s name and the last four characters of the key.
Nudge only installs into an empty project. If something goes wrong, the setup page says what, and you can press Connect Convex again. Once Convex is connected, your workspace’s name is fixed.

​
What the key lets Nudge do

Nudge doesn’t keep your Convex sign-in. What it keeps is one deploy key, named nudge-control, stored encrypted. Convex ties that key to the one project you approved, and to nothing else, so:
  • Inside that project it can put Nudge’s code there and update it, change the project’s settings, run its functions, read its data and logs, and pause it. That is what running and updating your workspace takes.
  • Outside that project it can do nothing: not your other projects, not your Convex account, not your billing.
If you pick a region on the setup page, a new project’s production deployment is made there (Europe or the United States); otherwise Convex uses your team’s default.

​
Revoking the key

In the Convex dashboard, open the Nudge project, go to the production deployment’s Settings, and delete the deploy key whose name starts with nudge-control. Your workspace keeps running on the version it has. Nudge can’t update it or fix it any more, and within a day your admins see a banner in the app: “Nudge can’t reach your backend to update it”. To put things right, go back to the setup page and press Connect Convex again. You approve the same project, and Nudge mints a new key for the project you already have and deletes the old one at Convex. Nothing is reinstalled.
Deleting the key is also how you leave. Your project and all its data stay in your Convex account. See Pausing and leaving.
Next: Set up with Claude Code or Codex, or carry on by hand on the setup page.