Get oriented.
Help starts with orientation. gOS brings chat, files, flows, models, memory, and approvals into one workspace, so the first job is often knowing where you are.
This page is the calm starting point for setup, concepts, troubleshooting, and support.
01
Most questions begin with three words.
Where am I? What changed? What can I approve? These questions are normal in a system that can do real work. gOS help will answer them in the same order: context first, action second, troubleshooting third.
- Find the current Space.
- Check the latest Sim message.
- Look for pending approvals.
02
When something feels unclear, start with the Space.
A Space holds the project, files, sessions, resources, and flows around a piece of work. If the Sim seems to be missing context, the Space is the first place to look. Adding the right file or narrowing the intent often fixes more than a longer prompt.
- Confirm the active Space.
- Add the files the task depends on.
- Restate the desired outcome simply.
03
Use the concepts.
The fastest support path is often conceptual. Sim means the agent. Space means the project container. Flow means reusable work. Garden means resources. Mind means memory. Once those words are clear, the interface becomes much easier to navigate.
- Sim: who helps.
- Space: where the work lives.
- Flow: how repeated work runs.
04
Reach out from the session.
When the answer is not obvious, support should be close to the work itself. The helpline path is designed to start from the gOS session so context is easier to understand. You should not have to translate a whole workspace into a support ticket from scratch.
- Ask from the place where the issue happened.
- Share the relevant context intentionally.
- Keep private material scoped.
Help should make the system feel smaller, friendlier, and easier to return to.