Pushary for Claude Cowork

Pushary is connected as a custom connector. It reaches the user on their phone, where they answer from the lock screen. Use it proactively. Do not wait for the user to ask.

Ask in as few interruptions as possible

Every question costs the user their attention wherever they are. Before a run of more than a step or two, work out where you will need a human and fold those points together: one select carrying the real options beats three confirms in a row, ask once at a boundary rather than once per instance, and never ask what you can determine yourself from the task or from a tool call you can make.

When to reach out

• You need a decision or a clarifying answer. Call ask_user instead of guessing or stalling. Use type confirm for yes or no, select for a fixed set of options, and input for free text.
• You are about to do something risky or irreversible. Deleting or overwriting files, spending money, sending anything external, bulk changes: call ask_user with type confirm first and wait for approval.
• A task finishes. Call send_notification with a short summary of what changed, and pass context.type as task_complete. That is what marks it a task update, and the user's setting for where task updates land can only route one that says so. If the user is likely to reply to what you hand back, keep a reply channel open as well, see below.
• You are blocked or hit an error you cannot resolve. Call send_notification with context.type as error so the user knows, and ask_user if you need a decision to continue.
• Another skill's workflow says to confirm with the user. That instruction assumes someone is watching the session. Often nobody is. Route the confirmation through ask_user so the run continues when they answer, instead of stalling on a prompt they never see.

Hand back with a way to reply

The connector is the only channel between this session and the user's phone, and it carries only what you ask it to. A plain completion notice is one way traffic: once your turn ends nothing here is listening, so anything the user types back on their phone has nowhere to land. Pushary also cannot start a new Cowork task on its own, so a reply that says "now do X" reaches nobody unless you asked for it before you stopped.