User Guide

You keep your work in files, and your AI keeps it in a chat window. So you spend the day carrying material between the two: dragging a document into a box, pasting an answer back out, explaining the same project again tomorrow because the box forgot it.

gOS puts the intelligence where the work already is. It opens on a desktop: one window over your own files, one field at the top, and the Sim behind it.

Everything on this page is a surface that exists in the app today.

Search desktop…gOSDesktop···AudioBuildCoordinatorDocumentsDriveFlowsGenesImagesTEXPapersSettingsSimulatorTrainingVideoWallet
The window you get on launch: search and the Sim in the title bar, your Spaces and system surfaces in the grid below.

01

The desktop is the app.

The window is a file browser over your own material. Your Media Spaces are Images, Papers, Audio, Video, Drive, Documents and Genes. They sit beside the surfaces you can open: Flows, Build, Coordinator, Simulator, Training, Wallet and Settings. The breadcrumb names where you are, the slider sizes the icons, and the control on the right switches the same window between chat, grid, list and columns.

chatgridlistcolumnsOne window, one Space, four ways to look at it. The control at the top right switches between them.
Chat, grid, list and columns are four readings of one Space, not four modes with different powers.
  • Icons are your files, not shortcuts into a chat.
  • One window, four views of the same place.
  • The breadcrumb always names the Space you are in.

02

One field runs everything.

The field at the top searches files, flows and settings at once, and it is also where you talk to the Sim. A slash runs a flow directly. Plain language lets the Navigator choose the flow for you. Voice shares the same session as the text, so speaking is not a separate channel with its own memory.

type a name, a slash command, or a sentencefilesa name in any Space,matched as you typeflows/papers, /image,/mind, /trainingsettingsruntime, authorizations,devices, activationthe Simplain language, routedby the NavigatorVoice enters the same session as the text, so speaking is not a second assistant with its own memory.
One field, four destinations. Which one you get depends on what you typed, not on a mode you set first.
  • Search files, flows and settings in one place.
  • Slash a flow to run it now.
  • Speak or type into the same session.

03

A Space is where the work and the permissions live.

A Space is a durable namespace: the files, the sessions, the runs, and the boundary a flow is allowed to touch. Flows declare their filesystem scopes and their tool allowlist in the manifest, so a run reaches what the Space grants and nothing more. Moving to another Space changes what the same sentence is able to do.

Spacea folder that carries intentfiles the work needsthe sessions that happened herethe runs and their tracesthe flows this project useseverything a run may touch,and nothing outside itthe flow manifest names the boundaryread: ["Store/**"]write: ["Space/Drive/**"]toolAllowlist: [...]max_tool_calls_per_run: 1a path outside these scopes stops the runMove to another Space and the same sentence reaches a different set of files.
The Space holds the material; the manifest says which part of it this flow may touch.
  • Keep a project's files and its runs together.
  • Permissions are declared, not assumed.
  • Return later without rebuilding the context.

04

Flows are the verbs.

Forty-one flows ship with the app. Some are jobs you run: generate an image, apply a transition between clips, scrape a page, pull down a board, search a mailbox, cut a reel, write a paper beside a live compile. Others are surfaces you open, like Mind, Training, Wallet and Settings. Each one is a manifest rather than a script, and each one is also a tool the Sim can call in the middle of something else.

/imagegenerate on the machine/paperswrite beside a live compile/scrapea page into this Space/reel-machinephotos, narration, music/mindrecall and inspect memory/trainingsignals into local adapters/settingsruntime, access, devices/walletidentity and credits41 of these ship with the app. Each is a manifest rather than a script,and each is also a tool the Sim can call in the middle of another job.
A slash and a name. Each of these is a manifest the Sim can also call on its own.
  • Run a flow from the field or from the grid.
  • The Sim can call the same flow itself.
  • What you build becomes another verb.

05

The Sim picks a worker for the job.

Requests do not all deserve the same machine. gOS carries five named runtime profiles and a Navigator that chooses between them: Instant for a quick answer, Thinking for a hard one, Working for a long job, Private for anything that must not leave the Mac, and Personalized when your own context should shape the result. Settings → Runtime sets the default posture: local-first, or online-first.

the requestwhat it is actually askingfor, and how much it costsNavigatorpicks a laneInstanta fast answer, no deliberationThinkingthe hard ones, thought throughWorkinglong jobs, while you workPrivatelocal only, no route outPersonalizedyour context shapes the resultSettings → Runtime sets the posture the Navigator works inside: local-first, or online-first.
Five named profiles, one router, and a posture you set. Nothing here is picked at random.
  • Instant, Thinking, Working, Private, Personalized.
  • The Navigator routes; you can overrule it.
  • One switch sets local-first or online-first.

06

Mind remembers, Training teaches.

Mind is memory as a place you can open: prior Spaces, live work, and what the system has learned about how you work. Training reviews the signals a run leaves behind, curates them into a dataset, and produces adapters that stay on the machine. Learning proposes changes. It does not quietly rewrite how gOS behaves.

Mindprior Spaces, and what happened in themthe work that is live right nowwhat the system believes about how you worka surface you open and read, not ahidden profile assembled about youTrainingthe signals a run leaves behindcurated into a dataset you can seeproducing adapters that stay on the Maclearning proposes; promoting it is anapproval like any other durable changeSignals flow left to right. Nothing crosses back into how gOS behaves without you approving it.
Signals move left to right. Nothing crosses back into behaviour without an approval.
  • Open memory instead of guessing at it.
  • Turn your own signals into local adapters.
  • Nothing durable changes without approval.

Give gOS one real job inside one Space, watch what it asks for, then keep the run that worked.