Live data from Hacker News

Show HN: A browser-based IDE with multi-agent terminal execution (no install)

forge.synvara.ai

1–6 of 6 posts

Show HN: A browser-based IDE with multi-agent terminal execution (no install)

#1
We built a browser-native IDE that runs a real Linux terminal and multi-agent coding tools directly in the browser — no installation or VM setup.

It supports: – A full CloudShell terminal (xterm.js + Node-PTY) – Multi-agent CLI execution (Aider, GPT Engineer, Claude Engineer) – Agents directly modifying files in the repo – UI plan generation + CLI build workflows – Zero local setup, zero dependencies

Demo: https://forge.synvara.ai

We would love technical feedback. Happy to answer questions about: – Browser terminal performance – WebSocket architecture – Agent orchestration – Security model

Thanks in advance — this community’s feedback is extremely valuable to us.

Show HN: A browser-based IDE with multi-agent terminal execution (no install)
forge.synvara.ai

Re: Show HN: A browser-based IDE with multi-agent terminal execution (no install)

#5
post #4

"85–92% faster development " well thanks for the hype, wtf is that based on?

Thanks for calling that out — fair question. The 85–92% number is from internal time-tracked tests comparing:

Before FORGE (baseline):

Spec/plan creation: 3–6 hours

Context switching (browser → IDE → terminal): ~1 hour

Manual copy/paste of generated code: 30–60 minutes

Manual setup + environment config: 30–90 minutes

After FORGE (CloudShell + agents):

Plan generation: 10–30 seconds

No local setup

Agents edit files directly in the repo

Terminal + UI in one interface

So the measurement isn’t “marketing hype” — it’s based on reducing a 6–12 hour workflow to 30–60 minutes on real feature builds.

Happy to share the breakdown or the feature sets we used if that helps.

Re: Show HN: A browser-based IDE with multi-agent terminal execution (no install)

#6
post #4

"85–92% faster development " well thanks for the hype, wtf is that based on?

Thanks for calling that out — fair question. The 85–92% number is from internal time-tracked tests comparing: Before FORGE (baseline): Spec/plan creation: 3–6 hours Context switching (browser → IDE → terminal): ~1 hour Manual copy/paste of generated code: 30–60 minutes Manual setup + environment config: 30–90 minutes After FORGE (CloudShell + agents): Plan generation: 10–30 seconds No local setup Agents edit files di…

thank you