Notifications
12 settings on this page.
Notifications Overview
What it does
ACondor can push alerts to your phone for the three events worth interrupting you for: a new position filled, a position closed, and a trading halt. Two independent channels are available, each with its own master switch and per-event toggles. One channel being off or misconfigured never affects the other. Pushover (recommended). Push notifications through the Pushover app. This is the primary channel because it stays free at any message volume: each user registers their own free Pushover application, so you never draw on a shared quota. Pushover pools message quotas per developer account, which is exactly why ACondor does not ship a shared token. The only cost is the Pushover app itself on the device that should receive alerts: free 30-day trial, then a one-time $4.99 purchase per platform (iOS, Android, or desktop). Configure it with these settings: /docs/pushover-api-token (your own application's token, from pushover.net/apps/build) /docs/pushover-user-key (your personal key, from pushover.net) /docs/pushover-on-entry, /docs/pushover-on-exit, /docs/pushover-on-halt (per-event toggles) /docs/pushover-priority (delivery priority, -2 to 2) The pushover_enabled master switch in the dashboard turns the channel on once both credentials are saved. Both the API token and user key are stored in the bot's settings database only and are write-only: the dashboard shows whether they are configured, never the values. Twilio SMS. Text-message alerts remain available as an alternative (see /docs/sms-enabled). Today the Twilio credentials (account SID, auth token, sender number) are configured server-side through environment variables, not per-user in the dashboard; only the destination number and the per-event toggles live in settings.
Example
Verify your setup before relying on it live: in the dashboard open Settings, Notifications, save your Pushover API token and user key, then click the send test push button. The test deliberately works even while pushover_enabled is still OFF, so you can confirm delivery before switching the channel on. A test push should arrive on your device within seconds; if the dashboard reports the send failed, re-check the token and user key.
SMS Enabled
What it does
Master toggle for SMS notifications via Twilio. When ON, ACondor sends text messages on fills, closes, and circuit breaker halts. Requires sms_to_number and valid Twilio credentials configured in environment variables (TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_FROM_NUMBER).
When to change it
Turn ON once you have Twilio configured and want real-time alerts without watching the dashboard.
Safe range
ON or OFF.
Example
Bot enters an iron condor on SPY. With sms_enabled=ON and sms_on_entry=ON: "ENTRY: SPY iron condor 480/485/520/525 exp Jul 18 filled at $1.52 credit."
SMS Destination Number
What it does
Phone number that receives ACondor SMS notifications. Must be in E.164 format (+1XXXXXXXXXX for US numbers). This is the destination number; the Twilio sender number is configured in environment variables.
When to change it
Set once when configuring Twilio. Update if your phone number changes.
Safe range
Any valid E.164 phone number.
Example
+15055551234 for a New Mexico number.
SMS On Entry
What it does
Send an SMS whenever a new position is filled. Message includes the underlying, structure, strikes, expiration, and credit received.
When to change it
Turn ON when you want real-time fill confirmations while running the bot unattended.
Safe range
ON or OFF.
Example
Bot fills NVDA iron condor. SMS: "ENTRY: NVDA IC 110/115/135/140 Jul 18 filled $1.38 credit."
SMS On Exit
What it does
Send an SMS whenever a position is closed. Message includes the underlying, exit rule, P&L, and credit captured.
When to change it
Turn ON to receive exit confirmations without watching the dashboard.
Safe range
ON or OFF.
Example
Iron condor closes at 50% profit. SMS: "EXIT: SPY IC closed profit_target +$76 (50% of $152 credit)."
SMS On Halt
What it does
Send an SMS whenever a circuit breaker fires (VIX kill switch, daily loss limit, weekly loss limit, risk-off halt). Critical for knowing when the bot has stopped entering without checking the dashboard.
When to change it
Turn ON when trading live. Knowing the bot has halted is more important than fill confirmations.
Safe range
ON or OFF.
Example
VIX spikes to 36. SMS: "HALT: VIX kill switch fired (36.2 > 35). No new entries until tomorrow."
Pushover API Token
What it does
The API token of your own Pushover application. This is a per-user credential, not a shared ACondor key: create a free account at pushover.net, then register your own application at https://pushover.net/apps/build (any name works) and paste its API token here. Pushover pools free message quotas per developer account, so each user running their own application is what keeps the channel free at any usage level. The token is stored in the bot's settings database only (there is no environment-variable path) and is write-only: once saved, the dashboard shows only whether a token is configured, never the value.
When to change it
Set once during setup. Replace it only if you delete and re-create your Pushover application, or if you believe the token was exposed.
Safe range
Any valid Pushover application API token (a 30-character string from pushover.net/apps/build).
Example
Register an application named ACondor at pushover.net/apps/build, copy its API token (it looks like azGDORePK8gMaC0QOYAMyEEuzJnyUi), paste it into the dashboard's Settings, Notifications section, then pair it with your user key and send a test push.
Pushover User Key
What it does
Your personal Pushover user key, shown on your https://pushover.net dashboard after you log in. The user key identifies which device(s) receive the pushes; the API token (see /docs/pushover-api-token) identifies the sending application. It is distinct from the token and both are required before the channel can send anything. Like the token, it is stored write-only in the settings database: the dashboard shows only whether a key is configured, never the value.
When to change it
Set once during setup. It only changes if you reset your user key on pushover.net.
Safe range
Any valid Pushover user key (a 30-character string from your pushover.net dashboard).
Example
uQiRzpo4DXghDmr9QzzfQu27cmVRsG: pushes arrive on every device registered to your Pushover account. You can limit delivery to specific devices from inside the Pushover app.
Pushover On Entry
What it does
Send a push notification when a new position is opened. The alert fires after the fill is booked and the position is recorded as OPEN in the database, and includes the engine, underlying, structure, credit received, and DTE. Independent of the SMS on-entry toggle: each channel checks its own flags. Only takes effect while pushover_enabled is ON with valid credentials saved.
When to change it
Leave ON for real-time fill confirmations while the bot runs unattended. Turn OFF if you only care about halts and want less phone noise.
Safe range
ON or OFF.
Example
Bot fills an SPY iron condor. A push titled "Trade entry" arrives: "[BOT] FILL ...1234: mechanical SPY iron_condor +$1.52 38DTE".
Pushover On Exit
What it does
Send a push notification when a position is closed. Covers every exit path: profit target, DTE management, delta defense, news gate, expiry flatten, and assignment cleanup. The alert includes the underlying, the exit rule that triggered, the realized P/L, and the engine. Independent of the SMS on-exit toggle. Only takes effect while pushover_enabled is ON with valid credentials saved.
When to change it
Leave ON to receive exit confirmations without watching the dashboard.
Safe range
ON or OFF.
Example
Iron condor hits its 50% profit target. A push titled "Trade exit" arrives: "[BOT] EXIT ...1234: SPY profit_target P/L +$76.00 [mechanical]".
Pushover On Halt
What it does
Send a push notification when a circuit breaker fires and halts new entries (VIX halt, macro halt, daily-loss halt, weekly-loss halt), plus operational alerts such as a half-rolled position or a streamer error. Halt alerts are deduplicated per account and halt reason per UTC calendar day, so an active halt does not re-notify on every cycle. The dedup date is only recorded when at least one channel actually sends, so switching Pushover on later the same day still gets you the alert.
When to change it
Leave ON when trading live. Knowing the bot has stopped entering matters more than fill confirmations.
Safe range
ON or OFF.
Example
VIX spikes above the kill switch. A push titled "Trading halted" arrives once: "[BOT] HALT ...1234: vix_halt (vix=36.2)". The same halt stays quiet for the rest of the day even though it remains active.
Pushover Priority
What it does
Pushover message priority on the standard -2 to 2 scale, applied to every event this channel sends. -2 (Lowest) is silent: no sound, vibration, or banner. -1 (Low) delivers quietly. 0 (Normal) is a standard push. 1 (High) bypasses your phone's quiet hours. 2 (Emergency) requires acknowledgment and repeats until you dismiss it; ACondor automatically adds the retry and expire parameters the Pushover API requires for emergency priority (retry every 60 seconds, stop after 1 hour). Values outside -2 to 2 are clamped into range.
When to change it
Leave at 0 for normal delivery. Raise to 1 if alerts must break through Do Not Disturb. Emergency (2) suits a drop-everything view of halts, but remember it applies to routine entry and exit pushes too, which gets aggressive fast.
Safe range
-2 to 2. Out-of-range values are clamped.
Example
Set to 1: fill and halt pushes bypass quiet hours. Set to 2: every push repeats every 60 seconds for up to an hour until acknowledged, including routine entry fills, which is why 0 or 1 is the sensible day-to-day setting.