How can we help?

1. Open setup for Grok Bot and sign in to Pending You if you aren’t already.
2. Copy the setup message and paste it into a new chat with Grok Bot.
3. Before you press Authorize, make sure this browser is signed in to Cursor/Grok with the same account as your Grok Bot (or use a private window signed in to that account), then wait on cursor.com for “Authorization complete”.
4. When Grok Bot asks, sign in to Pending You and choose Allow.
5. Answer the test question it sends you.

Make it instant. On its own, a Grok Bot checks for your answers every 3 hours. Paste its webhook (the “POST to” and “header” rows from its routine’s Webhook panel) into the Make it instant step on the setup page, or under the Bot’s name on the Assistants page, and it hears you within seconds. Never paste them into the chat.

More than one Grok Bot. Each Bot sets up its own routine and wake-up. Paste the same setup message into each one: a Bot whose account already has Pending You skips the sign-in. On the Assistants page, each Bot’s row says what it has, and Finish setting up has a message for any Bot that’s missing one.

1. Open setup for dots and sign in to Pending You if you aren’t already.
2. Do this first in ChatGPT. Your dot can’t add a connection or change its own rules, so these two are yours, on the ChatGPT website. The setup page shows both, with what to copy.
3. Copy the setup message and paste it into a new chat with your dot.
4. Answer the test question it sends you. Your dot checks for your answers every 15 min, 7 AM–9 PM.

1. Open setup for Muse and sign in to Pending You if you aren’t already.
2. Copy the setup message and paste it into a new chat with Muse.
3. When Muse asks, sign in to Pending You and choose Allow.
4. Answer the test question it sends you. Muse checks for your answers every hour, 7 AM–9 PM.

1. Open setup for Claude Cowork and sign in to Pending You if you aren’t already.
2. Add the Pending You plugin to Claude. In Claude, open Customize › Plugins, add the marketplace recordplane/pendingyou-plugin (Add marketplace › Add from a repository) and install Pending You. Then connect its Pending You connector, sign in and allow it.
3. Copy the setup message and paste it into a new chat with Claude.
4. Answer the test question it sends you. Claude checks for your answers every hour, 7 AM–9 PM.

1. Open setup for Claude Code and sign in to Pending You if you aren’t already.
2. Copy the setup message and paste it into a new chat with Claude Code.
3. Claude Code installs the Pending You plugin, then asks you to restart it: type /exit, then run claude --continue in the same folder. Then run /mcp, choose plugin:pending-you:pendingyou, Authenticate and click Allow in your browser.
4. Answer the test question it sends you. Claude Code hears your answer while it’s working.

Hear answers instantly. Claude Code hears you while it’s working. Run npx pendingyou init once in Terminal on each Mac and your answers reach it within seconds, even when it’s idle.

1. Open setup for Codex and sign in to Pending You if you aren’t already.
2. Copy the setup message and paste it into a new chat with Codex.
3. Codex adds Pending You itself and opens your browser once: sign in and click Allow there.
4. Answer the test question it sends you. Codex checks for your answers every 15 min, 7 AM–9 PM.

Its sign-in hasn’t been proven yet, so this is a preview.

1. Open setup for Cursor and sign in to Pending You if you aren’t already.
2. Add Pending You to Cursor. Add to Cursor opens Cursor with Pending You ready to install: choose Install, then connect it when Cursor asks. Sign in, click Allow, and let your browser open Cursor again. If it goes on to cursor.com first, that browser must be signed in there with the account you use in Cursor: wait for “Authorization complete”. If Cursor doesn’t open, add this address as a server in its MCP settings. https://www.pendingyou.com/mcp
3. Copy the setup message and paste it into a new chat with Cursor.
4. Answer the test question it sends you. Cursor hears your answer while it’s working.

Don’t go Back to Pending You’s page after Allow: it works once, and going back only says it’s already allowed. If you see “You already allowed this” or “You’re already signed in” while Cursor still isn’t connected, turn the Pending You server off and on in Cursor’s MCP settings, so it starts a fresh sign-in.

ChatGPT is off the setup list for now, until it can connect more simply. A connection you already made keeps working, and you can still set it up from ChatGPT’s setup. For an OpenAI assistant that checks on its own, use dots.

