← PusharyCONTENT HISTORY
WHAT CHANGED
Update to Pushary
Snapshot Oct 24, 2026 · 13:18 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Pushary and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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.",
"included_files": [],
"name": "pushary-setup",
"skill_md_contents": "---\nname: pushary-setup\ndescription: 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.\n---\n\n# Set up Pushary\n\nPushary 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.\n\n## 1. Send one test question\n\nTell the user in one line that you are sending a test question to their phone through Pushary. Then call `ask_user`:\n\n```json\n{\n \"question\": \"Pushary is connected. Did this reach your phone?\",\n \"type\": \"confirm\",\n \"context\": \"Test question from Pushary setup. Answer yes or no.\",\n \"agentName\": \"ChatGPT - Pushary setup\"\n}\n```\n\nIn Codex, use `Codex - Pushary setup` as the `agentName`.\n\n## 2. Read the result\n\nCheck these in order and act on the first that matches.\n\n- **Pushary refused the connection.** Go to step 3.\n- **`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.\n- **`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.\n- **`answered` is `true`.** Tell the user the connection works and what they answered. Go to step 4.\n- **`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.\n- **`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.\n\nTo 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.\n\n## 3. When Pushary refuses the connection\n\nIf 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.\n\nIf Pushary says this account is a viewer on its workspace, show that message as it is and end setup.\n\nIf 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.\n\nDo 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.\n\n## 4. Show the user what to ask for\n\nTell the user they can add any of these to their own request, in any chat where Pushary is on:\n\n- **Before a task:** \"Plan this, then send the plan to my phone so I can approve it before you start.\"\n- **During a task:** \"Keep going and ask me on my phone before any step you can't undo.\"\n- **After a task:** \"When you're done, send a summary to my phone with what you did and what's left.\"\n\nAdd one sentence: a question they do not answer is never treated as a yes. Then stop. Do not start a task the user did not ask for.\n"
}SHA-256 of public snapshot: 6ac6b3368d5b252ad524d96acc434d2eb091ae3c8ac760e0bc2bba2663bc1797