Can you route a Claude Code permission prompt to your team lead before it runs?

Not with Claude Code alone. A permission prompt goes to the person running the session, at their terminal or on their own phone. You can force Claude Code to ask before a git push, but you can't choose who answers. To get a lead's yes first, you need a hook that waits for someone else, or a tool that routes the prompt for you.

Everything below was checked against Claude Code's docs on 7 November 2026.

What Claude Code does on its own

A permission prompt asks whoever is at that terminal. Remote Control moves the prompt to the same person's phone. Channels, a research preview, relays it to Telegram, Discord or iMessage, but anyone who can reply there can approve, and the reply carries no name.

Managed settings are the team-wide rules. They can put Bash(git push:*) in the ask list so every push stops for a yes. The yes still comes from the person who ran the agent.

So on a team, the developer whose agent wants to push to the infrastructure repository is the one who approves it. If that's not who you want deciding, Claude Code has no setting for it. Who approved it? checks the same question for Codex, Cursor and Copilot. None of them has one either.

Build it with a hook

Claude Code runs a PermissionRequest hook when a tool call needs a decision. The hook gets the tool name and its input, and it can return a decision of allow or deny. A command hook can run for up to 600 seconds by default before Claude Code cancels it, and you can set a different timeout.

That's enough to build the basic version:

1. Match the steps you care about, such as Bash calls that start with git push.
2. Post the request somewhere the lead will see it: a Slack message with two buttons, or a small web page.
3. Wait for the answer, then return allow or deny.

What you'd still have to build:

• Knowing who answered. A Slack button press is easy to attribute. A link in a chat isn't.
• What happens at the timeout. A hook that times out renders no decision, so Claude Code falls back to its own prompt, and the person at the terminal decides after all.
• A record. Something has to keep which step was asked, who answered and when.
• Every machine. The hook has to be on each teammate's computer, for each agent they run. Codex and Cursor have their own hook formats.

If your team runs only Claude Code and you're happy to maintain the script, this works.

Route it with Pushary for Teams

Pushary for Teams does the routing without a script. Each person connects their own agents. Once a second person joins, each question goes to the person whose agent asked, and an owner or admin can send a chosen step to someone else.

In the dashboard, open Policies, find Approval routing and add a rule:

• Tool pattern: Bash(git push:*) for every git push.
• Repository: infra, or all repositories.
• Route to: a role such as Admins, or one person.

Now when Tom's Claude Code wants to push to infra, Pushary asks the admins on their phones and in the dashboard instead of Tom. Pushes to other repositories still ask Tom. Only they can answer is on by default, so Pushary refuses an answer from anyone else. Whoever answers in the Pushary phone app, Mac app or dashboard is saved by name, next to whose agent asked.

The same rule works for Codex, Cursor, Gemini CLI, OpenCode and Hermes, so a team that runs more than one agent keeps one set of rules and one record.

What a routing rule can't do

• It doesn't lock the terminal. If the lead hasn't answered when the wait ends, the step goes back to Claude Code, and the person who started it can say yes at the prompt. That yes isn't recorded.
• The phone can't approve a risky step. A plain push can be approved from the phone. A force push, rm -r or a deploy can only be denied there; approve those in the dashboard.
• It matches tool approvals only. A question the agent writes itself, such as which of two migrations to keep, goes to the person whose agent asked.
• It needs a second person. Routing starts once someone else joins the workspace.

The Team docs keep these limits current. Team is $59 a month for 5 people, plus $12 a month for each extra person, and new workspaces get 3 days free.