1. Open setup for ChatGPT and sign in to Pending You if you aren’t already.
2. Add Pending You to ChatGPT. ChatGPT adds connectors in its settings, with developer mode on (Plus or Pro). Add a custom connector named Pending You with this address, then sign in and allow it. https://www.pendingyou.com/mcp
3. Copy the setup message and paste it into a new chat with ChatGPT.
4. Answer the test question it sends you. ChatGPT checks for your answers every hour, 7 AM–9 PM.

For Gemini and any other app that can add a remote tool server (developers know it as an MCP server).

1. Open setup for Another app (MCP) and sign in to Pending You if you aren’t already.
2. Copy the setup message and paste it into a new chat with your app.
3. When your app asks, sign in to Pending You and choose Allow.
4. Answer the test question it sends you. Your app picks up your answer when you open a chat with it.

Everything an assistant needs from you arrives as a card, one at a time on your phone and as a list on your desk. Each says what it needs:

• Choose one or Choose a few: pick from its options. The one it recommends is already selected. When none fits, the last choice is Something else…, for your own answer.
• Approval: say yes or no. Anything that spends money, can’t be undone or goes public asks you to hold the button.
• Question and Take a look: write a reply, or check what it made.
• Your move: a step only you can do, like signing in somewhere. Passwords never go through Pending You.
• Update: a notice with nothing to answer. Tap Got it, or ask the assistant to change something.

On a card with choices, pick one. When none fits, choose the last one, Something else…, and write your own answer in the box that opens. Once you’ve picked, Add a note under the choices opens the same box for a note that goes with your pick. An Approval or Your move card has Add a note too, and on Take a look, Changes opens the box for what should change. A Question’s box is open already: your reply is the answer. On your desk, T opens the box.

What you write goes to the assistant as your answer, together with any option you picked. Once you’ve written something, the card’s main button sends it and says where: “Send to” and the assistant’s name, or “Send changes” on Take a look. Enter in the box does the same, and Shift+Enter starts a new line. An Approval keeps a Send of its own in the box, for your words without a yes or no; Approve and Decline take them along. The + in the box adds files or a screenshot, up to 4.

Tap the mic in the box (or press V on your desk) to dictate. Your browser turns your voice into words in the box; the audio goes to its speech service, never to us, and nothing sends until you tap Send.

Tap Later on a card, or press L (or H) on your desk. Pick Later today, This evening, Tomorrow, This weekend or Next week, or type a time like “fri 3pm” or “3 days”. If Pending You can’t read what you typed, TypeSafe reads just those words and shows you the time before anything is set.

The card waits in Later (in the sidebar, or under You on your phone) and comes back to your stack on its own, with a notification. Bring back returns it early, and Undo is there for a few seconds after you put it off.

An area is what a card is about: Inbox, Bills, a trip, a codebase. Your assistants file each card into one, so you never make them yourself.

• Rename an area or a group right where it is: double-click its name in the sidebar, or choose Rename in its ⋯ menu (on your phone, under You › Areas). Enter keeps the new name, and Esc puts the old one back.
• Groups sort areas in the sidebar, like Work and Personal. Use Move to group… in an area’s ⋯ menu, or drag it.
• Pin to top keeps an area first in the sidebar.
• Areas with nothing new for 14 days fold under “quiet”, and leave the sidebar after 30 days until something arrives. All of them stay under Areas.

On your desk, press G anywhere, type a few letters of an area’s name and press Enter. Initials and small typos work too.

On your desk, press / to jump to the search box. It looks through what’s waiting, Later and Done: titles, areas, assistants, your own answers and the emails cards are about.

On Pending on your desk, press ? (or choose All shortcuts under the card) to see them all: J and K to move, 1–9 to choose, T to write, L for Later, E for Details, / to search and G to go to an area.

When an assistant writes on a card after you’ve answered, it comes back to you under New replies, first on Pending, with a notification. Open it to read what’s new and write back in the box underneath.

When an assistant needs a few answers for the same thing, like an email that asks three questions, they come as one card, a question at a time. Pick or write an answer and Next question takes you on; what you chose is kept as you go. Once every question has an answer, Send sends them together. If one doesn’t belong, Split into its own card.

When a card is about an email, tap its subject (or open Details) to read the email itself: who sent it, to whom, the message and its attachments. Images stay hidden until you choose Show images.

