Hatchet vs Pushary

Hatchet

A durable task waits for a keyed event without holding a worker slot, and resumes from its event log after a restart, in Python, TypeScript, Go or Ruby. Hatchet supplies only the pause and resume. It has no approver inbox, notification channel or record of who answered, and its MCP server cannot push the event.

Pushary

Six small tools with a detailed skill that says when to ask, when to notify and when to stay quiet. No free plan, and the 3-day trial takes a card up front.

Hatchet

1. Put the approval wait in a durable task, and keep API calls, database reads and random values in child tasks, because the code between checkpoints is replayed
2. Add a sleep condition in the same or group as the event condition to set a deadline, and treat the sleep firing first as a timeout
3. Give the event a scope and the wait a lookback window when the answer can arrive before the wait starts. Both must be set together
4. Filter with a CEL expression such as input.user_id == '1234' so one approval key cannot resume another request's task
5. Push the answer with the SDK's event push or POST /api/v1/tenants/{tenant}/events. The MCP server has no tool for it
6. Grant the MCP server one profile with hatchet mcp auth --grant <profile>. It refuses profiles that were not granted

Pushary

1. Read answered, status and handoffAction on every result, and never treat a timeout as approval
2. Expect ask_user to return at once with answered: false when the user's mode is notify-only or terminal-only
3. Poll wait_for_answer once (it waits at most 55 seconds), then follow the handoff instead of looping
4. Cancel a live question with cancel_question before asking the same thing in chat
5. Group open decisions into one select question, since each push interrupts the user