> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gridshift.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Cases

> Producer workflows an assistant runs in Gridshift, each with a prompt to start from and the tools it uses. Say what you want in musical terms; the assistant works it out step by step and you watch it happen in the window.

## Build an arrangement and read it back

> *"Start a 124 BPM house track in A minor: drums, bass, chords and a pad, the drums in a group, an 8-bar intro and a 16-bar drop with markers. Loop the drop."*

The assistant sets key, scale and tempo, adds and colors the tracks and the group, places drum patterns and samples, writes the bass and chord MIDI, marks the sections and sets the loop. It then reads the whole arrangement back with `get_session_overview` to check its work.

<video src="/videos/assistants-build-arrangement.mp4" poster="/videos/assistants-build-arrangement.jpg" aria-label="ChatGPT builds an 8-bar house beat in a new project: tracks fill with clips and the loop plays" title="ChatGPT builds an 8-bar house beat in a new project: tracks fill with clips and the loop plays" muted loop playsInline preload="none" />

A shorter request builds too: *"In Gridshift, start a new project and build an 8-bar house beat at 124 BPM."* It takes a few minutes; the clip runs faster.

## Tidy and color the tracks

> *"Name the tracks after what they play, color the drums red and the synths blue, group the drums and fold the group shut. Delete the empty tracks."*

The assistant reads the tracks and their clips, renames them, sets the colors, groups the drums and collapses the group with `track_configure`, and deletes the empty tracks with `track_manage`. `⌘Z` takes the changes back one tool call at a time.

## Make the kick duck the bass

> *"Make the kick duck the bass, only below 120 Hz, and start the dip a 1/16 early."*

The assistant sets up [ducking](/mix/ducking.md) with `ducking_configure`: the kick's notes and clip starts trigger it, the bass is the target, the range is set to the lows and the lookahead to 1/16. Ask for a compressor instead and it routes a [sidechain](/mix/sidechain.md) with `plugin_configure`.

<video src="/videos/assistants-duck-kick-bass.mp4" poster="/videos/assistants-duck-kick-bass.jpg" aria-label="Asked to make the kick duck the bass, ChatGPT adds ducking to the Reese bass track and Kick Ninja appears in its Ducking section" title="Asked to make the kick duck the bass, ChatGPT adds ducking to the Reese bass track and Kick Ninja appears in its Ducking section" muted loop playsInline preload="none" />

Ask *"Make the kick duck the bass in Gridshift."* The bass track gets a **Ducking** section driven by the kick.

## Check the mix against a reference

> *"Compare the drop with Reference.wav. What is different, and what fights in the low end?"*

The assistant measures the loop region with `analyze_mix`, giving the file as `reference`, and reports the differences in loudness, peak, band balance and width, plus the tracks that compete in the same band. It adjusts faders, EQ or the clipper, then measures again. With a collection of finished tracks instead of one file, `style_profile` gives target ranges to mix toward.

## Sort samples into a collection

> *"Find my dark, punchy kicks, put them in a new collection called Dark Kicks and tag them dark."*

The assistant finds the kicks by sound with `sample_search` (this needs [Smart Search](/library/smart-search.md)), then creates the collection, files the kicks and adds the tag with `library_organize`. The collection appears in the library window and syncs to your other devices.

## Ask how a feature works

> *"How do I unlink one copy of a linked clip?"*

The assistant searches these docs with `docs_search`, reads the matching page with `docs_read`, and answers with the steps and keys from it. It can then do the steps for you.

## Good to know

* **Name the musical goal, not the tool.** *"Make the chorus hit harder"* works; the assistant chooses between faders, the clipper and a compressor and says what it changed.
* **Ask it to measure, change and measure again.** A mix change is only checked once `analyze_mix` runs a second time.
* **Library sorting cannot be undone with `⌘Z`.** Collections, tags and renames in the Sample Library behave as they do by hand; [What Assistants Can Do](/assistants/capabilities.md) lists what asks you first.
* **A later chat can pick up where this one stopped.** Ask it to read the project back first; `get_session_overview` with `clips` gives it the whole arrangement.

> **Writing a whole project**
>
> * The tools come in two halves. The mixer, plugin, send and ducking tools nudge a project you have open and are listening to. The rest (placing clips as windows into a file, `clip_configure`, `marker_configure`, `project_configure`, `group_create`) build a project from nothing.
> * `transport_control` sits on both sides: it drives playback while you listen, and it builds, with `set_tempo` before anything is placed and `set_loop` once there is something to loop over.
> * The audio window makes building work. A real arrangement is a long stem cut into sections, each clip reading the part of the file that belongs where it sits. Setting `source_offset_beats` equal to a clip's `start_beat` reproduces that cut, so every section stays in sync with the song.
> * A workable build order: key and scale with `project_configure`, tempo with `transport_control`; tracks and groups; colors; audio; MIDI parts and automation; sends; section markers; the loop region.
> * Finish by measuring with `analyze_mix` and reading the result back with `get_session_overview`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.