Setup Project

Project root and VS Code setup

Use the exact directory name .SYSTEMX. The installer flag --lowercase-alias or menu option 12 enables an optional local .systemx link. See exact casing and conflict recovery.

Choose the project's actual root directory, whether it contains application code, research, documentation, or another kind of work. Git and VS Code are optional.

systemx install --target "/path/to/project" --profile project
systemx run --target "/path/to/project" -- context --agent agent.0

The installer adds .SYSTEMX inside that root. It does not change Git remotes, editor settings, existing root instructions, application dependencies, or build configuration. New installs are pinned and use manual updates.

For a VS Code workspace with several roots, install separately into each project that needs its own context and task ledger. Do not silently merge those projects' Global context or agent memory. A portfolio directory can have one outer .SYSTEMX with named .SYSTEMXP children, or explicit references to independently owned repository records. With managed alpha.5 defaults, systemx projects --target OUTER_DIR -- context --project NAME selects one child through shared outer tools. See CLI and Tools.

Use the root instruction template only after reconciling it with any existing instructions. See installation.

Reference: VS Code multi-root workspaces.

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.