A recipe is a message you paste into your assistant. It sets up one job that uses Pending You, like sending you the Gmail that needs your decision, or asking before your coding agent deploys, and your assistant asks you only what’s yours to decide, as cards here. Set up Pending You for your assistant first.

Each recipe’s page says what it does, which assistants it works with and what it will never do. Copy the whole recipe, or the one-line version, which has your assistant read it from the page. In the app, Assistants › Recipes lists them, the ones your assistants can follow first: Set up asks which assistant should do it and writes the line with its name in. Add a recipe in an assistant’s ⋯ menu shows just the ones it can follow.

A service like Cloudflare can post notices to Pending You through an incoming webhook. On your desk, open Assistants › Incoming webhooks › New webhook, name it for what it sends and pick its area. Its notices arrive as updates.

Every email has a link and a 6-digit code, and both work for 15 minutes. Mail apps such as Gmail open links in their own browser, which forgets you as soon as you leave it, and links never open in the Pending You app on your Home Screen.

• Type the code instead. Go back to Pending You where you asked for the email (Safari, or the app on your Home Screen) and type the 6 digits there.
• Add Face ID. After you sign in, choose Use Face ID, or later add a passkey under You › Sign-in methods (Settings on your desk). Then you sign in with a glance, no email needed.
• No email after a minute? Look in spam or promotions for mail from signin@pendingyou.com.

Each connection page works once, for 10 minutes. Go back to your assistant and start connecting again: it opens a fresh page, where you sign in and choose Allow.

For Cursor and Grok Bot, sign in to cursor.com in your browser with the right account (the one you use in Cursor, or your Grok Bot’s) before you start again. Grok Bot’s sign-in always finishes there and Cursor’s often does; signed in as anyone else, the app never connects.

Both mean you already chose Allow and Pending You sent your sign-in on, so close the tab and go back to your assistant. If “You’re already signed in” kept appearing while your assistant asked you to sign in again, that was a bug, and it’s fixed: start connecting again from your assistant.

Still not connected? Start again from the app. For Cursor and Grok Bot, sign in to cursor.com with the right account first. In Cursor, turn the Pending You server off and on in its MCP settings to start a fresh sign-in.

Most assistants check for your answers on a schedule, so an answer can wait until the next check. To hear sooner:

• Tell it. Say “done” (or that you answered) in your chat with it, and it checks right away.
• Grok Bot: Make it instant. Paste the Bot’s webhook (“POST to” and “header”, from its Pending You routine’s Webhook panel) under its name on the Assistants page, and it hears you within seconds.
• Claude Code: hear answers instantly. Run npx pendingyou init once in Terminal.

How often each assistant checks is in its setup steps above.

Your assistant may still be using an old connection, such as one to a test site or another account. Restart its session (in Claude Code, type /exit and run claude --continue) so it loads its current connection, then ask it to try again.

Still nothing, or it says it’s already set up? Check that the Pending You address in its settings is https://www.pendingyou.com/mcp, and that you’re signed in to the same account here. If not, remove that connection in the app and set it up again from the setup page.

With Claude Code’s instant answers on, npx pendingyou status says “Mismatch” when a session is on a different Pending You.

Pending You notifies you when an assistant has stopped for you, a deadline is close, a card comes back from Later or there’s a new reply. While it’s open on your computer, your phone stays quiet.

• iPhone: notifications only reach Pending You on your Home Screen. In Safari, tap Share, then Add to Home Screen, open it from there and allow notifications. Show me how
• Blocked: allow notifications for Pending You in your phone’s or browser’s settings, then turn them on again.
• Muted, or a Focus on: Mute (in the sidebar on your desk, or under You on your phone) holds them until the time you chose, and your device’s Focus or Do Not Disturb holds them too.
• Test it: Send test, under You on your phone or Settings › Notifications on your desk, sends one now.

On the Assistants page, choose Send a test on the webhook. Pending You delivers a sample notice as if your service had posted it, and “Test from” the webhook’s name appears in its area. A paused webhook counts the test without showing it.

The test arrives but your service’s notices don’t? Your service doesn’t have the whole address. Lost it? Replace it on the Assistants page (the old one stops working at once) and give your service the new one.