@raster_app · X

@stewartjarod · X

@kitbasedev · X

We just launched, check us out at

u/Zyron_X · Reddit

I built a service for people to use Codex API without 5-hour limit disruption I built a small service for people who use the OpenAI Codex API regularly and want more predictable usage without the 5-hour or weekly limits. It currently provides: Frontier OpenAI models (GPT 5.6 family included) Managed API key Monthly usage budgets depending to plan No 5-hour limit No weekly limit Under the hood, it is built on top of an open-source project and proxies requests to

@gomixo · X

和团队做了一个非常实用的小工具：HTMLShare。 现在用 AI 生成网页、报告、可视化作品越来越方便，但生成后的 HTML 文件，想分享给别人却很麻烦：要么发文件，要么部署网站，要么截图。 HTMLShare 解决的就是这个问题： 👉 欢迎体验，也欢迎反馈建议。

@RulianLLP · X

Mine is - it's a "I vibe coded my app, now what?" production checklist, scanner and and active/dead man monitor to make sure you've covered all the small things that could easily break your production environment. My laravel cloud url is -

@TheSarimQureshi · X

@sivasankar___s · X

I’m currently deep in building Rudra, a visual orchestrator for Next.js designed for full engineering control. ​Zero vendor lock-in—you own the code. ​ Website: App Build with Rudra

chenglong-hn · HN

Data visualizations are the bridge between user and data. But building AI agents that can generate visualizations reliably can be very tricky: - simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability We figured out it is a limitation on the language issue (not just AI capability thing) -- current visualization languages are a bit too low-level for AI agents, requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler. Flint is a visualization intermediate language to address this issue, allow AI agents to solve this last-mile human-agent interaction problem. It provides a simple semantic-type based specification, and contains a layout optimization engine that can produce good-looking charts (filled with derived low-level details) from simple

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

@aunahmedm · X

Samjha — AI meeting notes for 600M+ multilingual professionals. Urdu. Hindi. Punjabi. Bengali. English. US. UK. UAE. South Asia. 91% accuracy on mixed-language meetings. Free beta.