crewai-agentgate

Gate any CrewAI tool behind human approval in Slack or Microsoft Teams — one wrapper, no rewrite.

pip install crewai-agentgate

Usage

from agentgate import AgentGate
from crewai_agentgate import ApprovalRequiredTool

gate = AgentGate(api_key="ag_your_key")

gated_publish = ApprovalRequiredTool(
    wrapped_tool=publish_content_tool,   # any existing CrewAI BaseTool
    gate=gate,
    risk_tier="high",
    timeout_minutes=15,
)

Give gated_publish to an Agent anywhere publish_content_tool would have gone — same name, same input schema, same output type. The only difference: before it actually runs, it posts a request to Slack/Teams and blocks until a human clicks Approve or Reject.

publisher = Agent(
    role="Content Publisher",
    goal="Publish approved content to the appropriate platforms",
    tools=[gated_publish],
)

If rejected, the tool call returns the rejection reason as its output instead of raising — so the agent sees "the action was rejected because X" and can react to it, rather than crashing the crew.

Why wrap instead of rewrite

Most human-in-the-loop patterns require restructuring how you build the tool. This doesn't — it wraps a BaseTool you already have. Your tool's logic, its args schema, and its name are all unchanged; approval is a layer around it, not a rewrite of it.

Parameters

Requires

An AgentGate server — self-hosted or hosted at useagentgate.com — connected to Slack and/or Teams. See the AgentGate docs.

License

MIT