Human-in-the-loop for CrewAI
Human-in-the-loop for CrewAI agents, on a phone.
Swap CrewAI's console human_input for a phone approval that blocks fail-closed until a real person answers.
The integration
Add it to your CrewAI agent
Run pip install pushary-crewai and give your agent make_ask_human_tool(user_id). It is a ready-made CrewAI tool that replaces the console human_input prompt. When the agent reaches an approval, it blocks fail-closed until a real person answers on their phone, then hands the agent the decision. Connect each end-user's phone once with a one-tap link keyed to your own id. The id is bound when you build the tool, so a prompt-injected agent can never ask the wrong person.
from crewai import Agent, Task, Crew
from pushary_crewai import connect, make_ask_human_tool
# Connect the user's phone once, keyed to your own id.
connect("user_123")
agent = Agent(
role="Ops",
goal="Ship safely",
backstory="Careful operator.",
tools=[make_ask_human_tool("user_123")], # blocks on a real person, fail-closed
)Why you need it
CrewAI pauses the agent. Pushary reaches the human.
CrewAI's built-in human_input=True only prompts on stdin, so nothing happens unless someone is watching the terminal. pushary-crewai moves that approval to the person's phone. make_ask_human_tool gives the agent a tool that blocks fail-closed until they answer, delivers to the device they carry, and logs every answer. Each of your end-users approves their own decision.
How it works
From ask to resume
Connect the phone once, then ask a human from the tool or step that guards the action. The waiting, the delivery, and the record are handled for you.
- 01
Install the adapter
Run pip install pushary-crewai and set your Pushary API key in the environment.
- 02
Connect the phone
Call connect(external_id) once per end-user. It returns a link the person taps once to turn on approvals, with no account and no app to install.
- 03
Give the agent the tool
Pass make_ask_human_tool(user_id) in the agent's tools list and drop human_input=True. The user id is bound to the tool, so the model cannot change who gets asked.
- 04
It stays fail-closed
The tool treats anything short of an explicit approval as a stop. A decline, a timeout, or no answer all mean the agent does not act.
A decision is a yes or no confirm, a multiple-choice select, or a free-text input. Every one is stored with its outcome and kept in the audit log.
The Partner plan
Your agent asks your users, not just you
Ship the agent to real users and let each of them approve their own decisions from their phone, under your brand.
Your users never see a Pushary login or bill.
Your users answer on their own phones
The externalId is your own id for the end-user. Connect their phone once with a keyless one-tap link, and every approval lands with the right person. No account, no app, no key on their side.
Durable, fail-closed waits
The agent stays open on a durable wait backed by a decisions ledger. If nobody answers in the window you set, the decision comes back denied, so a timeout or a restart never turns into an unapproved action.
Phone-first delivery
Pushary reaches the person on the device they carry: native app push first, then PWA push notifications, then Slack if you route it there. You do not build a delivery pipeline.
Signed webhooks and an audit trail
Every decision is written to a durable ledger you can query and export, and resolved decisions post a signed webhook to your callback URL. You have the record of who approved what and when.
FAQ
Questions, answered
Let your CrewAI agent ask a human.
Connect a user with one tap, ask a human with one call, and act on a fail-closed decision. Every decision is saved to a durable ledger you can audit.
Partner plan, $99 a month. Your users never see a Pushary login or bill.