Setup Directory

Operating-system directory 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.

Select a working directory you own. It does not need Git, an IDE, or an application framework. The installer creates .SYSTEMX beneath that directory. It refuses a drive/filesystem root; use a named working folder such as C:\Projects\Example, not C:\ or a Windows system directory.

PowerShell, after installing the library into your chosen Python environment:

systemx install --target 'C:\Projects\Example' --profile directory
systemx run --target 'C:\Projects\Example' -- context --agent agent.0

From an extracted template on Windows:

& .\.SYSTEMX\INSTALL.ps1 --target 'C:\Projects\Example' --profile directory
& 'C:\Projects\Example\.SYSTEMX\SYSTEMX.ps1' status

macOS/Linux, from an extracted template:

bash .SYSTEMX/INSTALL.sh --target "$HOME/Projects/Example" --profile directory
bash "$HOME/Projects/Example/.SYSTEMX/SYSTEMX.sh" status

Python 3.9+ is required for commands. Documentation works without it. SYSTEMX does not install Python, elevate privileges, change execution policy, add login items, or create OS schedulers. In Bash, set SYSTEMX_PYTHON to the intended Python executable if your terminal uses a different environment. Read installation for update policy and the library guide for Git-based setup.

CLI and named projects

For a managed alpha.5 workspace, systemx projects --target 'C:\Projects\Example' -- list reads registered child identities; add --project NAME to a scoped operation. The records live at .SYSTEMX/Projects/NAME/.SYSTEMXP and share outer tools. A reviewed folder-only copy can invoke its local SYSTEMX.ps1 or SYSTEMX.sh without installation metadata. Invalid managed markers fail closed, and the external manager still requires valid managed selection before run/projects. Use tools-guide or menu option 18 for CLI and Tools.

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.