Documentation
LiTT is an AI project operator. You describe what you want in plain language, and LiTT plans the work, edits real files, runs terminal commands, verifies the result, and prepares it to ship. Bring the idea — LiTT builds the rest.
Every build follows the same loop — whether you type it into Studio chat or run it from the CLI:
Nothing is faked
LiTT works on real files in a real project workspace. The preview pane shows your actual project running — not a mockup — and the terminal runs real commands against it.Studio is the main workspace. It has three areas:
The full tour — every tab, drawer, and control — is in the Studio Guide.
A project is the thing you are building — a website, an app, a campaign. Each project gets its own workspace: the files, the preview runtime, and a terminal session connected to that environment. Create a project from a template or start blank, then select it to make it active. Everything in Studio — chat, preview, terminal — follows the active project.
You drive LiTT by chatting. Pick a specialist for the job — LiTT, Coder (engineering), Writer, Researcher, Marketer, Analyst, Nova, Forge, Echo — or use LiTT Auto, which routes your request automatically. You can also choose the underlying model, including your own API keys, with live provider health shown in the selector.
The Preview tab runs your active project so you can see and click through it while LiTT works. Preview starts automatically for the active project, and if it ever fails to start you can retry it from the preview panel. Preview is a working copy for iteration — it is not the same as a production deployment. See Preview & Deployment.
Studio includes a real terminal connected to your project's environment. LiTT uses it to install dependencies, run builds and tests, and inspect the project — and you can open it yourself any time you want to run a command by hand.
Building is a conversation, not a form. Describe what you want, watch LiTT plan and edit files, check the preview, and keep iterating: “change the hero,” “fix this build error,” “make the button bigger.” Each round goes through build → verify → preview until it looks right. Worked examples are in Building with LiTT.
When the project is ready, the Deploy action in Studio prepares it to go live. Publishing is a deliberate step and may ask for your approval first — previewing is free and unlimited, deploying is the moment you decide the world should see it.
Prefer the terminal? The LiTT CLI (@litlabs1/litt-cli) brings the same operator to your command line: health checks, builds, tests, and deployment verification. See Installation & Commands.
The Marketplace offers specialist agents you can install into your workspace — for code review, content, support, analytics, and more. Installing requires an account. Details in Marketplace.
LiTT asks for your approval before consequential actions like deploying or publishing. In the CLI you can also set a permission mode — plan, act, or auto — to control how much runs without asking. How it all works is covered in Safety & Approvals.
Pick where to go next — or start at the beginning with the Quick Start.
A step-by-step walkthrough: sign up, open Studio, build your first project, preview it, and deploy.
ReadThe Studio interface: LiTT chat, Plan, Canvas, Code, Preview, Media, Files, Terminal, and activity.
ReadReal example prompts and the build → verify → preview → deploy loop.
ReadHow preview works, how it differs from production deployment, retries, and approvals.
ReadInstall the LiTT CLI, sign in, and use the real commands: doctor, check, build, deploy verify, and more.
ReadFind and install specialist agents that extend what LiTT can do.
ReadHow LiTT asks for approval before consequential actions, and how permission modes work.
ReadFix common launch issues: preview not starting, terminal disconnected, approvals, and CLI connectivity.
Read