Check the connection before the experiment
Ask Codex to list available NexusTrade tools and read an existing portfolio without updating it. Confirm its name and ID against your NexusTrade account. A tool list proves discovery; the successful read confirms account access. Keep the strategy specification and returned IDs in your workspace for review.
Keep the strategy reviewable
Use Codex to turn a precise trading brief into an explicit portfolio definition in your workspace. Store the rule specification, source notes and assumptions alongside the code so a later change can be compared with the prior candidate.
NexusTrade supplies the tools and engine. Codex supplies the workflow around authoring, reviewing and explaining the returned evidence; it does not create a market edge by itself.
Register the NexusTrade connection
In the desktop app, open Settings, select MCP servers and choose Add server. Name it nexustrade, select Streamable HTTP and paste the NexusTrade server URL from the connection guide. Save, select Restart, then Authenticate for OAuth. In the composer, /mcp shows connected servers. The terminal command below is a separate CLI alternative; run codex mcp login nexustrade after adding the server.
codex mcp add nexustrade --url https://nexustrade.io/api/mcpAsk for a small, checkable change
Codex is useful when the output is a strategy definition and a concrete validation record, rather than a trading recommendation. Keep the initial test bounded and make the baseline part of the brief.
Create a new paper-only candidate from these rules. Show the exact universe, entries, sizing and exits. Keep a research note with the strategy configuration and source links. After I approve the draft, submit one historical test, preserve its operation ID, and explain its warnings. Do not edit or deploy an existing live portfolio.Persist the evidence, not just the conclusion
Keep returned portfolio IDs, backtest IDs, dates and caveats. For a parameter change, compare the same historical window and assumptions before adding an out-of-sample period. Write why a candidate failed as well as why another advanced.
If you later start paper trading, verify that the newly created deployment is paper and record its new deployment ID. A saved draft ID and the running portfolio ID are different.
Check a missing tool or failed account read
If NexusTrade is absent from /mcp, check the saved server URL and restart the connection. If tools are discovered but account access fails, complete authentication and retry a read-only call. In the CLI route, use codex mcp login nexustrade. Check the returned portfolio identity against NexusTrade; do not replace a failed account read with an inferred answer.