Vibe Coder Layout

A prompt-first layout: one full-size composer, chips for project, agent, and model, and Preview, Changes, and Code side by side.

Most layouts arrange the tools around your code. Vibe Coder arranges them around one question: what do you want to build?

Pick Vibe Coder in the layout picker. The workspace rearranges into a composer-first surface — the terminal is still real and still running underneath, it just stops being the first thing you look at.

Vibe Home

The home screen is a full-size composer, not a stripped-down chat box. Everything you have in Agent Input works here:

  • @ mentions for files, terminals, agents, and sibling projects
  • Skills and slash commands
  • Prompt templates
  • Drag-and-drop images

Under the prompt sits a row of chips that decide how the run behaves:

  • Project — which repo this prompt runs against
  • Agent — Claude Code, Codex, Kimi, Pi, or anything else you have installed
  • Model — the model chip for that agent
  • Plan or build — whether the agent drafts a plan first or starts changing files
  • How much it asks — the permission posture for the run

Open the app with no project loaded and Vibe Home still greets you, so a new idea does not have to start with picking a folder.

Submit, and it becomes a conversation

Sending a prompt turns Vibe Home into a conversation view. The agent underneath is an ordinary terminal — one click gets you the raw TUI whenever you want it, and everything you know about session persistence and resume still applies.

Recent conversations are listed on Home, so picking up yesterday's thread is one click rather than a hunt through tabs.

Preview, Changes, and Code

The right panel keeps three views side by side:

  • Preview — your app running, via the built-in browser
  • Changes — the diff the agent is producing, as it produces it
  • Code — the files themselves

The point is that you watch a build happen instead of hunting for the result after the fact.

When to use it

Vibe Coder suits work that starts from a description rather than from a file: a new feature, a spike, a prototype, or driving an agent on a repo you do not know well yet. For a day of hand-editing, Default or Classic will serve you better.

Layouts are per project, so one project can live in Vibe Coder while another stays in Default.

Related