Giselle
Build and run AI workflows. Open source.
974 followers
Build and run AI workflows. Open source.
974 followers
Built to design and run AI workflows that actually complete. Zero infra setup—just build and run. Handle complex, long-running tasks with a visual node editor and real-time tracking. Combine models from multiple providers in one canvas.
You’re basically packaging “LLM orchestration as a legible object” turning invisible glue code into something humans can reason about.
Knife-edge question: what’s your plan for reproducibility (snapshots of models/inputs/connectors) so workflows don’t drift into “works on my Tuesday”?
I love this because I hate myself. (Kidding. Mostly.)
Giselle
@teodor_hascau Exactly, Giselle's core value is making LLM orchestration something humans can easily experiment with and iterate on. Sometimes you want AI to suggest the optimal approach, but ultimately, if humans can't understand it, it's hard to make good decisions. Our plan is to first make it easy to translate human ideas into flows, then layer in AI-powered suggestions.
As for reproducibility, it's a tough problem. We have internal state management, but we haven't yet shipped robust snapshotting or version control features for users. It's a pain point everyone's grappling with, and definitely on our roadmap.
Giselle
@teodor_hascau san, Thanks for the comment! You nailed it exactly.
On reproducibility, we're planning features like "app version history," "app templates," and "template sharing + community." As for reproducibility of flow execution results—since LLM outputs depend on the model itself, we're not planning to intervene there for now. That said, having an environment where workflows run reliably day after day is something I need myself as a daily Giselle user, so we're definitely working on it.
Giselle
@teodor_hascau Great question — and yes, that’s absolutely the knife-edge.
Today, Giselle already persists full step-level inputs and outputs for every execution (including intermediate states). The UI for inspecting, diffing, and selectively re-running those steps isn’t fully exposed yet, but it’s very much on the roadmap.
We’re pretty realistic about this part: bit-perfect reproducibility with LLMs is a mirage. Models change, providers evolve, and some entropy is inherent. Rather than pretending we can freeze time, our goal is to make every run legible — so you can see exactly what happened, why it happened, and what changed.
In other words, we may not guarantee “works on every Tuesday,” but we can guarantee you’ll know why it worked last Tuesday and what drifted by Thursday — and give you the tools to course-correct quickly.
Thanks for calling this out. I’ve personally been burned by this class of failure more times than I’d like to admit, and it’s one of the core problems we want to solve for builders trying to tame very energetic LLMs.
NerdyNotes
Congrats on the launch, the focus on clarity and flexibility in a workflow really stands out.
Giselle
@musfk san! Thank you so much!!
While we only have simple features for now, we worked really hard to deliver an easy-to-use UX! I really appreciate your comment.
Giselle
@musfk Thank you!
We really appreciate the kind words. We're glad the focus on clarity and flexibility came through.
Giselle
@musfk Thanks a lot! That’s exactly what we were aiming for — a workflow builder that stays clear and opinionated, but still flexible enough to handle real-world complexity.
Giselle
@musfk Thank you! Really glad that came through. NerdyNotes looks great too — love what you're building!
Congratulations on the launch 👏
I agree with you. A lot of workflow tools look powerful until you try to debug something at 2am.
What was the hardest part to simplify without removing flexibility? That balance is tough.
GraphBit
This resonates. Visual workflows only become useful once debuggability and execution transparency are first-class, not afterthoughts. Open source plus real-time visibility is a strong combination, especially for long-running, multi-step flows where trust is built by being able to see what ran, why it ran, and where it failed. Curious to see how this evolves as teams push it beyond experimentation into shared production workflows.
Giselle
@musa_molla Thanks for this. Debuggability and execution transparency being first-class is something we deeply care about too. Beyond open source and real-time visibility, we want to strengthen features like debugging and eval. But first, we're focused on making the experience of experimenting and iterating with AI as smooth as possible. As teams move toward production use, transparency and debugging become even more critical. We're also exploring the ability to expose workflows as APIs, and through that process, we aim to improve stability and transparency further.
Giselle
@musa_molla san, Thank you! Transparency was our top priority when building Giselle, so I'm glad that resonated with you. We're continuing to improve it for production use. Would love to hear your feedback if you give it a try!
Giselle
@musa_molla Thanks for the thoughtful take — you’re hitting the core of it. Visual workflows only really become “production-ready” when you can clearly see what ran, why it ran, and exactly where it failed so you can iterate with confidence.
Giselle already keeps the underlying run data, but we don’t yet have a user-facing UI that makes debugging and execution transparency truly first-class. That’s a priority for us next: better run history, step-by-step inspection, and clearer failure points so teams can move from experimentation to shared workflows with trust.
If there are specific debugging views you’ve found most useful (e.g., per-node logs, inputs/outputs diffs, retries), I’d love to hear what you’d want to see.
Giselle
@dubd59 Thank you so much — we’re really honored!
If you don’t mind, I’d love to hear what stood out to you most. Was it the zero-infra setup, the visual node editor, real-time tracking, or the ability to mix models from multiple providers in one workflow?
Giselle
@dubd59 Thank you so much for your kind comment. It really means a lot to us.
We’re truly happy to hear that!
Giselle
@dubd59 san
Thanks so much for the kind words — it really means a lot! We’re going to keep shipping updates and improving Giselle, so stay tuned. If you get a chance to try it, I’d love to hear what you build and any feedback you have.
Giselle
@dubd59 This means a lot — thank you! 🙏
Giselle
@dubd59 san! Wow, thank you! 🎉 #2 product of the day is incredible – we're so grateful for the amazing support from the community!
Giselle
@nico Thanks so much for checking it out, Nico! Really appreciate it 🙌
Curious — what part feels the coolest to you so far? For most people it’s either the visual node editor + real-time tracking, or the ability to mix models from different providers in one canvas.
Giselle
@nico Thank you so much for the kind words!
We’re really happy to hear your positive feedback, and we’ll keep working on improving the product.
Giselle
@nico san
Thanks so much—really appreciate it!
I’m super happy you think it’s cool. If you get a chance, I’d love to hear what stood out to you most✨
Giselle
@nico Thanks so much — really appreciate it! 🙌
Giselle
@nico san, Thank you so much! 🙌 We'd love to hear your thoughts if you get a chance to try Giselle!
@codenote I am actually thinking about integrating this with a fork of @Sokosumi and the Masumi protocol
Giselle
@nico Oh, that sounds great! Please let me know once you've completed the integration!!
FUNCTION12
I loved the neon sign-like effect, it made the content very easy to recognize! Is it possible to change the color of the cards inside as well? Looking forward to the launch!
Giselle
@shawn_park_f12 Thank you so much for your kind words! We've finally launched! 🎉 Please give it a try and let us know what you think!
Giselle
@shawn_park_f12 Thanks so much! I'm really glad you picked up on that - it's a detail I really worked on. Hoping to add customization features like other editors down the line. Will keep pushing forward with updates!
Giselle
@shawn_park_f12 Thanks for the early comment — we're live now! FUNCTION12 looks awesome too. Hope you get a chance to try it out!