@klorityx · X

One workspace for project management, documentation, test management & CRM. Enterprise features without enterprise pricing.

@qurative · X

vibe coded a landing page for seo and shit, will fix it later focusing on adding features to the dasboard

@Puneeeeeeet · X

We help brands go viral on X with organic video campaigns that people actually want to watch. wanna try for

@akadhanu · X

an ai sprint retrospectives for it teams (

@jimmy_harika · X

TLDR: Notion shipped my exact app that I have using in my daily workflow from last 2 years. Try here: It got a mcp that wires to your claude code and codex. Git integration is almost complete and will ship in coming days

@mkappworks · X

I am building lets connect

@hannah24_app · X

@Umitech_AU · X

AI photo restoration without the AI slop.

@trackowork · X

@evcodebr · X

@DionJerry · X

Promoting We already have over 800 Signups!

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t