Show HN: NimbleBrain – We killed our agents; users now just describe workflows

Founder here. We killed our agent builder and rebuilt around conversational workflow development.

Last year we built agents coordinating agents. Users asked for it. Demos looked great. Then we watched them not use it.

Nobody knows what an agent actually is, and nobody wants to configure them. What they wanted was simpler: "pull reports from my CRM and send them to me every day at 8am."

We scrapped it and built V3 around a ginle interface: describe what you need, it gets built. The agent (Nira) helps you build - you don't build agents.

Under the hood we're orchestrating across MCP servers - intent classification, dynamic tool loading, state management, scheduling. MCP registry is open source: https://github.com/NimbleBrainInc/mcp-registry

Free tier has all integrations unlocked.

Happy to answer questions about the architecture or why we killed agents.

Show HN: NimbleBrain – We killed our agents; users now just describe workflows
studio.nimblebrain.ai

"Outcomes not rules" is the whole game. On ambiguity: we don't try to solve it upfront. Get it 80% right, let them refine the rest in seconds. When something's wrong, they fix it in natural language, not by going back to eng to change logic or mess with config. The unlock is really iteration without a ticket.

Would love to swap notes on the accounting side. Similar problems, different domain constraints.

What's the best way to connect?