MarketDeck docs

notifications

Read the persistent desktop-notification log written by the GNOME plugin.

The GNOME extension fires desktop notifications for trade events and agent reports. Those notifications are flush-on-dismiss in the GNOME Shell tray, so the plugin also writes every one to the notification_log table for recovery. marketdeck notifications is the read surface.

Usage#

marketdeck notifications <subcommand> [flags]

Subcommands#

Subcommand	What it does
`list [--from YYYY-MM-DD] [--kind K[,K…]] [--min-urgency N] [--search STR] [--limit N]`	Newest-first list.
`kinds`	Distinct kinds seen — useful for picking a `--kind` filter.

Flags#

Flag	What it does
`--from YYYY-MM-DD`	Drop entries older than that date.
`--kind K[,K…]`	Comma-separated kinds (`trade-event`, `agent-report`, …).
`--min-urgency N`	`0`=LOW, `1`=NORMAL, `2`=HIGH, `3`=CRITICAL — matches the GNOME `MessageTray.Urgency` enum.
`--search STR`	Full-text scan across title + body.
`--limit N`	Cap the result count.

Examples#

marketdeck notifications kinds --format text
marketdeck notifications list --kind trade-event --from 2026-04-01 --format text
marketdeck notifications list --min-urgency 2 --limit 20 --format text
marketdeck notifications list --search "BTC" --limit 50

Where they live#

The notification_log table holds:

ts, kind, urgency.
title, body.
payload_json — kind-specific fields (coin/direction/price/pnl for trade events, agent + analysis-path for reports). Schema-bumps for new fields land in this column rather than as new columns.

Indexes on ts DESC and (kind, ts DESC) keep the default views to a single index scan.

Pruning#

marketdeck prune notifications --older-than 60

There is no built-in retention cap by default — the GNOME plugin's "Notification History" panel relies on long-term recall for trade event review.