Commands  ›  Preferences / Presets  ›  Preferences Sync Presets With Supabase

Preferences Sync Presets With Supabase

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

Coming soon

Before you run this

Local preset store populated. Tenant signed in to Supabase. Network connectivity to the Supabase project.

After it runs

Local + remote preset stores aligned for this tenant; new presets exchanged in both directions; conflicts listed for manual review with both versions preserved.

When to use this

Don't use this when

One-way export (use the local-save command), cross-tenant sharing (out of scope), or first-time login (presets are pulled at sign-in automatically).

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "any" Deterministic config preset

Decision flow

1. Read every preset on disk + every preset in Supabase for the active tenant.
2. Compare by id + checksum: detect new-local, new-remote, conflicts.
3. Push new-local up + pull new-remote down in one batch.
4. Surface conflicts with both versions for manual resolution; nothing overwritten silently.
5. Report counts pushed / pulled / conflicting.

What you'll see in the chat

on start
I'll sync your presets with the team library now.
thinking
Comparing local + remote presets for the active tenant.
on success
Done — {n_pushed} pushed, {n_pulled} pulled, {n_conflicts} conflicts to review.
on failure
Couldn't sync presets: {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_sync_presets_with_supabase
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

sync presets · Supabase preset library · team presets · preset upload · preset download

PillarPreferences / Presets