Scripts and data files

The zero-code tier. A palette can be a data file (json, jsonl or toml) or a shell script that prints JSON lines, described by a small TOML table. No TypeScript. The extension reads those tables from a pal v1 style config file and turns each [palette.<name>] into a palette named after its table, with the config id scripts-<name>. The full format is in docs/scripts.md; this is the short version.

A data-file palette

[palette.links]
auto_list = true
data = "links.json"       # relative to the config file's directory
icon_utf = "🔗"
actions = [
  { id = "open", title = "Open", action = "open", key = "url", primary = true },
  { id = "copy", title = "Copy link", action = "copy", key = "url", shortcut = "cmd+c" },
]

links.json is a JSON array (or one object per line, or a TOML file whose first top-level array is the rows). Every row is an item: name is the title, id defaults to name; subtitle, keywords, section, url (a favicon when there is no icon), accessories, detail and icon_utf are what they say. The table's actions apply to every row. Without actions, auto_pick = true with default_action (copy, open, cmd, type) and action_key gives one built-in action.

A script palette

[palette.hosts]
base = "plugins/hosts"    # the directory holding run.sh
requires = ["awk"]        # skipped when the binary is missing
ttl = 3600                # reuse a listing for an hour

run.sh list prints one JSON object per line (the row fields above, plus preview, a shell command whose stdout becomes the detail pane's markdown, run lazily). run.sh pick gets the picked row as JSON on stdin and every field as PAL_<KEY> in the environment (PAL_ID, PAL_NAME, PAL_ACTION, PAL_FILTER), and prints a result envelope: clipboard, open, toast, hud, show (a read-only level), palette (drill into another script palette with env), reload. No envelope hides the panel.

Table keys: input (list on every keystroke, the query on stdin and in PAL_QUERY), input_prompt, live (list on every show), ttl, view = "grid", display = { detail = true, columns = 8 }, filter (a scope dropdown, the id in PAL_FILTER), requires, os, command (instead of run.sh). A plugin.toml in base may carry the same keys. base may also be github:<user>/<repo>/<path> from v1's plugin cache.

Keyboard

What a row does is the table's: the first action (or the primary one) runs on enter, the second on cmd+enter, every action from cmd+k with the shortcut it declares. With no actions at all a script palette's row is Select, which runs run.sh pick.

Setup

Point config at the file that holds the tables. The default is pal's own config file; pal's parser flags a palette table as an unknown key (the palettes still work), so a file of their own keeps the warning away:

[extensions.scripts]
config = "~/.config/pal/scripts.toml"

Relative paths inside that file (data, base, [general] env_file) are resolved against its directory; ~ is expanded. Scripts get the app's PATH plus ~/.local/bin, ~/.cargo/bin, /opt/homebrew/bin and /usr/local/bin. A type action pastes into the app in front, which needs Accessibility on macOS (wtype or ydotool on Linux).

Settings, [extensions.scripts]:

config, skip, v1_repo and ttl are read when the extension loads; after changing them, Settings > Restart extension host. timeout and preview_max apply to the next run.

What it does not do

• v1's builtin/... bases: no equivalent, one inert row says so.
• Raycast icon names (icon_rc): dropped; use icon_utf, icon or icon_xdg.
• Metadata separators in detail: no equivalent, left out.
• Run a list or pick past timeout: it is killed with its process group and counts as failed.
• Watch the config: a new table shows after Restart extension host.

Platforms

macOS and Linux. A table with os = "macos" or "linux" is skipped elsewhere; requires gates on binaries on PATH the same way on both.