@Bim_evaporates · X

Check out DMs open

@daogangtang · X

my claw team to help creators/OPC ship their app without the tech team. We help them build, deploy, and auto scale.

Aldasams · HN

Show HN: DocFlow – AI documentation updates for GitHub pull requests

软著 Pro — AI 软著生成器，帮助用户生成软件著作权申请文档

@liquidated0x · X

building an AI coding agent that ships full projects from a prompt — if you're if you're curious

@Dil_Lynn · X

@javimosch · X

@zyvadev · X

✨ AI Vibe Coding 🎨 Website Cloning 💻 Live Code Editor 👀 Live Preview 🎭 Design Presets 🖼️ Auto Logo & Favicon 🗄️ Database 🌐 Free Hosting & Subdomains Native 0G SDKs: ⚡ 0G Compute 💾 0G Storage ⛓️ 0G Chain Everything in one AI Cloud IDE. build with 0G

@milonspace · X

A specification nobody can find is functionally the same as no specification.

@islamtaha · X

@jitendraballa · X

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