Commands

Overview

The command system lets you query your library using a text-based DSL or a visual builder. Results can be piped to actions like backup, tagging, or creating collections.

DSL syntax

select <entity> [where [any] <filter> <filter> ...] [| <action>]

Entities:  plugins, projects, bounces, collections
Operators: : (equals)  ~ (contains)  ^ (starts with)  > (greater than)  < (less than)  ! (not equals)
Actions:   backup, collect "name", tag key:value, export json

Examples

# All VST3 plugins
select plugins where format:vst3

# Master bounces over 1 minute
select bounces where name:~master duration:>60

# Projects using Serum
select projects where plugin:~serum

# Collect mix bounces into a new collection
select bounces where name:~mix | collect "Latest Mixes"

# Tag recent projects
select projects where modified_date:>7d | tag status:active

Filters

Filters use the format field:operatorvalue. Available fields depend on the entity type:

• Plugins: name, format, manufacturer
• Projects: name, format, plugin (plugin used), modified_date
• Bounces: name, format, duration, sample_rate, bpm, key
• Collections: name, status

Visual builder

Toggle the visual builder in the command detail view to construct queries without typing. Select an entity type, add filters with dropdowns, and attach actions. The text representation updates in real time.

Recipes

Save frequently used commands as recipes. Recipes are synced to your account and appear in the Commands sidebar for quick access. Run a command and click "Save as Recipe" to store it.

Piping actions

Use the pipe operator (|) to chain actions after a query:

• backup — Queue matched items for cloud backup
• collect "Name" — Create a new collection with matched items
• tag key:value — Apply a tag to matched items
• export json — Export matched items in the specified format