Commands  ›  Preferences / Presets  ›  Preferences Save Preset To Local Store

Preferences Save Preset To Local Store

Preferences / Presets writes to model Public API · not yet exposed

Coming soon

Before you run this

One preset selected for export (or the active preset). Local preset store path configured (default %LOCALAPPDATA%\Adelphos\Presets). Preset content valid (passes the project schema).

After it runs

One JSON file written to the local preset store named "{preset_kind}__{preset_id}.json"; existing file with the same id overwritten; audit entry recorded with checksum.

When to use this

Don't use this when

Bulk-exporting every preset (separate routine), syncing to Supabase (use the sync command), or sharing presets across organisations (presets are per-tenant).

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "any" Deterministic config preset

Decision flow

1. Read the selected preset (or the active one).
2. Validate it against the project preset schema for its kind.
3. Write it to "{LOCALAPPDATA}/Adelphos/Presets/{kind}__{id}.json" in one filesystem operation.
4. Record a checksum and timestamp in the audit log.
5. Report the file path and preset id.

What you'll see in the chat

on start
I'll save that preset to your local store now.
thinking
Validating against the schema and writing to the local preset folder.
on success
Done — preset saved to {file_path}.
on failure
Couldn't save the preset locally: {error}.

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/preferences_save_preset_to_local_store
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

save preset · preset export · local preset store · preset backup · plantroom preset save

PillarPreferences / Presets