omeraplak
Joined 7 years ago
Karma
38
Submissions
71
Member since
Jul 18
Recent submissions
Comment · 6 months ago
Thank you so much!
Comment · 1 year ago
Thanks so much! Yes, we've received this feature request from many of our users. No-code workflows are already on our backlog
Comment · 1 year ago
Thank you!
Comment · 1 year ago
Hi HN,
I'm one of the founders of VoltAgent. Over the past months, we've been building it with a simple focus: AI development lacks real-time observability.
When you work with agents, it's often a black box. You write some code, run it, and just hope it behaves. If something goes wrong, debugging feels painful. Tools like n8n showed us how powerful it is to see a workflow step-by-step, but as soon as we needed customization and deeper control, we hit the limits of no-code tools.
VoltAgent is our attempt to bring that visibility to a real framework. It's an open-source, TypeScript framework for building and orchestrating AI agents with observability built in from the start.
What VoltAgent offers - TypeScript-native building blocks -> tools, memory, multi-agent orchestration, and seamless ai-sdk integration. - Real-time observability -> OpenTelemetry-based tracing and a visual console to inspect how agents think step by step.
Repo: https://github.com/VoltAgent/voltagent Docs: https://voltagent.dev/docs/
We’d love your thoughts, feedback, or questions.
Comment · 1 year ago
Thanks!! We spent a lot of time on the details. Glad you liked it
Comment · 1 year ago
Wow, thank you for this thoughtful message. You really got what we’re trying to build. We’re pushing hard to bring shadcn-level simplicity to agents. Your feedback means a lot!
Comment · 1 year ago
Thank you! Really appreciate it. Let us know if you try it out.
Comment · 3 years ago
The dilemma of choosing the right tool for a long-term project is understandable. We are running an open source React framework called refine for building Enterprise B2B apps like admin panels, internal tools and dashboard.
It's designed to be ensuring that projects remain maintainable even as time goes by. With its headless architecture, it can be used with custom styles or any UI library and data services. Maybe it helps you somehow
You can check the examples with source code: https://refine.dev/docs/examples/
Repository: https://github.com/refinedev/refine
Comment · 3 years ago
Just for clarity: the author of this comment is not from our team. But if you ask for my opinion, I enjoyed reading the article. We always pursue ideas that will take 'refine' to the next level, and this piece was helpful to us.
Comment · 3 years ago
If I understand correctly, using 'swizzle' to customize the data provider is not a hack for refine, but an expected behavior. But I'm curious about the conversation; could you possibly share the link?
Comment · 3 years ago
Oops, we haven't heard of this issue before. We're looking into it. Thank you