Help
Real fixes for the issues you're most likely to hit at launch. Start at the top — most problems are one of these.
If the terminal shows as disconnected or never starts, open the Terminal drawer and reconnect it from there. The terminal is only the visible console — LiTT installs dependencies, runs builds, and executes commands through the server, so chat and builds keep working while it's disconnected. If reconnecting fails repeatedly, refresh the page: Studio re-establishes the session and your files are safe.
If a deployment seems stuck, check whether it's waiting on you: deploying is a consequential action, so Studio may be holding for your approval. Look for the approval prompt in the conversation or header, approve it, and the deploy proceeds. Declining or ignoring it leaves everything exactly as it was — nothing publishes halfway. See Safety & Approvals.
If LiTT reports that a model or provider failed, it will tell you what happened rather than silently degrading. Your options:
If Studio looks empty — no files, no preview, chat with no context — no project is active. Select a project to make it active; chat, preview, and terminal all follow the active project. Creating a new project from a template is the fastest way to get back to a working state.
Refreshing the page is safe: your project files are saved, and Studio re-establishes the chat session, preview, and terminal connection on reload. If the UI ever gets into a weird state — a stuck spinner, a panel that won't update — a refresh is a legitimate first fix, not a workaround.
litt doctor--remote work needs the terminal server to be reachable. Confirm you're signed in (litt whoami) and not forcing LITT_LOCAL_ONLY=1.litt workspace current shows the selected workspace; litt workspace select switches it.Still stuck?
Email [email protected] with what you were doing, what you expected, and what you saw instead — including any error text. The activity timeline and terminal output are the most useful things you can include.