Your own chords

Create a package folderCopy Anchor Link

A simple package needs a package.json and a chords folder:

my-chords/
├── package.json
└── chords/
    ├── macos.toml
    └── com/apple/finder/macos.toml

{
  "name": "@your-name/my-chords",
  "type": "module"
}

Add a global chordCopy Anchor Link

Global chords begin with a symbol. Keep them in the package's root chords/macos.toml. The comma prefix is the convention for your own global bindings.

name = 'My Chords'

[chords]
',t' = { name = 'Open Terminal', shell = 'open -a Terminal' }

Load this folder in Settings → Chords → Local Folders. Enter chord mode, type ,t, and release Space to open Terminal.

Shortcut and shell-only packages do not need a JavaScript build step.

Add an app-specific chordCopy Anchor Link

App-specific chord files use the application's bundle ID as a folder path. Finder's bundle ID is com.apple.finder:

name = 'Finder'

[chords]
'fn' = { name = 'New Folder', shortcut = 'cmd+shift+n' }

This binding works when Finder is focused. Keep global bindings in chords/macos.toml; package builds reject them in nested app files.

Name and quote your bindingsCopy Anchor Link

Every chord has a name. Always use single quotes for the sequence key, which also preserves backslashes in special-key notation and patterns.

Use hints to organize related actions:

[chords]
'?f' = { name = 'File' }
'fn' = { name = 'New Folder', shortcut = 'cmd+shift+n' }

The 0 namespace is reserved for Chord's protected built-in commands.

Reload and extendCopy Anchor Link

Run 0,r to reload configuration after editing. If you add TypeScript handlers, build them first; Chord loads js/, not src/.

Continue with creating a package for a complete handler example, or read the scripting API for events and host APIs.