@Jack_Timonen · X

@collinsjimu404 · X

Ready to ditch gmail and yahoo emails for something professional? Claim up to 15 FREE business email accounts on your own domain ([email protected]). No card needed. Quick setup. Professional, secure, and built to grow your brand. Start now.

@hoofader · X

Get ready for robots age:

@WebWrightAI · X

Aldasams · HN

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

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.

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

ATsimbalistov · HN

Show HN: Tracking GenAI cost and endpoint fragility so app teams don't have to

hubraumhugo · HN

Design slop is the feeling that tells you a website is purely AI-generated. This is an attempt to classify the design patterns behind it. Applying this scoring to recent ShowHN submissions shows that about a third of the submissions show medium to heavy design slop: https://slopcop.adriankrebs.ch/show How the scoring works: - A headless browser loads each site (Playwright) - A small in-page script analyzes the DOM and reads computed styles - Every pattern is a deterministic CSS or DOM check. There are false positives, but my manual QA run verified it’s maybe 5-10%. Is design slop bad? Not really, just uninspired. After all, the web was never about the fanciest design, and before the AI era, everything looked like Bootstrap. However, there is a difference between trying to craft your own design and just shipping with whatever defaults the LLMs output. And the same has been the case pre-LLM when using CSS/HTML templates. I guess people will get back to crafting beautiful design

stfurkan · HN

Show HN: I wrote a 1-bit WebGPU runtime to run a 1.7B LLM in the browser

debamitro · HN

I found that AI tools are generating excellent HTML documents nowadays, yet there's no easy way to show them to others. Yes, there's GitHub pages - but I don't know if it is user-friendly for non-technical people. This app allows you to keep your HTML file in your Google Drive and serve it from there. Feedback is most welcome.

@MalkkiLea · X

Hi, I'm building