Skip to main content

crewship preferences

Manage your own user preferences — small JSON settings the dashboard persists per user (theme, layout toggles, and similar). They are scoped to your account, not the workspace, so no elevated role is required: the endpoints key every row on the user ID from your auth token.
crewship preferences <subcommand> [flags]
Preferences are stored as raw JSON, so set takes a JSON literal — quote strings and booleans. set theme dark is rejected (not valid JSON); set theme '"dark"' is correct.

Subcommands

CommandDescription
listList all your preferences (KEY, VALUE).
setSet a preference key to a JSON value.
deleteDelete a preference key.

crewship preferences list

crewship preferences list
Prints every preference as a KEY / VALUE table (values are the raw JSON as stored). Use -f json for a machine-readable map.

crewship preferences set

crewship preferences set theme '"dark"'
crewship preferences set sidebar '{"collapsed":true}'
crewship preferences set density 3
The value must be valid JSON and is stored verbatim (the CLI does not re-encode it, so true is stored as the boolean true, not the string "true"). Values over 16 KB are rejected by the server.
ArgumentDescription
<key>Preference key (letters, digits, -, _, .).
<json-value>A JSON literal: "dark", true, 3, {"collapsed":true}.

crewship preferences delete

crewship preferences delete theme
crewship preferences delete theme -y   # skip confirmation
FlagTypeDefaultDescription
--yes, -yboolfalseSkip the confirmation prompt.

API

CLIEndpointAuth
preferences listGET /api/v1/me/preferencesany authenticated user (self)
preferences setPUT /api/v1/me/preferences/{key}any authenticated user (self)
preferences deleteDELETE /api/v1/me/preferences/{key}any authenticated user (self)
See also crewship privacy for peer-memory consent and cards, and crewship config for CLI-side (not account) settings.