Open Setup when Sol0 says something is missing. Open Chat when you want to use the app. Sol0 keeps working in local preview mode while the required services are still being connected.
1Use Setup first if this is a fresh production install.
2Connect Login, Database, and AI Brain before expecting the live cloud app to feel complete.
3Return to Chat after setup and send one real message to confirm the app is ready.
Setup Center is the friendly checklist for connecting services. It tells you what each key unlocks, where to get it, and whether Sol0 is missing, checking, connected, or waiting for a redeploy.
1Paste service values only into their matching setup step.
2Use Validate selected step before saving when you want a quick sanity check.
3Save to Vercel, redeploy, then refresh Setup to see the connected state.
Chat is the main Sol0 workspace. On mobile, the composer stays at the bottom like a normal chat app. If an AI, image, or voice provider is missing, Sol0 explains the exact setup step instead of crashing.
1Type a normal message, or use slash commands like /help for the command list.
2Pick a mode with the toggle next to the model: Chat lets Sol0 act, Plan keeps it read-only and drafts a plan first. /chat and /plan do the same from the composer.
3Set Effort next to the model (Off, Low, Medium, High) to control how hard a Claude model thinks before answering; its reasoning streams above the reply, and Working… shows elapsed time while it runs.
4Check the plug icon by the composer to see how many tools are connected — the full file, git, and shell toolset lives in the desktop app, so on the web it reads zero unless the sandbox is enabled.
5Click New chat (or Chat in the top bar) to start a fresh, empty conversation anytime.
6Attach files when needed; very large browser-only attachments stay local.
7Use Connect Sol0 when a message says a provider or database is missing.
Threads sync to the server after Login and Database are connected. Before that, Sol0 keeps browser-local threads so you can still try the app and export your data.
1Use the thread sidebar to reopen, rename, export, or delete conversations.
2Use Local chat data in Advanced settings to import, export, or clear browser data.
3If Sol0 says local only, connect Database in Setup to enable server-synced history.
Mobile Sol0 keeps the chat bar at the bottom, moves extra controls into thumb-friendly sheets, and never opens the keyboard until you tap an input yourself.
1Use the left panel button for navigation and threads.
2Use the right panel button for context, runtime status, voice, and setup actions.
3Open deeper controls only when needed; mobile panels use accordions instead of clutter.
Settings is where you tune the regular app defaults. Models controls the AI default, Voice controls speech behavior, Appearance controls theme, and Advanced shows runtime details.
1Use Models to pick the default model and chat mode.
2Use Voice and Appearance for speech language and theme.
3Use Tools, Skills, Workflows, and Advanced to see what is connected and what still needs setup.
Shortcuts are powered by the same action registry as the top nav, panels, command surfaces, and documentation. You can edit bindings and reset to the Sol0 defaults.
1Open Shortcuts in Settings.
2Change one binding at a time and watch for conflict warnings.
3Use Reset if you want Sol0's default keyboard map back.
Readiness cards turn confusing setup failures into plain language. Missing means you still need a key. Local mode means the browser fallback is active. Ready means that part is connected.
1Open Advanced settings when something feels unavailable.
2Read the status label first: ready, missing, fallback, invalid, or local mode.
3Follow the setup link for the exact service instead of guessing which key is missing.
The website cannot read files on your Mac. Local filesystem, git, shell, browser, and MCP-style tools need the Tauri desktop app plus a workspace you explicitly choose.
1Open Sol0 in the desktop app when you want local Mac tools.
2Choose a safe project folder, then enable local tools in the desktop app.
3Run Test desktop tools before using local commands in Chat.
Use ForgeCode beside Sol0 when you want prompts straight from Zsh.
ForgeCode fits as the shell-native coding harness in the workflow: install the binary, enable the Zsh plugin, log in to a provider, then keep Sol0 open for guided setup, essays, chat history, and desktop tool readiness.
Installcurl -fsSL https://forgecode.dev/cli | sh
Installs the ForgeCode CLI binary on macOS, Linux, Android, WSL, or Git Bash.
Verifyforge --help
Confirms the binary is available before touching shell integration.
Enable Zshforge zsh setup && exec zsh
Runs the plugin wizard, then reloads the terminal so the colon prompt trigger is active.
Connect AI:login && :model
Selects a provider and model before the first prompt from your shell.
Keep ForgeCode provider keys in its own CLI login flow; do not paste them into Sol0 unless a Sol0 setup field explicitly asks for that service.
If the colon trigger does not respond after setup, run forge zsh doctor before changing Sol0 settings.
Use Sol0's desktop setup card to verify local tools, then use ForgeCode for fast terminal prompts in the same project.
The Launch Checklist is the final human check. Sol0 can verify wiring, but you still confirm real login, real chat, server thread persistence, production URL, and desktop app behavior.
1Finish required cloud setup, redeploy, and refresh Setup.
2Tick manual checks only after trying them with your real accounts.
3Copy or download the launch report when you want a clean release note.
