Start in Chat. Sol0 is already set up for normal use when you can sign in and send a message; Setup is an owner-only recovery and launch surface, not everyday onboarding.
1Sign in and open Chat.
2Send a normal message, then keep the conversation or start a new one.
3Open Status if sending is paused; it tells you whether Sol0 can safely accept a new message.
Chat is the main Sol0 workspace. It keeps your draft safe when the service is paused and explains a temporary problem in plain language instead of showing raw provider or database errors.
1Write a normal request, or use /help to see the available chat commands.
2Use Chat when you want Sol0 to carry out allowed work; use Plan when you want a read-only plan first.
3Choose a model and effort level when you need a different balance of speed and depth.
4Research results keep approved sources and citations readable instead of showing raw provider response data in the conversation.
5Attach a file only when it helps with the request. Very large browser-only files may stay on this device.
Threads are your conversations. When you are signed in, Sol0 can keep them online; your browser also keeps a local cache so you can export your work and avoid losing a draft.
1Use the conversation list to reopen, rename, export, or delete a thread.
2Use New chat when a different topic deserves its own history.
3Use Account & memory to review personalisation and remove captured memories one at a time.
Agents are reusable specialised assistants. Foundry is Sol0's visual builder for agent-driven experiences. Both should have only the abilities they genuinely need.
1Choose an agent when a repeated kind of work benefits from a consistent approach.
2Review its model, allowed tools, and connections before you let it run work.
3Use Foundry only when you are building a focused agent experience rather than starting a normal chat.
Automations are saved work that can run later, run manually, or begin from another Sol0 surface. They are useful when you want a repeatable process, not a one-off chat.
1Set up the task in Settings → Tasks.
2Use a clear name and check the result in Tasks after it runs.
3Review and remove an automation when it is no longer useful.
Settings → AI & media is where you choose models and manage optional skills, images, and voice. Capability availability is shown in Sol0 status and can change when the live service changes.
1Choose the model that suits the work; a more capable model may be slower or cost more.
2Use images and spoken replies when the app reports they are available.
3Live Conversation is separate from dictating a message or playing a reply. If it is unavailable, it is not ready to use yet.
You control your own chat and memory data. The privacy controls are intentionally specific about what they clear so a button never promises to erase more than it actually does.
1Export, import, or clear chat and memory data from Settings → Advanced → Local chat data.
2Check Offline storage there to see whether this browser is protecting local drafts and chat cache; export important chats when it is only best effort.
3Use Account & memory to review personalisation and delete captured memories one by one.
4Use the connection and token controls themselves when you want to remove those permissions.
You can install Sol0's website on a phone home screen. It remains the same hosted product, with a chat bar and controls designed for a smaller screen.
1Open Sol0 in your phone browser and use its install or Add to Home Screen action.
2Open the installed app and sign in normally.
3Keep a draft in the composer if the app says chat is paused, then retry once it becomes available.
4When you are offline, recent saved thread titles and previews remain visible in a read-only view; reconnect before opening a chat or sending a message.
The website cannot read files on your Mac. Filesystem, Git, shell, browser, and other local tools need the desktop app and a workspace you explicitly choose.
1Open the desktop app when you want to work with a folder on your Mac.
2Choose one safe project folder, then enable and test the local bridge before asking Sol0 to use it.
3Review every write request. The desktop app should ask before it changes your local files.
Settings is organised by what you are trying to manage, not by technical provider. Start with Account & memory, AI & media, Tools & connections, and Tasks; less common options are grouped separately.
1Use Account & memory for profile, personalisation, and saved memory.
2Use AI & media for models, skills, images, and voice.
3Use Tools & connections for outside accounts, local tools, tool servers, and access tokens.
4Use Advanced for local chat data, updates, and owner-only runtime status.
Shortcuts use the same actions as Sol0's menus and command surfaces. You can adjust a binding or return to the defaults when a shortcut stops feeling natural.
1Open Shortcuts in Settings.
2Change one binding at a time and watch for conflict warnings.
3Use Reset to restore Sol0's default keyboard map.
Status tells you whether Sol0 can accept a new conversation safely. Owner-only runtime details stay out of normal chat so a temporary problem does not become a confusing technical checklist.
1Open Status before guessing why a message cannot be sent.
2Reload the relevant page and keep your draft rather than retyping it.
3If a specific connection or task is affected, open that area to check its own status.
Setup Center is for the Sol0 owner to launch or recover a service. It is not a normal user task, and normal users should never be asked to paste production keys or provider details into chat.
1Use it only when you own the deployment and need to repair a missing runtime requirement.
2Store secrets in the approved secret store, never in a message, screenshot, or source file.
3After a release, verify a real chat, then refresh the current-state record before calling the work complete.