Setup Google Drive

Google Drive setup

Use the exact directory name .SYSTEMX. Do not create or upload a separate .systemx tree. OS aliases are local conveniences and are not part of this cloud/chat format; see the case contract.

Use the same regular Markdown and JSON files in a project folder made available locally by Drive for desktop. Choose the real mounted/mirrored path on your computer; a drive.google.com folder URL is not a filesystem path.

systemx install --target "/your/local/Drive/Project" --profile drive
systemx run --target "/your/local/Drive/Project" --offline -- status

On Windows, quote the full path, for example G:\My Drive\Project; the drive letter and folder location are user-selected, not assumed by the installer. Make the project available offline before running commands. Google documents mirroring and streaming in Drive for desktop help.

The profile does not create a Google account, obtain OAuth access, call Drive APIs, change sharing, or convert files into native Google Docs. Drive performs the synchronization. Keep one writing computer/session active for a shared project and wait for synchronization before switching: the local lock is not a distributed lock across computers. Resolve Drive conflict copies explicitly.

For browser-only Drive, upload the reviewed folder's ordinary files while preserving their hierarchy, or upload a chat export. Updates there require an explicit download/review/upload cycle or a separately authorized connector. There is no background cloud updater. Keep private records in an appropriately shared folder and never publish a populated project as a template.

Shared chats, cloud references, and bots

The shared workspace guide covers repository, portfolio, and hybrid ownership; Drive URLs and connectors; cloud snapshots; local/VM bot memory; and explicit handoffs between chats. Every child needs the named path Projects/NAME/.SYSTEMXP. Choose one authority for each task ledger, verify write/readback and transport, and keep workers scoped to the selected project. For start-to-finish execution, use the one-shot project guide.

Agent Y and private execution state

A locally available Git repository and reviewed installed CLI can support Agent Y while Drive carries portable coordination records. Choose the provider and execution host per task; keep one canonical writer. A browser-only Drive folder cannot run the CLI. Exclude host-local state/agent-y/, prompt packets, and retained worktrees from cloud sync as appropriate: Git ignores do not exclude them from Drive. The portable job remains in its selected root or named .SYSTEMXP; another host must reconcile with Agent 0 and prepare its own reviewed handoff. Use X for real observed times, Y for the bounded CLI result, and Z for matching evidence review; Agent 0/user owns acceptance. See the current four-part system guide.