Grok Build
Connect Pushary to Grok Build, xAI's terminal coding agent. Approve shell commands, edits and MCP calls from your phone, or add the Pushary plugin so Grok asks you questions and sends a push when work finishes.
Updated
Grok Build is xAI's coding agent for the terminal. Pushary connects to it in one of two ways:
| Pushary setup | Pushary plugin | |
|---|---|---|
| Install | npx pushary@latest setup --agents grok | grok plugin install Pushary/grok-build-plugin |
| Approve shell commands, edits and MCP calls from your phone before they run | Yes, through Grok's hooks | No |
| Grok asks you questions and sends a push when work finishes | Yes | Yes |
| A question waits for your answer | Until you answer or it is cancelled | Up to 10 minutes |
| Adds hooks to your computer | Yes, the Pushary hook runs on each tool call | No |
| Signs in with | A Pushary key that setup stores | Your Pushary account, in the browser |
Both need a paid Pushary plan for your own agents, such as Agent, Agent Pro or Team, and the Pushary app on your phone, or the Mac app, signed in to the same account.
This guide is for Grok Build. For the Grok Bot app, see Grok Bot.
Approve tool calls from your phone
Install Grok Build with xAI's installer and run grok once to sign in. Then run:
npx pushary@latest setup --agents grokOn Windows PowerShell, run npx.cmd pushary@latest setup --agents grok. The CLI needs Node.js 20.17+, 22.13+ or 23.5+.
Scan the QR code with your phone
Setup shows a QR code. Scan it with your phone's camera or the Pushary app. Sign in or create an account, check that the code on your phone matches the one in your terminal, then tap Approve on Connect this computer? and allow notifications. If this computer already has a Pushary key, setup reuses it and skips this step.
Answer the test question
Setup sends a test push, then a test question. Answer it on your phone. The terminal says You're set once your answer arrives.
Start a new Grok session
Grok loads hooks when a session starts. Run /hooks inside Grok and check that the Pushary hooks are listed.
Setup writes three files under ~/.grok, or under $GROK_HOME when you set it:
hooks/pushary.json: the hooks. Before Grok runs a shell command, edits a file or calls an MCP tool, the call goes through your Pushary policy, and the risky ones wait for your answer on your phone.config.toml: apusharyMCP server with your key, so Grok can ask you questions and send you a push.rules/pushary.md: when Grok should reach you.
Setup leaves Grok's permission mode unchanged, and Grok's own permission checks still apply after you approve on your phone. Grok's own question and plan dialogs stay in Grok.
Grok fails open: if it kills the Pushary hook or cannot start it, the tool call proceeds. Grok's own permission mode and deny rules still apply.
Add the Pushary plugin
The plugin connects Grok to Pushary's hosted MCP server and adds the pushary skill. It installs no hooks. If the Pushary tools are not connected, the skill can have Grok look for an existing Pushary install, check it with npx pushary@latest status, or offer to install Pushary with the Mac app or the setup command above. Grok runs those commands like any other, under your permission mode.
Install the plugin
grok plugin install Pushary/grok-build-pluginSign in
Start Grok, run /mcps, select pushary and press i. Sign in in the browser with the same Pushary account your phone uses, and allow access. Grok registers itself with Pushary during sign-in, so there is no client ID or key to enter.
Sign in once in the interactive app. Headless runs such as grok -p cannot open a browser, so they skip a server that has no stored sign-in, and use the one you stored here.
Send a test question
Ask Grok:
Use Pushary to ask me "Did this reach you?" as a yes or no question, with
agentName "Grok Build - Setup check". Wait for my answer and tell me what I chose.Answer it on your phone. Grok telling you your answer confirms the connection.
With the plugin, Grok gets six tools: ask_user, wait_for_answer, cancel_question, propose_scope, send_notification and schedule_reminder. See the tools reference. It cannot read or change your policies, subscribers, campaigns or API keys. A question asked through this sign-in closes 10 minutes after it is sent, and a question that closes unanswered is never treated as a yes. Everything you connect by signing in to Pushary shares one limit: 10 notifications or reminders per 5 minutes, 25 open questions, and 8 open questions for one Grok session.
If you run setup after installing the plugin, Grok uses the pushary server setup added to config.toml in place of the plugin's, so your questions stay open until you answer them. You can keep the plugin or remove it with grok plugin uninstall pushary.
Disconnect
To remove setup's hooks, MCP server and rules, run:
npx pushary@latest disconnect grokTo remove the plugin, run grok plugin uninstall pushary. Your Pushary account and its history stay as they are.
Troubleshooting
Grok does not ask before a risky command
The hooks load when a session starts. Start a new session and run /hooks. If the Pushary hooks are missing, run setup again. The plugin alone never gates tool calls.
The plugin's tools return an authorization error
Run /mcps, select pushary and press i to sign in again. Run grok mcp doctor pushary to check the connection.