Choose who will run the strategy
For NexusTrade-managed strategy evaluation, use the native Public account connection and Port to Live workflow below. For direct brokerage tools in an AI client, connect Public's own MCP separately. Connecting two servers does not automatically synchronize strategies or create a persistent executor.
Start with a saved, tested candidate
Write explicit entry, sizing and exit rules, then save the strategy. Fix the historical test period, capital and benchmark before running it. Review warnings and individual orders as well as the return curve.
Use a separately identified NexusTrade paper deployment to observe simulated operation before brokerage deployment. Retain the original saved candidate ID, backtest ID and deployed paper ID. A backtest curve is not paper history, and paper results are not live fills.
Connect your Public account in NexusTrade
Open /live-trading/public and select Connect Public. Choose Connect my existing account, review and accept the disclosure, then select Connect Public to complete the broker authorization in its sign-in flow. NexusTrade checks the stored connection and returns account requirements; complete any requirements shown before proceeding. Do not paste broker credentials into an agent conversation.
Account connection identifies a broker account; it does not prove that the candidate strategy is deployed or that an order has filled.
Review Port to Live before confirming
Open the paper portfolio's Deployment Center and select Port to Live. Choose Public and inspect the confirmation. The port copies strategies into the live brokerage portfolio and preserves the paper source. Existing active live strategies can be disabled by the port; review the displayed conflict list.
Confirm & Port can activate the live target. Treat it as a real deployment action, not a preview. The server validates strategy eligibility and returns livePortfolioId, disabledCount and addedCount. Unsupported short strategies are rejected; options also require the account's applicable access.
If authorization or porting fails
If the account screen asks to refresh authorization, select Continue to Public and complete the broker sign-in again. Return to NexusTrade and check that the connection is ready before reopening Port to Live.
If the port returns you to the broker picker, the server did not find a connected brokerage. Reconnect the account and review the target again. For another error, read the displayed message and inspect the live target before retrying. A missing confirmation is not proof that the copy failed; check its strategies and active state to avoid repeating a deployment blindly.
Check automated trading and order approvals
Read the live portfolio's trading policy and follow the account application or portfolio-settings action it provides. Automated trading and its daily limit can only be changed by you in the NexusTrade UI. Aurora and MCP do not enable this policy, and account approval alone does not switch it on.
For manual review, inspect proposed orders before approving them. NexusTrade's create_orders tool stages live orders unapproved and does not submit them to the broker. Paper orders use a separate simulation path; a submitted or accepted order is not proof of a fill.
Verify the live target and know how to pause
Open the returned livePortfolioId and check its Public identity, strategies, active state and trading policy. Review orders and portfolio events against broker account activity. Use the exact live ID for get_portfolio, get_portfolio_policy, list_orders and query_portfolio_events when inspecting through MCP.
To pause NexusTrade strategy evaluation, switch Automated Trading off in the Deployment Center and select Save Changes. Verify the active state on that same live portfolio. Review outstanding broker orders and holdings separately; pausing strategy evaluation does not mean an existing position has been sold or every open order canceled.
Public MCP: connect a separate brokerage tool
Public documents https://mcp.public.com/mcp. In Claude, use Settings → Connectors → Add custom connector, enter that URL, then Connect and complete the browser authorization. Its Claude Code instructions start from that authenticated connector and use /mcp to select Public MCP.
Keep NexusTrade connected for research and historical tests. Discover Public's current tools and first read the connected accounts, buying power and positions. Prepare an order proposal from the reviewed strategy only after choosing the target account. Check broker order state after an approved submission.
NexusTrade paper simulation and Public MCP order submission run separately. Direct MCP execution needs an explicitly configured agent or workflow with its own cadence and approval controls. Stop that executor separately from a native NexusTrade portfolio.