Forge introduces slider-based landing page editing with panel toggle

• creativedash's demo says the entire Forge landing page was designed and choreographed with sliders instead of code, with ⌘. opening the control panel and ⌘K triggering auto-scroll.
• According to the official Forge page, the product mounts a Vite or Next project as a zoomable canvas where routes render side by side, including states like home and 404, with no extra build step.
• The same Forge page says it can call installed agents including Codex, Claude Code, and OpenCode, scoped to the file currently in view on the canvas.
• creativedash's reply adds the obvious catch: the slider workflow works much better when you already know where your controls live.

You can try the landing page, watch creativedash's demo, and browse Forge's own claims about route frames and agent handoff. The weirdly compelling part is that the public demo is not just selling a visual builder, it is showing a marketing page tuned in public with the same UI primitives the product wants to make normal.

Forge's clearest reveal is not a feature list. It is the claim that a polished landing page can be tuned like motion software, by dragging controls until spacing, timing, and layout feel right.

That makes Forge read less like a static site editor and more like a control surface for frontend behavior. The official Forge page frames the product as a zoomable canvas where pages and states sit beside each other, which matches the tweet's focus on choreography rather than one-page assembly.

The official Forge page says a Vite or Next project drops into one infinite canvas, with each route rendered as its own frame and no new config or build step.

The useful part for designers is the side-by-side setup: home, empty state, and 404 are meant to stay visible in the same workspace instead of hiding behind routes and tabs. That is a small workflow shift, but it changes the job from editing isolated screens to shaping the whole site map as one surface.

Forge is not pretending the canvas replaces code. Its official copy says edits still land on disk as normal source changes, and the app can call whichever local agent you already have installed, including Codex, Claude Code, and OpenCode, scoped to the file you are looking at.

That pairing, visual controls for fast iteration and agent-scoped file edits underneath, is the real product idea here. The canvas handles feel, while the repo stays a repo.

Forge says it is in beta with a small group of designers and engineers, with new invites going out weekly through the waitlist. The tweet adds two concrete controls for the public demo: ⌘. toggles sliders and ⌘K auto-scrolls the page.

Those details make the launch page double as a product sample. The landing page is not only advertising Forge, it is functioning as a live proof that the slider-first editing model can ship something polished enough to front the beta itself.