Pushary

View saved version →

---
name: pushary-chatgpt
version: 0.3.1
description: Reach the user on their phone through Pushary while ChatGPT or Codex works on a task. Use it to get a plan approved before starting, to ask before a step the user has not approved, and to send one summary when the work is done or fails. Use for requests such as get my approval on my phone first, ask me on my phone before anything you can't undo, I'm stepping away, ping me when it's done, send me a summary, or remind me later. Honor approvals the user already gave and follow the server's delivery policy.
metadata:
  tags: planning, approvals, human-in-the-loop, notifications, push, chatgpt, codex
---

# Pushary for ChatGPT and Codex

Pushary connects this chat to the user's phone. You send a question or an update, the user gets a push, and their answer comes back to you. Yes or no questions can be answered from the lock screen where the phone supports it; choices and typed answers open the Pushary app. Every question and answer is recorded in Pushary.

You decide when to call Pushary. It does not watch or block your actions, so the rules below are yours to follow.

## Tools

| Tool | Use it to |
| --- | --- |
| `ask_user` | Ask one question and get the answer: `confirm` for yes or no, `select` for two to six options, `input` for a fact only the user knows. |
| `wait_for_answer` | Keep waiting for a question that is still pending, with its `correlationId`. |
| `cancel_question` | Withdraw a question that is no longer needed. |
| `send_notification` | Tell the user something: a finished task, a failure, or an update they asked for. |
| `schedule_reminder` | Set a one-time personal reminder, when the user asks to be reminded later. |
| `propose_scope` | Record the boundary of a run so the user can agree to it. |

Pass `agentName` on every call as the host and the task, for example `ChatGPT - Q3 board deck` or `Codex - invoice audit`. Pass the same `sessionId` for the whole conversation. Do not call yourself another host.

## What the user asks for, and what to do

| The user says | Do this |
| --- | --- |
| "Plan this first, then get my approval on my phone." | Write the plan. Send it as one `confirm` question with the steps in `question`. Start only after a yes. On a no, ask what to change. |
| "Ask me on my phone before anything you can't undo." "I'm stepping away." | Work. Before each step in the list below, ask with `ask_user`. Keep going with work that does not depend on the answer. |
| "Ask me at every decision." | Ask each real choice as one `select` question with your recommended option first. |
| "Ping me when it's done." "Send me a summary." | When the work ends, send one `send_notification` with `context.type` set to `task_complete` and the result in `summary`. |
| "Tell me if something breaks." | On a failure you cannot fix, send `send_notification` with `context.type` set to `error`. |
| "Remind me in 30 minutes." | Call `schedule_reminder`. Tell the user the time it returns. |
| "Send a test question." | Send one harmless `confirm` question and report what the user answered. |

The user does not have to say "Pushary". "Ask me on my phone", "get my approval" and "ping me" mean these tools.

## Before the task: get the plan approved when asked

Ask for plan approval only when the user asked for it, or when the plan goes beyond what they asked you to do. A task with many steps does not need a plan approval by itself. Start `question` with a short line the lock screen can show, such as "Approve the plan for the Q3 board deck?", then list the steps after it. `question` holds up to 8,000 characters; `context` holds only 500, so use `context` for one line of background, never for the plan.

## During the task: ask before a step the user has not approved

Ask with `ask_user` before any of these, unless the user already approved it in this conversation:

- **Something that cannot be undone.** Deleting, overwriting or replacing something the user made.
- **Something that le

Preview of the first 4,000 characters. Read full instructions →

View saved version →

---
name: pushary-setup
description: Run once, right after Pushary is installed. Sends one test question to the user's phone to prove the connection works, handles an account that is not set up yet, and then shows the user what they can ask Pushary for before, during and after a task.
---

# Set up Pushary

Pushary sends your questions and updates to the user's phone and brings their answer back to this chat. Setup proves that with one test question, then shows the user what to ask for. Keep every message to the user short and plain.

## 1. Send one test question

Tell the user in one line that you are sending a test question to their phone through Pushary. Then call `ask_user`:

```json
{
  "question": "Pushary is connected. Did this reach your phone?",
  "type": "confirm",
  "context": "Test question from Pushary setup. Answer yes or no.",
  "agentName": "ChatGPT - Pushary setup"
}
```

In Codex, use `Codex - Pushary setup` as the `agentName`.

## 2. Read the result

Check these in order and act on the first that matches.

- **Pushary refused the connection.** Go to step 3.
- **`noDevices` is `true`.** No phone, browser or Slack can receive it yet. Cancel the test as described below; it was only a test, so do not ask it in this chat. Tell the user to install the Pushary phone app from https://pushary.com/download, sign in with the same Pushary account they connected here, and allow notifications. Send the test again when they say the app is ready.
- **`status` is `notified` or `terminal`.** The user's Pushary delivery setting keeps questions off their phone. Cancel the test as described below, tell them they can change how questions reach them in Pushary's settings, and go to step 4.
- **`answered` is `true`.** Tell the user the connection works and what they answered. Go to step 4.
- **`status` is `pending`.** Tell the user a test question is waiting for them in Pushary. If they do not have the Pushary phone app yet, tell them to install it from https://pushary.com/download and sign in with the same Pushary account; the question is waiting there. Keep calling `wait_for_answer` with the same `correlationId` while the status is `pending`. If your reply has to end first, tell the user to answer on their phone and then tell you here, and call `wait_for_answer` with that `correlationId` before anything else next time.
- **`status` is `expired`, `cancelled` or `missing`.** The test question stays open for 10 minutes. Say it was not answered and offer to send it again. It was only a test, so do not ask it in this chat.

To cancel the test, call `cancel_question` with its `correlationId`. If cancellation returns `handoffAction: "stop"`, stop there. If it returns `cancelled: false`, call `wait_for_answer` once for one second; an answer means the user answered the test after all, so go to step 4.

## 3. When Pushary refuses the connection

If Pushary says the account has no site yet, show the user that message exactly as it is, with its link. Tell them to finish setup there and then come back to this chat. Do not call Pushary again until the user says setup is done. Then go back to step 1.

If Pushary says this account is a viewer on its workspace, show that message as it is and end setup.

If Pushary says the account is not active, tell the user Pushary cannot reach their phone until their Pushary account is active again, and end setup.

Do not mention prices, plans or payment, and do not pass on an upgrade link. For an account with no site, Pushary's own message carries the link the user needs.

## 4. Show the user what to ask for

Tell the user they can add any of these to their own request, in any chat where Pushary is on:

- **Before a task:** "Plan this, then send the plan to my phone so I can approve it before you start."
- **During a task:** "Keep going and ask me on my phone before any step you can't undo."
- **After a task:** "When you're done, send a summary to my phone with what you did and what's left."

Add one sentence

Preview of the first 4,000 characters. Read full instructions →