Why every agent needs a Hug
Agents don’t just suggest any more — they act. The more they do, the more some steps need a person.
The shift
AI agents now pay invoices, send emails, change records, ship code and sign documents. Most of the time that’s exactly what you want. But some steps shouldn’t happen without a person: the payment over a limit, the contract change, the production deploy, the message sent in the company’s name.
Those steps need someone to approve, to supply what only they know, to check the work, or simply to own the decision. No amount of orchestration removes them — it just moves them somewhere easy to forget.
What goes wrong without it
Every team that puts agents to work ends up building a way to ask people. It usually looks like this:
- An approval asked in a chat thread, lost by Tuesday.
- Nobody sure who said yes — or whether they were allowed to.
- An agent that restarted and asked twice, or acted before anyone answered.
- A run that died waiting, because people take hours and the code expected seconds.
- Free-text replies the agent has to guess at.
- No trail for the auditor.
The moment an agent stops and asks a person — and waits for the answer.
A Hug is a Human Gate: the point in an agent’s run where it stops, and a person holds the gate open — or keeps it shut.
The right people are asked, wherever they are. They answer on a clear page made for that decision. The agent carries on with the answer. And every step is on the record.
Four steps, every time.
- 1
Your agent asks
At the step that needs a person, it opens a Hug: the question, who should answer, and by when.
invoice-agent · runningApprove invoice 1042$12,400 from Acmeto: financeexpires in 1 dayWaiting for a person… - 2
The right people are asked
By email or in their getHugs inbox — through the channels you set up — with reminders before it expires.
DK[getHugs] Approve invoice 1042Email · Dana KimSRApprove invoice 1042Inbox · Sam Rivera · reminder in 4 h - 3
They answer
On a clear page made for that decision: approve or reject, fill in a form, upload a file, sign off. The first answer, or several — two of three, or one from each team.
Approve invoice 1042Approve $12,400 from Acme?Note (optional)ApproveReject - 4
Your agent carries on
With the answer, who gave it and when. If nobody answers in time, it knows that too. Every step is on the Hug’s record.
Approvedby Dana Kim · 10:42 · via email09:15 asked · finance09:16 delivered · 2 people10:42 answered · Dana Kiminvoice-agent · paying invoice 1042
And around it
Templates
Ready-made decisions — approval, form, acknowledgement — or your own, built for the question.
Channels and roles
Who is asked, and who may answer: people, groups, or a webhook into your own tools.
Workspaces
One per team or project, each with its own people, channels and agents. One inbox across them all.
The record
Every Hug’s history — asked, delivered, viewed, answered, changed — and an audit log you can export.
Agents you can let act.
Control
Agents act only on the decisions you put in their path. What needs a person gets one — every time, not when someone remembers.
Accountability
Who decided, when, and on what — kept with the Hug. The right people answer, because roles say who may.
Speed
People answer from email or one inbox, with reminders before time runs out — instead of agents stalling in a queue nobody watches.
One way to do it
Every team’s agents ask the same way, on the same record — instead of each team building its own approval bot.
Wherever an agent shouldn’t decide alone.
Finance
Payments and invoices over a limit.
“Approve a $12,400 invoice from Acme before it’s paid.”
Legal
Contract changes before signature.
“Sign off the redlines an agent made to an NDA.”
Customer operations
Refunds and account changes.
“Approve a refund over $500, with the order attached.”
Engineering
Deploys and data changes.
“Approve a production deploy, or a migration on live data.”
People operations
Offers and access requests.
“Confirm an offer letter, or grant access to a system.”
Content
Anything published in the company’s name.
“Review a press release or a customer email before it goes out.”
Every decision, on the record.
Roles
Org and workspace roles decide who can ask, who can answer, and who can change anything.
A full history
Every Hug’s life is kept, and the org’s audit log exports to CSV or JSON.
Templates boxed in
A template’s page runs in a sandbox on a separate origin; getHugs never runs uploaded code on its servers.
Hosted, or yours
Use it at gethugs.ai, or run it on your own infrastructure — your database, your email, your storage.
Have you hugged your agent today?
Give it a person to ask — and give your people a clear way to answer.