What shipped: more Codex questions reach your phone
October's Pushary update brings typed Codex questions and supported browser approvals to your phone, with more reliable setup and updates in CLI 1.9.60.
More Codex questions can now reach you through Pushary, including questions that need a written answer and supported browser permission requests. Setup and updates also handle more of the cases that previously left a connection unfinished.
This update summarizes Pushary CLI 1.9.57 through 1.9.60, published here on October 15, 2026. The full CLI changelog records each release separately.
Answer questions in your own words
Sometimes an agent needs more than a yes or no. It needs you to explain what you want.
Since CLI 1.9.57, supported Codex questions without suggested choices reach Pushary as text questions. Your written answer goes back to Codex. If a call contains several supported questions, the CLI asks them one after another. Mac-managed sessions depend on the app version; the Codex guide records those differences.
A blank answer is not passed on as a decision. If you hand the question back or nobody answers, Codex shows its own card. Questions that need a secret remain in Codex.
Browser questions can reach you too
With Codex app cards enabled on Mac, CLI 1.9.59 adds three browser questions: site access, downloads, and uploads. Each names the site and reaches Pushary as a yes or no question. The first answer wins. This also requires Pushary for Mac 0.1.103 or later when the Mac app manages the connection.
For downloads and uploads, yes allows that transfer. Site access follows the scope Codex assigns to its own question, such as the conversation or the current turn. Broader choices like “always” remain in Codex. Developer Tools access, browsing history, verification codes, and sign-in questions also remain there.
Turn the option on with:
pushary codex --app-cards onThen quit Codex and open it again. The setup guide explains the switch and how to turn it off.
The question includes the URL path, but excludes its query string and fragment. Treat the path as information you are sending to Pushary; do not assume it is always free of sensitive details.
Fewer unfinished updates
Version 1.9.58 improves recovery when an upgrade finishes installing but does not finish refreshing the agent connection. Running the upgrade again can finish that step. It also keeps the Codex app-card connection working across supported CLI updates while Codex is open.
Version 1.9.60 fixes temporary mode expiry when you use the equals form of the time flag. For example, pushary mode terminal_only --for=30m now expires after 30 minutes as intended. Setup also respects the active Claude configuration directory.
These are small changes with a practical purpose: less time repairing the connection before you can get back to your work.
Update and check your connection
npx pushary@latest upgrade
pushary doctorThe upgrade command installs the current published version. This article covers behavior through 1.9.60; later versions may include more changes.
Read the version-by-version release notes for details, or the agent quickstart if you are connecting Pushary for the first time.