MarketDeck docs

config

Generic GSettings key access — get / set / list / reset for everything not covered by a dedicated command.

Most marketdeck preferences live in the GSettings schema org.gnome.shell.extensions.marketdeck. The dedicated commands (wallets, agent, telegram, maintenance, …) wrap their own keys; marketdeck config is the escape hatch for everything else.

Usage#

marketdeck config <subcommand> [args]

Subcommands#

Subcommand	What it does
`list`	All keys, with each key's inferred type and current value.
`get <key>`	Single key, parsed into a native value.
`set <key> <value> [--type T]`	Write a key. Type is auto-inferred unless you pin it.
`reset <key>`	Revert a key to the schema default.

Examples#

marketdeck config list --format text
marketdeck config get ai-enhance-provider --format text
marketdeck config set ai-enhance-provider claude
marketdeck config set agent-default-interval 30 --type int
marketdeck config reset ai-enhance-provider

Type inference#

The CLI inspects the schema to pick the right type for a set:

Integer: --type int.
Boolean: --type bool (accepts true/false/1/0).
Double: --type double.
String: --type string (default).
String array: --type strv (comma-separated).

When the schema is unambiguous, the CLI picks the type automatically — --type is only needed for keys whose intended type is ambiguous from the value alone.

What you should not set here#

wallets and agents keys carry compound JSON state managed by the dedicated wallets and agent commands. Editing them via config set bypasses the per-record write helpers and can corrupt the GSettings array. Use:

marketdeck wallets for wallet records.
marketdeck agent for agent records.

Hosts without GSettings#

On non-Linux hosts (or Linux installs without the GNOME schema compiled in), marketdeck config falls back to a JSON file in ~/.config/marketdeck/settings.json. The CLI surface is identical; the GNOME plugin's prefs UI is unavailable there.