Start with a Space.

gOS is easiest to understand as a place for intent. You begin with something you want to do, then give the system the files, context, and permission it needs.

The Sim helps turn that intent into useful work: a search, a document, a decision, a generated asset, a saved workflow, or a clearer next step.

01

The Sim is your personal executive agent.

The Sim is the persistent intelligence inside gOS. It is not just a chat box. It can listen, reason, search, launch flows, use tools, and keep track of the work in front of it. You stay in charge of scope and approval. The Sim helps reduce the back and forth as it learns what good work looks like for you.

  • Ask in plain language.
  • Review what the Sim plans to do.
  • Approve important changes before they become durable.

02

Spaces are folders with intent.

A Space is a folder on your Mac that carries purpose. It can contain inputs, outputs, sessions, resources, and flows for one project or area of work. You can think of a Space as both a file system view and a conversation view. The same work can be browsed, discussed, and acted on.

  • Keep projects separated.
  • Put source files close to the task.
  • Return later without rebuilding the whole context.

03

Flows turn repeated work into one reusable action.

A Flow is a procedure the Sim can run again. It can gather inputs, call models, use tools, render an interface, produce files, and save the result. Flows start simple. A repeated prompt can become a command, then a structured workflow, then a dependable part of your workspace.

  • Run a slash command.
  • Let the Sim suggest a flow.
  • Save a useful process for next time.

04

Garden and Mind keep the work alive.

Garden is where your resources live: documents, media, research, downloads, and other material the Sim can help you find and use. Mind is the inspectable memory layer. It helps gOS remember preferences, project facts, and working context without hiding the learning from you.

  • Browse resources visually.
  • Search across your workspace.
  • Inspect what the system remembers.

Start small. Give gOS one real job, review the result, then let the useful patterns become tools.