Gemini CLI setup

Pushary puts Gemini CLI's risky tool calls on your phone. Native Gemini hooks (small programs Gemini runs around each tool call) check your Pushary policy before each shell command, file write, edit and MCP call, and the ones that need a person wait for your answer. Gemini CLI has no --dangerously-skip-permissions. Its --yolo flag approves everything, and a deny from your phone still blocks the call.

Set it upCopy Anchor Link

npx pushary@latest setup

On Windows PowerShell, run npx.cmd pushary@latest setup. The CLI needs Node.js 20.17+, 22.13+ or 23.5+.

On a Mac you can use Pushary Isle instead. It connects Gemini CLI for you and needs no Node.

What setup changes on your computerCopy Anchor Link

Setup also installs the pushary package globally, so each hook starts fast.

What each hook doesCopy Anchor Link

Check that it worksCopy Anchor Link

npx pushary@latest doctor

Doctor checks your key and plan, then Gemini's MCP server, hooks and GEMINI.md block. It sends a real test push. Add --roundtrip to send a test question too.

Then try a real approval. A new workspace starts on Always, so it reaches your phone while you sit at your computer. If yours is on When away, decisions are left to Gemini's own prompt while you are there. To test from your desk, open the Pushary app, tap Questions & approvals at the top of your inbox, and pick Always.

Ask Gemini: Create a file called pushary-test.txt that says hello. Your phone buzzes with the write request. Tap Approve and the file appears. Switch back to When away when you are done.

What Pushary can and cannot enforce on Gemini CLICopy Anchor Link

Gemini's tools have different names from Claude Code's, so Pushary maps them onto your existing rules:

One rule works across every agent. A rule you set for Bash also gates run_shell_command. File reads and other Gemini tools are not gated.

Gemini's hook protocol has no "ask" answer. When Pushary leaves a call to Gemini, it prints nothing and Gemini's own confirmation runs. That happens:

• in In agent and Alert only modes,
• in When away, when you are at your computer, when nobody answers your phone in time, or when Pushary cannot be reached,
• in Always, when no phone is connected, when Pushary hands the call back to your keyboard, or when nobody answers and your rule says Ask in terminal.

In Always, a question Pushary could not send at all is refused.

Gemini CLI --yolo and dangerously skip permissionsCopy Anchor Link

Gemini CLI has no --dangerously-skip-permissions flag. The equivalent is gemini --yolo (short form -y, or --approval-mode yolo), which approves every tool call with no prompt. Ctrl+Y toggles it inside a session. Use it only in a throwaway or sandboxed environment.

Pushary does not make yolo safe. Every call Pushary leaves to Gemini runs with no prompt under yolo. That includes a question nobody answered when the rule says Ask in terminal, a call handed back to your keyboard, a call made while your plan has lapsed, and a call where the hook itself failed.

To answer fewer prompts in the terminal and still approve risky calls on your phone, stay in Gemini's default or auto_edit mode and set your Pushary approval mode to Always. Gated calls go to your phone. Anything Pushary hands back falls to Gemini's own approval mode, so a shell command still gets a prompt instead of running unchecked. Under auto_edit, an edit Pushary hands back runs without a prompt, so use default if every hand-back should prompt.

See Gemini dangerously skip permissions for the approval modes and Antigravity CLI's flag.

Set it up by handCopy Anchor Link

Use setup if you can. It pins each hook command to its full path.

Install the Pushary CLI globally, unless which pushary-gemini-hook already prints a path. An existing install under @pushary/agent-hooks provides the same commands, and npm refuses to install over them.

npm install -g pushary

Add the MCP server to ~/.gemini/settings.json. Replace the token with your API key:

{
  "mcpServers": {
    "pushary": {
      "httpUrl": "https://pushary.com/api/mcp/mcp",
      "headers": { "Authorization": "Bearer pk_xxx.xxx" },
      "trust": true
    }
  }
}

Add the hooks under the same top-level object. Replace /path/to/pushary-gemini-hook with the output of which pushary-gemini-hook, and use the same path in every entry. Gemini counts hook timeouts in milliseconds.

{
  "hooks": {
    "BeforeTool": [
      {
        "matcher": "run_shell_command|write_file|replace|mcp_.*",
        "hooks": [{ "name": "pushary", "type": "command", "command": "/path/to/pushary-gemini-hook", "timeout": 180000 }]
      }
    ],
    "AfterTool": [
      {
        "matcher": "run_shell_command|write_file|replace|mcp_.*",
        "hooks": [{ "name": "pushary", "type": "command", "command": "/path/to/pushary-gemini-hook", "timeout": 10000 }]
      }
    ],
    "BeforeAgent": [
      { "hooks": [{ "name": "pushary", "type": "command", "command": "/path/to/pushary-gemini-hook", "timeout": 10000 }] }
    ],
    "AfterAgent": [
      { "hooks": [{ "name": "pushary", "type": "command", "command": "/path/to/pushary-gemini-hook", "timeout": 10000 }] }
    ],
    "SessionStart": [
      { "hooks": [{ "name": "pushary", "type": "command", "command": "/path/to/pushary-gemini-hook", "timeout": 10000 }] }
    ],
    "SessionEnd": [
      { "hooks": [{ "name": "pushary", "type": "command", "command": "/path/to/pushary-gemini-hook", "timeout": 10000 }] }
    ]
  }
}

Save your key in your shell profile so the hook can read it:

export PUSHARY_API_KEY="pk_xxx.xxx"

Restart Gemini CLI, then run npx pushary@latest doctor.

TroubleshootingCopy Anchor Link

Gemini still asks in the terminalCopy Anchor Link

That is expected when Pushary leaves the call to Gemini, for example at your desk in When away mode. See the list under What Pushary can and cannot enforce on Gemini CLI.

The hooks never runCopy Anchor Link

• Restart Gemini CLI. It reads ~/.gemini/settings.json at start.
• Check that ~/.gemini/settings.json has a hooks.BeforeTool entry that runs pushary-gemini-hook.
• Run npx pushary@latest doctor. It lists any hook event that is missing.

Gemini CLI stopped working with my Google accountCopy Anchor Link

Google moved Google AI Pro, Ultra and free accounts to Antigravity CLI. Set up Antigravity CLI instead.

Setup says Pushary for Mac handles Gemini CLI's approvalsCopy Anchor Link

The Mac app already owns Gemini's hooks. Setup reuses the app's key and keeps the app's hooks. To have the CLI own them instead, run npx pushary@latest setup --take-over-hooks.

Next stepsCopy Anchor Link