fx setup

Pushary connects to fx through MCP (Model Context Protocol, the standard way AI apps call outside tools). One setup command gives fx's agent Pushary's tools and turns off fx's own terminal question tool. fx's agent then sends you notifications and asks its questions on your phone, or in the Mac notch while Pushary Isle runs.

npx pushary@latest setup --agents fx

fx has no hooks that other tools can register. So Pushary cannot answer fx's own approval prompts, and it cannot stop an fx tool call. fx's agent asks through Pushary when it decides to, which makes fx a cooperative agent. Supported agents explains which agents Pushary can enforce.

Set up fxCopy Anchor Link

The CLI needs Node.js 20.17+, 22.13+ or 23.5+. If this computer has no Pushary key yet, setup signs you in and saves one.

npx pushary@latest doctor

Set up fx with the Mac appCopy Anchor Link

The Pushary Mac app (Pushary Isle) sets up fx without Node or the CLI. With Set up new agents automatically on, it connects fx when it finds fx's files in ~/.fx. fx is also listed under Agents in Settings. Its switch connects or disconnects fx, and Repair puts back anything that is missing.

The Mac app writes the same three files setup writes. Its pushary server in ~/.fx/mcp.json runs ~/.pushary/bin/pushary-mcp, which starts the Mac app's signed helper. The helper uses the key this Mac signed in with, so no key is written to fx's files. If the Pushary CLI already set up fx, the Mac app keeps the CLI's pushary server as it is.

Questions fx's agent asks through Pushary reach the Mac notch, marked as fx, and your phone. As with setup, restart fx or run /mcp reload after the Mac app connects it.

What setup changes in ~/.fxCopy Anchor Link

Setup installs the Pushary CLI globally, then changes three files:

Setup adds both rules after your own rules. If you already have a rule for mcp_pushary_* or ask_user_question, setup keeps yours and tells you.

No key is written to fx's files. The bridge reads your key from PUSHARY_API_KEY when it is set, and from ~/.pushary/config.json otherwise. When you switch to a new key, fx picks it up from there, so you do not run fx setup again.

Pushary's tools in fxCopy Anchor Link

fx names them:

fx does not load these tools at the start of a turn. Its agent loads each one by exact name with mcp_select_tool, for example {"name": "mcp_pushary_ask_user"}. The block in ~/.fx/AGENTS.md tells it to.

For example, ask fx “Remind me in 30 minutes to check the deploy.” fx loads mcp_pushary_schedule_reminder, saves the reminder on Pushary, and confirms its time. Calendar times need your timezone. One-time reminders support the next 30 days; delivery can be about a minute late. Your connected phone receives it even when fx is closed. Pushary respects stop/mute and current account access. This does not run future fx tasks.

What Pushary cannot do in fxCopy Anchor Link

• fx's approval prompts stay in the terminal. fx cannot hand them to another tool. Only questions fx's agent asks through mcp_pushary_ask_user reach your phone.
• Full-access mode keeps fx's question tool on. fx's full-access mode (yolo, full-access or full access, set in settings, in a workspace, or with FX_PERMISSION_MODE) ignores permission rules. So the ask_user_question rule does nothing there, and the agent is only told to ask through Pushary. Setup and doctor tell you when this applies. Leave full-access mode with /permissions to route questions for certain.
• Workspace rules replace the global ones. An fx workspace with its own permission rules ignores the rules setup added. Setup tells you how many there are. Add "mcp_pushary_*": "allow" and "ask_user_question": "deny" to each one.

When setup leaves fx's files aloneCopy Anchor Link

Setup does not edit ~/.fx/mcp.json or ~/.fx/settings.json when fx itself would reject the file or refuse to edit it. That covers:

• comments, a trailing comma or a byte-order mark
• a repeated key
• servers under a key fx does not read
• a file larger than fx reads (1 MiB for mcp.json, 64 KiB for settings.json)

It also leaves settings.json alone when fx would ignore it, for example because of an unknown permission action or permission mode.

Setup names the file and the reason. Fix the file, then retry only fx:

npx pushary@latest setup --agents fx

If ~/.fx/AGENTS.md is a symlink to a file outside ~/.fx, fx ignores it. Setup writes no instructions there and tells you to replace the link with a file.

Why can fx's questions still stop in the terminal?Copy Anchor Link

Run npx pushary@latest doctor. It checks the pushary server in ~/.fx/mcp.json and that its bridge is installed. It warns when Pushary's tools are not auto-allowed, and when fx's questions can still stop in the terminal. The usual causes are full-access mode, a workspace with its own rules, or your own ask_user_question rule. Doctor names which one.

Remove Pushary from fxCopy Anchor Link

npx pushary@latest disconnect fx

This removes the pushary server, the mcp_pushary_* rule setup added, the ask_user_question rule (only if setup added it and you have not changed it since), and the block in ~/.fx/AGENTS.md. In the Mac app, turning fx off under Agents in Settings removes the same things.

npx pushary@latest clean removes Pushary from every agent, fx included. See the CLI reference.

Next stepsCopy Anchor Link