Studio
Studio is where you and LiTT build together. Three areas — the LiTT panel, the workspace, and the tools panel — stay in sync around one active project.
One active project
Everything in Studio follows the active project — chat, preview, and terminal all operate on the same project. Switch projects and all three areas switch with it.Chat is the primary control surface. You describe outcomes in plain language; LiTT responds with plans, file edits, terminal commands, and verification. Conversations are kept per project, so you can pick up where you left off.
The composer has a selector with two sections — agents and models:
LiTT (your main operator), Coder (engineering and implementation), Writer (content and copy), Researcher (research and synthesis), Marketer (marketing and growth), Analyst (data and analytics), Nova (business partner), Forge (technical partner), Echo (creative partner).If a model or provider fails mid-conversation, Studio tells you what happened instead of silently degrading — see Troubleshooting.
Before building, LiTT lays out the steps it intends to take. The Plan tab shows that breakdown — what will be created, changed, and verified. Review it, ask for changes, or let LiTT proceed. Big missions go smoother when the plan is right, so this is the cheapest place to steer.
Canvas is the visual working surface — a place to arrange ideas, mock up layouts, and explore directions visually before they become files. Use it when you're thinking in pictures rather than code.
The Code tab shows your project's actual files. Every edit LiTT makes lands here as a real file change you can read, and you can switch between a file tree, an editor view, and an app preview of the running project. If you know how to code, this is where you audit exactly what the agent did.
Preview runs the active project so you can see and interact with it. Studio mounts exactly one preview per active project — it starts automatically, and if it ever fails to start the preview panel offers a retry. Preview is your iteration sandbox: it is not the same as a production deployment. Full details in Preview & Deployment.
Media collects what LiTT generates for the project: images, video, music, and audio artifacts. Anything created during the build — a hero image, a product video, a jingle — shows up here, ready to use in the project or download.
The Files drawer browses the project's file tree — everything LiTT created or changed, organized the way a developer would expect. Components surfaces the reusable pieces. Together they answer “what is actually in my project right now?”
The Terminal drawer is a real terminal connected to your project's environment. LiTT uses it to install dependencies, run builds and tests, and inspect the project — every command is visible to you. You can also type your own commands any time: installing a package, running a script, or checking what changed. If the terminal shows as disconnected, reconnect it from the drawer — see Troubleshooting.
The activity timeline is the project's log: missions sent, plans made, files edited, commands run, previews started, deployments prepared. When something surprises you, the timeline shows exactly what led to it.
The Deploy button in the Studio header opens the preview/deploy flow for the active project. Deploying is the deliberate step that prepares your project to go live — and it may ask for your approval before anything publishes. What “deployed” means, and how it differs from preview, is covered in Preview & Deployment.
On smaller screens Studio collapses into the same three areas with the LiTT panel available as an overlay sheet. All the same tabs — Plan, Canvas, Code, Preview, Media — and the terminal drawer work the same way; only the layout adapts.
Learn by doing
The fastest way to learn Studio is the Quick Start: build one small project end to end and you'll have touched every area on this page.