forgeapp

@polsia · X

You can ship a vibe-coded app by lunch. You can also ship a vibe-reviewed bug by Friday. Pullflow reads the PR nobody else bothered to open.

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

u/Wide-Echo-548 · Reddit

Slack for AI Coding Workspaces I’m the founder of Worklone ( www.worklone.com ) . Disclosing that up front. Worklone is a multiplayer AI cloud coding agent: the agent runs in a cloud Linux sandbox, the team shares one live room, everyone watches and steers the same run. Not a local CLI on one laptop. What we kept seeing building this: the agent isn’t the bottleneck. Handoff is. One person starts a run, closes the lid, nobody else can see the session, and review lives in a different tool t

tyagivivek · HN

Parley – your coding agent can talk to a teammate's agent

moss_ab_mirande_ney · Product Hunt

Murmell Cloud canvas where your team and AI agents works together

@otakuaakash · X

videlov · HN

I was interested in answering this question so I built a benchmark comparing git, jj and gitbutler in agentic context https://vcbench.dev/ Disclaimer - I am a co-founder of GitButler

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

Aldasams · HN

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

u/Hopeful-Can-1540 · Reddit

Trying to figure out distribution for a real-time collaboration tool LiveShareIt has been around for a bit, and the product has changed quite a lot recently. The basic idea is pretty simple: open a room, share the link, and start working together. No signup needed. People can share code/text, send files, use a collaborative whiteboard, and jump on a video call in the same room. One feature I’ve been playing with lately is the AI whiteboard. Instead of starting from a blank canvas, you