| name | multi-session-etiquette |
| description | MUST READ when a _peers advisory appears or multiple AI sessions are active in the same TouchDesigner project: advisory contract, claim leases, destructive gates, raw-file-edit visibility, division of labor. |
Multi-Session Etiquette
Multiple AI sessions (Claude Code windows, other MCP clients) often work on
the same TouchDesigner project at once -- same live network, same
externalized files, same git tree. Envoy coordinates them; this rule is how
you cooperate.
At session start
Call get_sessions once early. It lists every connected session (label,
idle time, recent_scopes it modified, claims it holds, you = your own
session id). If peers are active, prefer working in a subtree none of them
touched recently.
Read the advisories -- they come to you
- Any tool response may carry
_peers: another session touched territory
overlapping your request (op path or externalized file) within ~10 min.
conflict: false -- informational. Note it, re-read files before editing
them, and avoid building on top of a peer's in-flight work.conflict: true (a peer WROTE there within the last minute) is a HARD
STOP. Do not keep mutating that scope. Check get_sessions, tell the
user who is working there, and either divide the work (different
subtrees) or get explicit user direction before proceeding.- A
CONFLICT WARNING or MULTI-SESSION GATE line in _logs follows the
same contract as a LAYOUT WARNING: never end a turn without addressing it.
Claim before big or destructive work
- Before a large build, a refactor of a COMP subtree, or editing an
externalized file, call
claim_scope with the NARROWEST scope that
covers the work and a short note ("rebuilding camera rig"): an op-path
prefix (), a file (), or a
special scope ( before a test run).
