No long prompt transfer
The task body is written directly to the repository.
Applicable Convention workflow
Conversation Between Chats
This guide shows the shortest safe user workflow for repository-backed cooperation between specialized chats.
xcq creates a temporary ChatGPT handover, while xcq <lcp-reference> performs the Cooperation operation.Minimal workflow
- Start in Chat A.xco lcp_bol1 Review BUSS connector geometryChat A validates the target LCP identity and writes a HANDSHAKE_REQUEST to Chat A's own LCP file.
- Switch to Chat B.xcq lcp_mep1Chat B reads Chat A's LCP, verifies sender, recipient, URL suffix, thread, and scope, then writes HANDSHAKE_ACCEPTED to Chat B's own LCP.
- Return to Chat A.xcq lcp_bol1Chat A verifies the acceptance and writes the actual TASK_REQUEST.
- Continue with short references.
The chats exchange RESPONSE, ACKNOWLEDGED, and finally CLOSED through their own LCP files.
What the user no longer carries
No Git mechanics
The chat reads and writes the correct LCP file through the connector.
No identity guessing
The four-character alias is always checked against the binding URL suffix.
Teams and durable continuity
For multi-participant work, use Agent, Team, and Network Coordination to separate current assignments and ownership from durable XRT memory, private transcript evidence, and canonical repository results. A resumed substantial task runs the Continuity Freshness Gate before execution.
Execution gate
| Required match | Reason |
|---|---|
| Recipient code + URL suffix | Prevents execution in the wrong chat. |
| Coop Thread | Prevents crossing parallel work streams. |
| Accepted handshake Post ID | Proves cooperation was explicitly accepted. |
| Reply chain | Preserves message order and traceability. |
| Applicable Convention | Defines the active workflow and authority. |
Status lifecycle
INITIALIZED (identity only) → HANDSHAKE_REQUEST → HANDSHAKE_ACCEPTED → TASK_REQUEST → RESPONSE → ACKNOWLEDGED → CLOSED
A mismatch produces IDENTITY_MISMATCH and no execution.