The global kill switch on the Risk page stops all accounts at once. Each broker account card also has its own per-account kill switch — useful when you want to pause one account while others continue trading.

The kill switch card is at the top of the Risk page. Click the red Activate Kill Switch button. A red banner appears across all pages. Click Deactivate to resume trading.

After every engine tick, TradeBot scans all open positions. Any position whose unrealized gain equals or exceeds the take-profit threshold triggers an immediate market sell. Stock and crypto accounts each have their own configurable take-profit percentage.

Go to Risk → scroll to the Take-Profit section. Set Stock Take-Profit % and Crypto Take-Profit % separately. Set to 0 to disable.

Fill rate = filled signals ÷ total signals. Below 50% usually means risk guards are blocking most signals. Check Logs and filter by "Blocked" to see which guard triggers most.

Every time a trade executes, TradeBot queues an AI explanation job. The AI reads the signal's reason (indicator values, crossover details, pattern names) and writes a 2–3 sentence explanation in plain English. Explanations appear in the Logs page next to each signal.

TradeBot supports two AI providers: Claude (Anthropic API) and Ollama (local, free, requires Ollama running on your machine). To use Claude, go to AI Tuning → AI Provider Settings, select the Claude (Anthropic) tab, and paste your API key (from console.anthropic.com) into the Anthropic API Key field. The key is encrypted and stored securely — you do not put it in .env.

Every Sunday at 11 PM ET, the auto-tuner analyzes each strategy's live win rate and compares it to the backtest benchmark. It then proposes adjusted parameters (RSI thresholds, EMA periods, notional sizes, etc.) to improve performance. Results are logged in the AI Tuning page.

Use the filter tabs to show All, Filled, Blocked, or Error signals. A strategy producing signals that are all "Blocked" indicates a risk configuration issue. A strategy producing no signals at all means the market conditions don't match the strategy criteria.

Both use incoming webhooks. In Slack: Apps → Incoming Webhooks → Add to Slack → copy the webhook URL. In Discord: Server Settings → Integrations → Webhooks → New Webhook → copy URL. Paste into Settings → Notifications.

Check these in order: (1) Is the strategy enabled for a broker account on the Bots page? (2) Is a risk guard blocking it? Check Logs for "blocked" signals. (3) For stock strategies — is the market open? (4) For crypto strategies — is the Binance account decrypting correctly? Make sure your .env file has DB_SECRET_KEY set. (5) Does the symbol meet the strategy criteria? Use backtesting to verify.

The most common causes: (1) DB_SECRET_KEY not loaded — the app couldn't decrypt your stored API keys. Make sure the key is in your .env file. (2) Demo vs. live key mismatch — paper accounts need keys from demo.binance.com, not live keys. (3) Insufficient balance — Binance requires a minimum of $10 per order. (4) Price in neutral zone — check Logs to confirm the strategy is actually generating signals.

The Pattern Day Trader (PDT) rule limits accounts under $25,000 to 3 day-trades in any rolling 5-business-day period. TradeBot's PDT guard blocks a 4th day-trade automatically. PDT does not apply to crypto (Binance) accounts.

Yes — the server runs continuously. Stock strategies skip order placement outside configured trading hours. Crypto strategies run 24/7 with no market hours restriction.

All data is stored locally in trading.db (SQLite). Nothing is sent to external servers except to your configured broker APIs. Backtest history, signals, settings, and encrypted credentials all live in this single file. Never delete or overwrite this file.

Go to Risk and click Reset next to the Consecutive Losses field. This manually clears the counter so strategies can trade again.

Yes — keys are encrypted with AES-256 (Fernet) before storage. The secret is never returned by any API endpoint. Use Alpaca's "Trading only" scope and disable Binance withdrawal permissions for added safety.

Your API keys are encrypted with the DB_SECRET_KEY stored in your .env file. If that key changes — for example, if .env is replaced, regenerated, or you re-run setup — the app can no longer decrypt your saved credentials, and they show as invalid even though the broker side is fine.

The fix depends on whether you still have the original key:

• If you backed up the original DB_SECRET_KEY: restore that exact value into .env and restart. Your keys decrypt instantly — nothing to re-enter.

• If the original key is lost: go to Broker Accounts and re-enter your API key/secret for each account. They re-encrypt under the current key and work again. Your accounts, settings, and history are all preserved — only the key/secret fields need re-pasting.