OVERRIDES runtime profile: uses no model — pure shell. Marked claude_anthropic because scheduler enforces a known-good profile sentinel; nothing in this script calls a model.
Ensures the dedicated Trading tmux window (target for crypto-trader bot
approval messages, swing council output, and trading dev work) exists with
claude running inside.
If the window is missing, recreate it. Per Elmar (2026-05-09): "If something happens to it, you just re-create it — not a train smash if we lose history."
The recreated window will get a new tmux pane id; ccgram detects it on its
next session-list refresh because the window_name is preserved as
"Trading". Crypto-trader topic (id 14010 in ccgram, "crypto-trader" alias in
notify.py) routes to whichever window is currently named Trading.
/home/lucienne/workspace/scripts/trading_session_watchdog.sh
Format: minute hour day month weekday
| Started | Status | Duration | Log |
|---|---|---|---|
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
| 1d ago | completed | 0s | View log |
Mission Control is the board for your delegated work: requests come in, Luci coordinates the next step, and evidence stays visible for review.
Luci is your always-on assistant for routing, status updates, and follow-through. Operators can still open deeper evidence when needed.