@shengkun_ye .01 cents per tool call is expensive in any real production system unless you’re only connecting to gated data providers like this…@shengkun_ye love what you’re building, and maybe I’m missing something that I’d be happy to learn and admit I’m wrong about. Let’s talk
In this @HealthITNews article, Girish Navani discusses how at #HIMSS26, eCW will be focusing on autonomous artificial intelligence & will launch the AI API Workbench, enabling customers to build autonomous AI agents for their organizations' workflows. https://t.co/MLYuH2Yw6D
@_avichawla Proud early customer and investor in Composio.
The interesting conversation: how does this evolve when agent tools/skills are tied to enterprise systems (where the organization owns the learning data), versus being used in RL to improve the skill for everyone
Everyone's losing their minds over OpenAI's Agent Builder.
I spent the last 24 hours testing it and analyzing community reactions.
Here's what nobody's saying about the $4B "democratization" play that's actually just vendor lock-in with a canvas:
The hype: "Agent Builder democratizes AI! No-code revolution! Zapier killer!"
The reality: It's a drag-and-drop builder for developers that's locked to GPT-only models.
That's not democratization. That's an ecosystem play.
I tested it against n8n, Make, and Flowise.
Complexity level: Same (if not slightly higher)
Integration flexibility: Worse (thin node sets)
Model options: One (GPT only)
Migration benefit: Zero
The GPT-only lock is the real killer.
I use Claude for complex analysis. Gemini for specific tasks. GPT for... honestly, the braindead simple stuff.
Being forced into one model is like telling a carpenter they can only use hammers.
Community reactions are split exactly how you'd expect:
Positive takes:
→ "Built a buyer agent in hours, 70% iteration reduction!" (Ramp)
→ "Game-changer for prototyping" (@piotrmacai)
→ "Seamless OpenAI integration" (obviously)
Reality checks:
→ "UI too complicated, features basic" (@wyndomb)
→ "Not autonomous, just rigid scripts" (@Vivek_5151)
→ "No migration incentive" (me + many others)
The pattern I'm seeing: Great for prototyping IF you're already deep in OpenAI's ecosystem.
Not great for: Production systems, multi-model workflows, anyone using n8n/Make successfully.
Here's what the docs won't tell you:
✓ Fast prototyping (true)
✓ Good for demos (true)
✓ Enterprise features (true)
✗ Vendor lock-in risk (ignored)
✗ Limited node library vs competitors (ignored)
✗ Still requires technical knowledge (ignored)
✗ Not actually "no-code" for non-technical users (ignored)
The "democratization" claim falls apart under scrutiny.
Community feedback shows it's "too technical for teams" and "missing features for production-scale."
It's low-code for developers, not no-code for everyone.
Real talk: If your workflows already work in n8n or Make, save yourself the migration headache.
The math doesn't add up:
→ Rebuild all integrations
→ Learn new platform
→ Lock into single model
→ Hope features catch up
For what benefit? "OpenAI native" that you can already get via API calls?
Where Agent Builder actually makes sense:
1. You're already 100% in OpenAI ecosystem
2. You need fast prototyping for demos
3. You're building customer service bots (their sweet spot)
4. You don't care about model flexibility
Everyone else? This is a solution looking for a problem.
The controversial truth: Agent Builder validates visual agent building as a category, but it's not the revolution they're selling.
It's an incremental improvement for a narrow use case wrapped in "democratization" marketing.
The winners: OpenAI (ecosystem lock-in), enterprises already using their stack
The losers: n8n/Make users expecting a reason to switch, anyone needing multi-model flexibility
My take: Good prototyping tool. Not worth migrating for. Overhyped by 3-5x.
The real opportunity isn't in the tool itself.
It's in the $400M-$4B consulting market that opens up when everyone realizes prototyping ≠ production deployment.
Stay where you are. Let others debug the hype cycle.
Your existing automations work. Your team knows the platform. Your models are flexible.
"OpenAI native" isn't a feature when you can call their API from anywhere.
Agree? Disagree? Drop your take below.
I'm curious if anyone found a compelling reason to migrate that I'm missing.
@zaidmukaddam Hiring at https://t.co/09LKxBMKiU and you get to work directly with our brilliant team on using LLMs and Agents to solve the biggest problems at leading US universities and enterprises. DM’s open!
Inspiring to see a tool I had never used 4 years ago become not only a part of my pinned apps almost immediately, but also becoming a household name so soon after.
Congrats to the @figma team on their public listing today! Glad I coincidentally walked down Wall Street today.
@MarcelFromMimic You should link the Rolai website or atleast tag @MarkKnd to give him credit if you’re going to try and copy his work on our branding and site
@lovable@johnrush@tibo_maker@FarzaTV@NickADobos Can I be a judge?? Working with 10s of thousands of university faculty and students and they’d love if we made some content about this. Would add visibility too