System requirements
ADT Desktop is built for Mac and Windows. Mac: Apple silicon, macOS 13 or later. Windows: Intel/AMD x64. You need IB Gateway or Trader Workstation, a suitable IBKR account, relevant trading and market-data permissions, research-provider access and a reliable internet connection.
The Windows testing installer includes its runtime and dependencies. Native installation, background-task behavior and the complete paper broker lifecycle still require validation on the target Windows machine. Windows ARM and Intel Mac are not validated targets. Guided access confirms the appropriate release for your computer before purchase.
Maintain the computer, broker session and power settings for the full trading session. A background service can keep running after you close the app window; it cannot trade while the machine is off.
Installation and first run
Request access for distribution and onboarding details. Public self-service downloads and commercial licensing are not currently available. The development build is ad-hoc signed; it is not presented as an Apple-notarized public release.
On Windows, extract the supplied testing ZIP completely and run Install.cmd. Setup verifies its payload and runs isolated local checks before creating shortcuts. Start with a fresh paper profile, then validate the gateway, background service and full paper workflow. Keep the computer plugged in; explicit sleep, lid closure, logout or power loss can interrupt operation. The testing installer is unsigned.
The setup assistant covers the research provider, broker connection, capabilities, trade notional and readiness. Do not enable live operation as a way to test an installation.
For ports, permissions and troubleshooting, use the complete IBKR connection guide.
Connect IB Gateway or TWS
- Sign in to your intended paper account inside IB Gateway or TWS. The trading application does not collect broker login credentials.
- Enable API socket clients and localhost access. Select the configured paper API port: commonly 4002 for IB Gateway or 7497 for TWS. Confirm your actual broker configuration.
- For order operation, disable the broker’s read-only API setting. Keep localhost restrictions enabled.
- In Settings → IBKR, enter the local host and port, then test the connection. Confirm the displayed account mode.
- Review capability and market-data results. A connection alone is not confirmation that orders or data subscriptions are permitted.
Configure the session envelope
In Settings → Trading, save maximum entries, simultaneous positions, position size, open capital and total session allocation together. The total session allocation counts cumulative purchases; closing a trade does not replenish it. Whole shares are required.
Expand Research and risk details to set qualified reserves, the supported universe, permitted symbols and an optional observed-loss exit threshold. The threshold uses available realized and quoted unrealized values; it cannot guarantee a maximum loss. Contradictory limits are rejected rather than silently rewritten.
Research receives the saved envelope before ranking. A $10 whole-share cap filters out candidates that cannot fit one share plus the configured entry buffer. A quote crossing above the cap is checked again before submission; ADT can move to a qualified reserve.
Once research starts, that session uses its persisted configuration. Settings changes apply to a future session. Existing one-entry settings migrate without expanding live risk. Use recommended intentionally applies a versioned provisional protection preset and preserves account authorization and session limits. See protection values and evidence.
Verified operating limits
Configuration permits up to 100 maximum entries and 100 configured simultaneous positions. Software scenarios exercise 1, 5, 10, 25, 50 and 100 lifecycles. These are simulation results, not an IBKR paper or live scale certification.
The default IBKR adapter has an 80-subscription quote budget and reserves four slots for entry validation, so its effective managed-lifecycle ceiling is 76. Actual account/data capacity and the entry window can reduce participation further. The dashboard shows the effective limit. Broker requests are paced with reserved safety capacity; a large configured number is never a promise of fills.
Configure research
In Settings → Research, select a supported provider and model. Hosted providers use your own API account; local endpoints may not require a key. Test the provider separately from the fresh-source setup. Keys are stored in the operating system’s credential store.
OpenAI and Anthropic adapters use native web search. For a suitable compatible or local model, choose Free news for keyless GDELT headline discovery. An optional organization/contact user agent enables SEC filing context. Public feeds can be unavailable and have incomplete coverage; missing fresh evidence produces No Trade. Observation time is identified separately from publication time. Tavily and Brave remain paid alternatives. News does not replace broker prices, spread or liquidity checks.
Preliminary and final times are configured in Settings → Schedule. The defaults are 07:00 and 08:00 America/Chicago on trading days.
Rehearse in a paper account
Confirm PAPER mode and review the entire envelope. Start with one position, then rehearse your intended concurrency. Inspect constrained candidates, reserve fallback, current sizing, entry and partial-fill states, independent protection, automatic exits and broker-confirmed flat for every lifecycle. Practice checking actual orders directly in the broker software.
Paper execution differs from real markets. A successful rehearsal demonstrates setup and workflow, not strategy profitability or future live fills.
Authorize live trading deliberately
Live trading is disabled by default. In Settings → Trading, a separate confirmation binds authorization to the exact broker account. Merely connecting to a live account does not enable live entry.
Review your trading amount, strategy settings, market-data mode, risk disclosure and recovery procedure first. Changing accounts requires matching authorization. Red live-account styling remains visible during operation.
Read the current session
- Readiness: research, broker, data, candidate qualification and trading authorization.
- Positions: independent quantity, entry, high-water, protection and exit state; the session ledger summarizes candidates, entries, skips and completion.
- Authority: broker stop versus app-monitored protection; accepted broker orders matter.
- Schedule: session state, next action and countdown based on the exchange calendar.
- Activity: state changes, order events and warnings.
A delayed quote is labeled. App-side stop ratchets using delayed data also lag. Use the broker application to verify a position whenever state is uncertain.
Recovery and intervention
Broker disconnected
Restore the gateway login and connection. The service reconnects with backoff and reconciles before resuming. Check the actual position and accepted protective orders in IBKR. App-monitored protection requires the service to be available.
Stop a new entry
Use Pause new entries or Disarm to prevent new session entries and cancel pending entry orders; existing exposure remains managed. Disarming is different from closing an existing position. Confirm whether an entry order is already working.
Automatic exits and manual overrides
The engine initiates configured protective, session and enabled observed-loss exits automatically. Normal operation does not require clicking Sell or Flatten. Flatten Position overrides one lifecycle; Flatten All and Emergency Stop disarm new entries and request managed exits. Each uses the same reconciliation path until broker-confirmed flat. Unrelated holdings are outside the managed flatten request.
Blocked or unresolved state
Read the alert’s specific reason. Resolve the underlying broker, data or position issue, then use Resolve to request reconciliation. An exit loop can continue retrying while an exposed position remains. Escalate directly in the broker software when needed.
After a service interruption
Restarting restores all managed lifecycle records, including protection peaks and exit state, and requests broker reconciliation. Do not delete the database or reset the application while there may be a position or working orders.
Local data and reports
The existing storage identifiers remain stable for compatibility. macOS stores application data under ~/Library/Application Support/DayTrader and logs under ~/Library/Logs/DayTrader. Reports use ~/Documents/Day Trader Reports. Windows stores private data and logs under %LOCALAPPDATA%\DayTrader, with the program under %LOCALAPPDATA%\Programs\DayTrader. Each computer has its own profile; installation does not transfer broker accounts, credentials or live authorization from another machine.
Use Settings → Advanced to export a session report or diagnostics. Review exported files before sharing; do not send credentials or private brokerage documents through the website inquiry form.
Updates and releases
There is currently no automatic update system. Updates require a supplied build or a rebuild from source. Prefer maintenance outside market hours after verifying exposure and protection directly at the broker. Follow the version-specific release instructions.
Need help with availability or your environment? Contact Automatic Day Trader.