The chat
Build by chatting — chats, the App / Server / Database controls, and the message box.
The Chat tab is where you actually build. You describe what you want, Solitud writes and runs the code, and your live app updates. This page covers the chat interface: your chats, the app controls, and the message box.
One shared calendar, or one per staff member?
Chats
A workspace can hold multiple chats — separate conversation threads, each with its own memory. Use them to keep different lines of work apart (for example, one chat for the booking flow, another for the admin dashboard).
Your chats are listed in the left sidebar of the Chat tab.
Create a chat
Click the New chat button (the ✚ icon) at the top of the chat list. A fresh chat opens and focuses the message box, ready for your first message.
Rename a chat
Hover a chat in the list and click the pencil icon. The row becomes an inline text box — type a new name and press Enter to save.
Delete a chat
Hover a chat and click the trash icon. You'll be asked to confirm:
Delete this chat? The chat and its memory will be permanently deleted. This can't be undone.
Deleting a chat removes its conversation and the memory tied to it. It does not delete your app or the workspace — only that thread.
App controls
At the top of the chat view, a status bar shows the health of your running app and lets you restart it.
| Control | What it shows / does |
|---|---|
| App | Health of your frontend. When it's running, click it to open your live app in a new tab. |
| Server | Health of your backend (the FastAPI server). |
| Database | Health of your PostgreSQL database. |
| Restart app | Restarts your running app — frontend, backend, and database together. Disabled while a build is delivering code (stop the build first). |
Each pill turns green when that component is healthy. If something looks stuck, Restart app is the quickest fix — it restarts just the app, and your data is preserved. To redeploy the whole workspace instead, use Restart on the Manage tab.
The message box
The composer at the bottom of the chat is where you type. Its placeholder reads "Message Solitud… (paste or drop files too)."
- Send — press Enter to send. Use Shift + Enter for a new line. You can also click the Send button. The box grows as you type.
- Attach files — click the paperclip, or paste / drag-and-drop files straight into the chat. Attached files appear as small pills above the box; remove one with its ✕. (See supported files below.)
- Dictate — click the microphone to speak instead of type, where your browser supports it.
Attaching files
Attach reference material the AI should use — screenshots, mockups, spreadsheets, PDFs, documents. Common image, document, and text formats are accepted, with per-file size limits; oversized or unsupported files are rejected with a message. HEIC images are converted to JPEG automatically.
Attachments become part of the chat's context, so the AI can read and act on them. Some requests ask you to attach a specific file — see the attachment card.
Talk vs. Build modes
Just below the message box is a mode toggle. Every message you send runs in the selected mode:
| Mode | Use it to |
|---|---|
| Talk | Talk it through — no code, just map the idea. The AI asks questions, sketches options, and builds a shared understanding. Nothing is changed. |
| Build | Build it — the AI edits and ships your app. The AI writes code, runs the app, and verifies it's live. |
Build is the default. Switch to Talk when a decision is fuzzy or far-reaching, then flip back to Build when you know the next concrete step. You can change mode per message.
Talking is what makes it agentic
Talk mode isn't small talk — it's where Solitud builds a real model of what you're after: who the app is for, what actually matters, and where the edges are. That understanding is what lets the AI act on its own once you switch to Build — making the dozens of small decisions a build requires in the direction you'd have chosen, instead of guessing and waiting to be corrected.
In other words, the conversation is the steering. The more you talk an idea through, the more agentic the build becomes: Solitud takes broader, more confident strokes because it understands the why, not just the what. A few minutes in Talk up front routinely saves a lot of course-correcting later — and it compounds, because what Solitud learns about you carries forward.
Rule of thumb: fuzzy or far-reaching? Talk. Clear next step? Build. When in doubt, talk first — it's cheap, and it makes everything after it sharper.
How responses appear
Solitud replies with normal, formatted text — and, when it needs something from you or wants to show a result, with interactive message cards: a clarifying question, a request to provide a value or a secret, a file to download, DNS records to copy, and so on. The next page covers each card type.