Warp finished the run.
Your phone knows.
Pushary sends a push notification when Warp finishes or needs your permission, and lets you approve from your phone in one tap.
Push notifications when Warp's agent wraps a long task, and it can ask you a question you answer from your lock screen. Connect Pushary as an MCP server in Warp and the agent gets send_notification, ask_user, and wait_for_answer as native tools.
One command
{
"mcpServers": {
"pushary": {
"url": "https://pushary.com/api/mcp/mcp",
"headers": { "Authorization": "Bearer ${PUSHARY_API_KEY}" }
}
}
}In Warp, open Settings > Agents > MCP servers, click + Add, and paste this. Warp also auto-spawns it from ~/.warp/.mcp.json (global) or .warp/.mcp.json at a repo root, and the bundled /agent-add-mcp skill can write the file for you. Export PUSHARY_API_KEY in your shell first. See /docs/agents/connect-any-agent.
Featured on Hacker NewsWarp's agent runs. You watch the terminal.
Agent Mode can run migrations, deploys, and multi-step git work on its own. You still sit near the scrollback so you catch the moment it finishes, or the moment it stops to ask you something. Pushary moves that moment to your phone.
Stop watching Warp spin. Start getting notified.
One command. Your phone buzzes when Warp is done.
Warp notification questions
How do I get notified when Warp finishes a task?
Connect Pushary as an MCP server in Warp, then ask the agent to send you a notification when it is done. Warp's agent calls send_notification and the push lands on your phone with a short summary of what finished. It works for local Agent Mode runs and for Warp's cloud agents, since both can use MCP tools.
Does Pushary hard-block Warp before a risky command?
No. This is a cooperative MCP integration. Warp's agent decides when to call ask_user, so you get notifications and questions you answer from your phone, but there is no runtime gate that physically stops a command until you approve. Enforced pre-execution gating (blocking an action until you say yes) needs a host hook and is available on Claude Code, Codex, Gemini CLI, Cursor (shell commands), and Hermes. With Warp you get human-in-the-loop over MCP: the agent asks, you answer, it continues with your decision.
Where does the MCP config live in Warp?
Three places. The GUI at Settings > Agents > MCP servers (paste the JSON into + Add), a global file at ~/.warp/.mcp.json that auto-spawns, and a project-scoped .warp/.mcp.json at a repo root that Warp asks to approve. The bundled /agent-add-mcp skill can write either file for you. All of them use the same mcpServers shape, so you paste the Pushary block once.
Can Warp's agent ask me a question and wait for my answer?
Yes. Pushary gives the agent ask_user and wait_for_answer. The agent posts a yes/no, a multiple choice, or a free-text question, your phone buzzes, and you answer from the lock screen. The agent blocks on wait_for_answer until you respond or it times out, then continues with what you chose. The question stays open for 10 minutes if you need a moment.
Which five tools does Pushary add to Warp?
The same five everywhere: send_notification (fire-and-forget alerts), ask_user (post a question), wait_for_answer (block on the reply), cancel_question (retract a pending question), and list_sessions (see active agent sessions). Pass agentName on each call so multiple Warp sessions show up separately in the dashboard and Fleet Board.
What does it cost?
Paid agent plans start with a 7-day trial at $9.99 per month, which includes 5,000 notifications per month. There is no free tier. You add a card at checkout and can cancel during the trial.