Setup LLM Chat

LLM chat setup

Start with the copyable New Chat Setup Prompt. That page includes project installation, chat-only use, and a prompt for resuming from exported project context.

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 SYSTEMX as project reference material within the active chat's instruction hierarchy. A setup URL does not give an LLM filesystem or cloud access.

With local files, prepare a packet from the same template and project records:

systemx install --target "/path/to/project" --profile chat
systemx export-chat --target "/path/to/project" --output "/path/to/new-session.md"

Review the packet for private content before attaching it to a chat. The export includes the selected release's guidance and bounded current project context; it does not upload anything and refuses to overwrite an existing export. Truncation notices tell the reader which original files still need inspection.

If the chat can read a setup URL but cannot write files, use this protocol:

1. Identify the selected template release and active project. Load Global context, Master Plan, current tasks, and the selected agent's memory from attachments or authorized tools. Request missing records instead of inventing them.
2. Maintain the same canonical paths and task IDs. Propose explicit record changes or downloadable replacement documents for the owner to retain.
3. Mark file updates as applied only after a writable tool changes them and reads them back. A chat answer alone is not durable project memory.
4. Export a checkpoint at handoff and attach the current records to the next session. Selecting a newer standard must preserve those project records.

Without a terminal or writable connector, updates and version selection are manual. The latest public guide is a discovery URL; choose a release-tag URL for a reproducible standard. Profiles do not select an LLM vendor, model, agent count, or orchestration runtime. A future MCP adapter can use the same library and format; this release does not install an MCP server.

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.

Four roles across chat and a CLI host

Agent 0 coordinates the selected scope; Agent X records observed events and Agent Z reviews saved evidence. A chat may hand an independently bounded task to Agent Y on an authorized filesystem/CLI host using its existing canonical task ID, provider choice, base revision, allowed paths, and reviewed packet. Chat-only access cannot launch that host’s provider or infer a successful result. Return original evidence to Agent 0 for independent checks and acceptance. A task-selected CLI or draft PR does not automatically synchronize private conversations. See the current four-part system guide.