The two clicks that stay yours
An agent can’t sign in as you, and it shouldn’t. Two steps happen in your browser:- Signing in with Google on the setup page. That’s how the page knows you’re approved, and it’s where the connector comes from.
- Approving Nudge in Convex. When the agent gets to Connect Convex, it gives you a link. Open it, pick your team, approve, and tell the agent you’re done.
Add the connector
Sign in on the setup page and pick With Claude Code or Codex. The page shows three snippets, each with your own key already filled in. Use the one that fits. Claude Code, one command. Paste it into a terminal:.mcp.json:
~/.codex/config.toml:
bearer_token_env_var = "NUDGE_SETUP_TOKEN" in place of the http_headers line, and run export NUDGE_SETUP_TOKEN=<your key> in the terminal before you start Codex.
Start it
Give the agent this prompt:What the agent can do
The connector gives the agent these tools. It picks them itself; you don’t need to name them, but it helps to know what’s there. Setting up
Inside your workspace, once it’s live
None of the tools deletes anything. An automation the agent writes arrives switched off: switching it on is a separate step, and the agent should tell you what it does and who it reaches before it asks to.
Templates and automations belong to a person, so they work after you’ve signed in to your workspace once. When the install finishes, open your workspace and sign in with Google before you ask the agent for them.