Organize names and colors

Use organize-session with an explicit request such as “keep the existing names, make these drum tracks red, and match their selected clips.” Resolve the exact tracks, Returns, Main, scenes and clips first. Colors supplement useful names; they should not be the sole way to identify a part. A name or instrument is evidence to discuss, not proof of a musical role.

Read and apply colors

The all profile provides get_live_object_colors and set_live_object_colors. Read one to 64 unique canonical IDs:

The read returns each native name, RGB color, colorIndex and supported status without moving focus. An uncolored scene has color: null and its native unassigned index (null on the tested Live, or -1 when returned); it can receive an explicit color. Empty slots are refused. Resolve IDs from current lists; indices alone are not persistent identities.

Plan an explicit map, using fresh Set guards:

{
  "changes": [
    {"objectId": "track-2", "color": "#FF0000"},
    {"objectId": "track-2:clip-0", "color": "#FF0000"}
  ],
  "expectedStateVersion": 12,
  "expectedSetFingerprint": "use-the-current-observed-fingerprint"
}

Review the inert plan before confirming its single-use token and hash. It binds current native objects, names, colors and selection; intervening manual changes invalidate it even at the same bridge state version. Native execution rechecks every target between writes and groups the edits into one Live undo step. It requests no playback or musical changes. Track color inheritance may also change the appearance of Rack chains; clips are recolored only when explicitly listed.

Live can choose a nearby palette color. Inspect writeCompleted, identityRetained, selectionUnchanged and every object's actual color, colorIndex, writeReturned and exactMatch. writeCompleted means the writes returned and their observed native results were retained; it does not mean every requested RGB was represented exactly. Use an observed reference color for subsequent matching. Native color access is documented for Track, Scene and Clip.

Partial edits remain after a failure. Inspect their returned observations and read current colors before creating a new plan. A lost reply is never permission to replay. Do not automatically undo over intervening manual edits.

Names remain explicit

rename_session_object separately handles tracks, Returns, scenes and Session clips. Return names use the raw label without Live's automatic bus letter. Each rename needs its own fresh guarded plan and name readback.

Track labels include Groups. For tracks/Groups, Returns and scenes, resolve the current exact ID from list_tracks, get_set_mixer or list_scenes and supply targetType, targetId, explicit name and fresh expectedStateVersion. The updated bridge binds the native object, its collection order and prior label, then rechecks inside the undo step before one name write. A replacement, reorder or intervening rename refuses even at the same state version. The existing trimmed, nonempty name limit remains 255 characters. Return labels omit the displayed bus letter. The plan separates the observed display label from its raw name; no-op detection uses the raw name, while the receipt reports Live's actual display label. Scene tempo and meter are separate native properties; see the Scene API.

These label checks exclude moving recording, automation and playback state. They issue no transport, selection or musical commands and make no write or undo step for a no-op. Inspect writeRequested, nativeReturned, verified, targetRetained, observed, error and observationError separately. The compatibility target descriptor appears only for a verified result. A failed setter or undo finalization can leave a changed label; inspect it before any new plan. There is no automatic rollback or replay. The receipt verifies identity and name, not musical controls, contents, hidden state or file bytes. Independently compare mixer/routing and scene tempo/meter when assessing preservation. A name is not a content backup. For a Session clip, resolve its exact occupied slot through list_clips, then provide targetType: "clip", trackId, targetId, explicit name and fresh expectedStateVersion. The updated bridge binds the native owner, scenes, slots and target clip plus its prior label. It checks them again inside one undo step before a name write. Empty slots, replaced objects, reordered layouts and changed labels refuse. Session clip labels retain the 255-character limit and reject control characters; Unicode and duplicate names are allowed. Lookup is bounded to 256 tracks and 4096 slots/scenes.

Recording length and playback progress are excluded from this label guard. Label edits issue no stop, disarm, freeze, selection or musical commands. A no-op makes no write or undo step. Read writeRequested, nativeReturned, verified, targetRetained, slotPreserved, observed, error and observationError separately. The compatibility target descriptor is returned only for a verified result. A partial write retains the actual observed label without automatic rollback or replay. Read current identity and name after a lost reply before planning remaining work. These checks inspect label context; they do not compare or back up notes, audio settings, hidden content or external files.

Use rename_arrangement_clip for an exact Arrangement MIDI or audio clip from list_arrangement_clips. Supply its trackId, clipId, explicit name and fresh expectedStateVersion. Names may contain Unicode and duplicate existing labels; they must be nonempty, at most 128 characters, and contain no control characters. Resolve the actual track and beat interval rather than guessing from a label. Lookup is bounded to 256 tracks and 4096 Arrangement clips on the target track.

The plan binds native owner and timeline clip objects, the current interval and prior name. Execution rechecks those observations inside the undo step immediately before one Clip.name write. A same-version manual rename, changed interval or replacement invalidates the plan. A no-op makes no write or undo step. Playback and focus continue; the tool requests no note, audio, loop, device, routing or recording change. It does not read or back up complete musical content.

Inspect writeRequested, nativeReturned, verified, targetRetained, intervalPreserved, observed, error and observationError separately. Finalization or readback failure retains the actual name without rollback or replay. After a lost reply, inspect the current exact clip before planning what remains. Preserve intervening manual labels. Organization does not silently move tracks, create Groups, rewrite notes or replace clips to change a label.