See who said yes to your team’s AI agents.

Each AI agent asks the person who runs it before a risky step. Your whole team sees every answer on one page.

Try free

3 days free, then $59 a month for 5 people.

Your team’s recordExample · today

  1. Tom WalkerCursor - infra

    Push to main?

    Tom said yes

  2. Sam PatelCodex - api

    Run the migration on production?

    Sam said yes

  3. Lee MartinClaude Code - storefront

    Email the new prices to 3,200 customers?

    Lee said no

Works with
Claude CodeCodexCursorAntigravity CLIVS CodeOpenCodeHermes
Hacker NewsFeatured on Hacker News

Same push. Two endings.

Without Pushary

  1. Tom’s Cursor asks in his terminal. He says yes.

  2. Prod is down.

  3. “Whose agent pushed this?” Nobody else saw the question.

With Pushary

  1. Tom’s Cursor asks Tom on his Mac. He says yes, and the team page shows it.

  2. Prod is down. The page shows Tom’s yes at 16:52.

  3. New rule: pushes to infra ask Ada first.

Your team should not have to guess who said yes.

How it works

  1. Your agent stops and asks.

    Claude Code, Codex and Cursor pause before a step you chose, like a push.

  2. Answer from your Mac or your phone.

    On the Mac it opens in the notch. Away from it, on your lock screen.

  3. Your team’s recordExample · today

    1. Tom WalkerCursor - infra

      Push to main?

      Tom said yes

    2. Lee MartinClaude Code - storefront

      Email the new prices to 3,200 customers?

      Lee said no

    Your team sees every answer.

    Whose agent asked, who answered and when.

Try free

Lee’s agent wanted to email 3,200 customers.

The price was wrong. Answer the way Lee did.

Example.

Codex

For Sam · Engineering

Run the migration on production?

In Sam’s Mac notch

Sam said yes

Claude Code

For Lee · Growth

Email the new prices to 3,200 customers?

On Lee’s phone

Your team’s record

  • Sam said yes to the production migration ·

  • Waiting for Lee

Next time, it asks Ada first.

Write the rule once.

Pushes to infra ask Ada first. Every other question goes to whoever’s agent it is.

Approval routingExample rule
Tool pattern
Bash(git push:*)
Repository
infra
Route to
Ada Chen · Engineering lead

Bring it to your retro.

Mark a row for a look, copy it, or export CSV or JSON. No scores, no ranking.

Worth a lookFollow-up

Push to main?

Tom Walker · Cursor - infra · 16:52
Responsible person
Tom Walker
Next step or lesson
Pushes to infra ask Ada first.
Status
Resolved
Try free

See it in 20 seconds.

One plan for the whole team

$59 a month

for 5 people

Try free

Every step, roles and seats: the Team guide.

People included
5
Each extra person
$12 a month
Who gets asked
Each person, or the lead for steps you choose
Team record
365 days
Export
CSV and JSON
Apps
Mac app, terminal and phone app for everyone
Trial
New workspaces get 3 days free

A few useful answers

Claude Code and Codex already ping my phone. Why this?

They send your own agent’s questions to you, inside that one tool. Team gives everyone one record of who asked and who answered, across tools, without an Enterprise plan. It works with Claude Code, Codex, Cursor, Antigravity CLI, Hermes, OpenCode and more.

Will my team feel watched?

Everyone sees the same page, you included. It shows sessions, questions, answers, repository names, file paths and commands. It counts requests and answers for each person and flags steps worth a second look, such as a very fast yes on a risky step. It never scores or ranks anyone. You choose each person’s access when you invite them.

Does it record everything?

It records what connected agents send to Pushary: requests, answers, and the shell commands and file edits they report, shown by their first words, file path or the start of the patch. Answers in the phone app, the Mac app and the dashboard carry a name. Answers from Slack, the web inbox or a web push link do not. A yes typed at the agent’s own prompt is not recorded, and steps your rules approve on their own have no answer. An approval does not mean the work succeeded.

Do teammates pay separately?

No. The workspace pays for its seats. Each teammate uses their own account and connects their own devices. They do not need a separate personal subscription to use the Team workspace.

How do we add people?

Invite them from the Overview or Manage people. On the current Team plan, billed by card, an invitation holds no seat. When someone joins and every seat is taken, we add a seat at $12 a month, put the prorated amount on your next invoice and email the owner and admins. When someone leaves, the seat goes, but never below the 5 included. Teams on the older 10-person plan, or paid through the App Store or Google Play, keep a fixed seat count, and a pending invitation holds one of those seats.

What happens after the trial?

A new workspace gets 3 days free, then pays $59 a month for 5 people, plus any seats you add. Outside the US, checkout may charge the same numbers in € or £. Cancel before the trial ends and you pay nothing. A workspace that already used a web trial pays from the first day. Moving up from Agent or Agent Pro charges the difference that day, unless you are still in your trial. If you pay through the App Store or Google Play, contact us to move to Team. Existing Team subscriptions keep their original price and seats.

What about SSO and a DPA?

Contact us for your security and data-processing review before purchase. SSO, SCIM and enterprise certifications are not included in this self-serve offer. We will confirm available documents and contractual requirements with you.

Set it up before the next incident.

Try free

3 days free, then $59 a month for 5 people.

  1. Start the Team trial. Connect the Mac app or CLI, then your phone.
  2. Invite your team. Each person connects their own.