Skip to main content
When an agent or team pauses for human-in-the-loop, the Slack interface renders the pause as an interactive TaskCard in the channel. The user resolves it with buttons and inputs, and the run resumes. All four pause types are supported.

Example

A paused run is persisted to the database and resumed by run_id when the user resolves the TaskCard, so the Slack interface needs a db.
cookbook/05_agent_os/interfaces/slack/hitl_simple.py

Pause Types

Each pause type renders a different TaskCard: Rejections collect a reason where applicable, which is passed back to the agent so it can adjust.

Teams and Workflows

The same TaskCards work for teams and workflows. When a member agent inside a team pauses, the pause propagates to the team run and surfaces in Slack. Workflow step and executor pauses surface the same way.

Next Steps