[ DOCUMENTATION / GLITCH AGENT / ATTACHABLE CONTEXT ]

ATTACHABLE CONTEXT

The agent always sees the whole session, but you can sharpen its focus by attaching specific pieces of the project to a message. Type @ in the chat input to bring up the attachment picker.

// HOW TO ATTACH

Press @ anywhere in a message and a popup lists everything in the current project you can pin: tracks, clips, effects, VST3s, and instruments. Start typing to filter the list, then hit Enter to attach. The reference appears as a chip in your message; you can attach as many as you need before sending.

// WHAT YOU CAN ATTACH

Tracks — Pin a specific track — audio, MIDI, group, or master. The agent gets that track's full state: clips, effect chain, automation, volume, pan, and routing.

Clips — Attach an audio or MIDI clip to focus the conversation on a single region. The agent sees the notes, warp settings, gain, and pitch of that clip.

Effects — Reference a single effect slot on a track's chain. The agent sees the parameters and ordering, so it can suggest tweaks or replacements in context.

VST3 plugins — Pin a hosted VST3 to ask about its preset, parameters, or how it is sitting in the chain.

Instruments — Attach a Sampler, DrumRack, or VST3 instrument to talk about the patch loaded on a MIDI track.

// WHY IT HELPS

The agent already has a picture of the whole project, but attaching context tells it which pieces matter for this message. Instead of “the snare on track 4”, you pin the track and ask “what would tighten this up?”. Instead of describing a plugin chain, you pin the reverb and ask for a darker setting. The conversation stays short and the agent's answers stay specific.

// GOOD USES

Pin two clips and ask the agent to compare their timing, key, or tone.
Pin a track plus a reference VST3 preset on another track and ask for a similar sound.
Pin a full effect chain and ask what is doing the heavy lifting and what could go.
Pin an instrument and a MIDI clip together to talk about whether the patch is right for the part.