TL;DR
Enable NexusTrade in your OpenAI dot's cloud plugin settings, then request a dated public filing to check the read workflow. A local Codex task has its own connection and sign-in. Dots can maintain a recurring research brief, while paid tests and portfolio changes require separate review. Pausing a dot also leaves any already deployed NexusTrade portfolio with its own trading state.
Connect OpenAI Dots in the intended environment
- Enable for the dot
- Dot profile → Customize → Plugins → NexusTrade → review account connection. Cloud plugins and a local Codex-host connection are separate.
Create the NexusTrade custom MCP plugin on ChatGPT web if it is not already installed. Use endpoint https://nexustrade.io/api/mcp with OAuth and complete NexusTrade sign-in. Open your dot’s profile → Customize → Plugins, select NexusTrade and complete any requested connection.
Try a public filing read in Dots
Inspect the request
Run the public filing request after connecting. A fresh response may return a later filing; compare its reporting period, filing date and source URL.
Recorded NexusTrade filing reference
NexusTrade MCP sec_edgar returned this listing in Codex on 2026-10-12. Use it as a reference when checking your own connection.
Show the table · 5 rows, 2 columns
| Returned field | Recorded result |
|---|---|
| Company | Apple Inc. |
| Form | 10-Q |
| Filing date | 2026-07-31 |
| Period ended | 2026-06-27 |
| Accession | 0000320193-26-000020 |
No matching rows. Clear the filter to see all records.
Choose a separate next task
These guides are independent choices after the connection check. Review any proposed paid research, historical test or portfolio change before authorizing it.
Give your dot an ongoing research brief
A dot is OpenAI's persistent agent in ChatGPT, with its own cloud computer and browser. Use it to maintain a research brief and return evidence for review. This guide concerns OpenAI Dots, not Dots text-to-speech software.
Dots access depends on plan, region and rollout. Check the official getting-started guide before expecting the profile to appear. A dot is a separate workflow from a regular ChatGPT conversation.
Check the account connection with read tools
Ask your dot to discover the NexusTrade tools, call fetch_portfolios, then call get_portfolio with one ID returned by the first call. Check that the portfolio name, strategies and account match NexusTrade. An empty portfolio list is valid for a new account; in that case, confirm the authenticated read completed without creating anything.
A working connection returns a tool result, including the owned portfolio ID when one exists. A prose answer about a stock or a public web page does not verify account access. If the tool is missing, check the plugin's included app and whether it is enabled in this environment. If OAuth expired, open the reconnect request and repeat the same read. Account or permission errors need connection repair before any changes.
Use the NexusTrade app in my installed plugin. Call fetch_portfolios and inspect one returned portfolio ID with get_portfolio. Show the ID, portfolio name, saved strategies and deployment type from the tool response. If my account has no portfolios, report the empty response. Do not create, edit, backtest, deploy or place orders.Collect the evidence for a research brief
Ask your dot to open public filings, dated news and NexusTrade's public strategy pages. Have it return the issuer, reporting period, publication date and source URL for each claim. It can compare the stated rules and identify missing assumptions without accessing your trading account.
For a website that needs sign-in, open the dot's profile under Computers, then use its browser handoff. Select Take over to complete sign-in yourself and Return control when finished. Its cloud browser has separate sessions from your personal browser.
Research a stock thesis using public sources. Give me the bull case, bear case, dated filings and news, and the assumptions a saved strategy would need. Return source URLs. Do not create a portfolio, run a paid task or place orders.Use a connected local workspace when your task needs it
In the ChatGPT desktop app on your computer, open your dot's profile → Computers → Your computer → Allow access. Review and confirm Allow access. Keep the computer online and the app open while it is in use. Ask your dot to create a local Codex task for the strategy review.
In that local task, configure the desktop MCP connection: Settings → MCP servers → Add server. Name it nexustrade, choose Streamable HTTP and enter https://nexustrade.io/api/mcp. Save, select Restart, then Authenticate for the browser OAuth sign-in. These are local Codex-host settings; they do not configure the dot's cloud computer.
In the resulting task, use /mcp to inspect the connected server, discover its tools and ask for an owned portfolio using fetch_portfolios followed by get_portfolio. Confirm the account and returned ID before allowing any changes. If tools are unavailable, check that you opened the configured local task and completed its OAuth connection. Cloud plugin tools and local Codex-host settings are separate connection paths.
Review rules, then choose the next action
Keep the research brief separate from the saved strategy and any deployment. A historical test evaluates past rule behavior. A paper deployment observes simulated execution going forward. Neither establishes live profitability.
For recurring research, specify the question, sources, cadence and what change deserves an update. In your dot's profile → Customize → Custom rules, choose Ask before taking action for portfolio edits, paid tests and deployment. Keep research updates separate from permission to activate a strategy.
To pause the dot, open its profile → ••• → Pause. This stops the dot's ongoing work. A portfolio already deployed in NexusTrade has its own trading state; inspect and stop that portfolio separately. Pausing a dot does not establish that a trading portfolio stopped.
Choose the task you want to finish
Use the research guide for a dated company brief, the backtest guide for one fixed historical candidate, or the paper guide to observe a separately identified simulated book. Each guide shows how to check the connection, retain the accepted operation ID and recover from a failed request.
Review a brokerage deployment separately
Public and Tradier have native NexusTrade account connection and strategy-port flows described below. Public also offers its own external MCP route. The Robinhood guide uses Claude Code with separate NexusTrade and Robinhood MCP servers; it does not imply that this client already has a verified native Robinhood connection. Broker account selection, order approval and a verified stop remain separate from paper observation.
Optional: check the account before owned-record changes
Optional: verify an owned portfolio before changes
Skip this step if you only want to inspect the public filing in the next step. Before reading or changing an owned portfolio, ask for a read-only list, inspect one returned ID with get_portfolio and compare its name, strategies and deployment type. An authenticated empty list is valid for a new account.
What you should see: For owned records, you have the intended account response or an authenticated empty response. Resolve an account mismatch before saving anything. Public filing inspection does not require an owned-portfolio read.
- Identity boundary
- A server list or public filing read does not verify access to your owned portfolios.
Use only NexusTrade read tools. Call fetch_portfolios, then get_portfolio with one returned portfolio ID. Report the ID, name, strategies and deployment type. If the authenticated list is empty, report that result. Do not create, edit, backtest, deploy or place orders.
No comments yet.