@ohdearkk · X

Tovo - AI 会议/面试助手 — 在会议中，Tovo 是一款注重隐私的 AI 助手，完全在您的设备上运行，为会议和对话提供实时转录和智能协助，无需向外部服务器发送任何数据。

@ContinuumCode · 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

@DLVaultApp · X

Most families aren't prepared for someone's digital life. Passwords. Documents. Recovery information. Important instructions. Digital Legacy Vault helps you organize everything securely and decide exactly who can access it when it's needed. #buildinpublic

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

Canvave — 简单图形设计和动画制作平台。无须专业技能也能做出任意尺寸的精美设计；最高支持图片 3x 或动画 240 FPS 导出；内置基于 Flux 的 AI 文生图、图生图；适合电商卖家、广告设计、社媒运营、独立开发等有设计需求的群体

@JamesAuble · X

Building something cool? List it on DealMyApp and get your project in front of thousands of founders, makers, and potential buyers. 🚀

fran-mora · HN

I gave 5 AI coding agents one prompt: grow a banana plant through its whole life in three.js: sprout, leaves, flower, fruit, rot, then pups that restart the loop. It's deceptively simple and yet very hard to get right from procedural code: you have to write working three.js and understand how the plant is actually built; how it hangs, ages and decays. Get the biology wrong and the code renders something weird. These are agents, not bare models (Claude Code and Codex for now). They can use tools, including playwright to check their work and improve it.