people are now arguing about whether an agent should be allowed to approve the refund. a year ago the fight was over letting it answer the ticket at all, and nobody brings that one up anymore
ZooWork retweeted
Building an agent is easy now. Handing it to a client is the hard part.
@ZooWorkAI lets you build one by chat (or with Codex or Claude and their SDK) and deliver it as a link, an API, or a Slack or WhatsApp bot.
Your expertise, deployed in minutes: zoowork.ai/?utm_source=x&utm…
🤖 Made with AI
3.8x on cost for five points of intelligence, and on everyday work those five points barely show. we route the boring stuff to the cheaper models, and that routing is where most of our model savings come from
10 years sounds about right from where we sit. getting an agent to run inside someone's actual POS system for months is where most of them stall out.
In retail, your AI agent can look up a customer’s order, but should it also be able to issue a refund?
Here’s how we decide what an agent can see and do:
Data access and permissions belong in the solution design, and the client’s own systems should enforce them.
Human approval is one gate. It does not replace backend authorization.
what's even left for the gateway once routing moves into the harness? just the cost and latency stuff?
router lives in the harness, not a gateway, bc the harness knows the task
blog: langchain.com/blog/how-to-bu…
xitter.cf/neil_xbt/status/210997…
A stylist that knows your closet. A bot that reads every filing before the market opens. How much can you ship between breakfast and 6 PM?
Nov 7 · NYC · with @AITinkerers · $100 in credits per builder · 100 spots
Apply 👇
nyc.aitinkerers.org/p/fashio…
Before we build an AI agent, we agree with the client what “done” looks like.
Here’s why, and what we agree on before any code gets written:
A demo proves the happy path. Acceptance criteria determine whether the system should scale, keep piloting or stop.







