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.
1. Install and connect NexusTrade
Open Plugins in ChatGPT and search for NexusTrade. Open the plugin details, check that it includes the NexusTrade app, then select the plus button to install. Complete the NexusTrade account connection when prompted. On mobile, your dot's profile → Customize → Plugins opens the shared connection settings.
Your dot can use installed and enabled plugins with the connected account's permissions. An MCP plugin provides account tools; a plugin containing only instructions does not. Check the included app and connection status before asking it to work with your portfolios.
If NexusTrade is not listed in your directory, create a private connection using the next step.
2. Create a private MCP plugin if needed
On ChatGPT web with custom-app access, open Settings → Apps → Advanced Settings and enable developer mode. Authorized workspace users use Settings → Apps → Create; admins can use Workspace settings → Apps → Create. Enter NexusTrade and the endpoint below, choose OAuth, select Scan Tools, complete the NexusTrade sign-in and select Create. Workspace role and action controls determine which tools are available.
To package that connection for your dot, install Plugin Creator from Plugins and start a chat with @plugin-creator. Ask it to create a NexusTrade research plugin using the connected NexusTrade app. Review the included app, finish creation and install the plugin when prompted. Return to your dot and run the read-only check below.
If your account uses Site-hosted plugins, OpenAI also documents creating MCP tools in a Site and installing its associated plugin. Open a Site you own and ask ChatGPT to add MCP tools connected to the NexusTrade endpoint with OAuth. Review the tools, publish the Site as its owner, select Install on the generated plugin card and complete its connection. Verify that its tools read NexusTrade with your account before using it for portfolio work. This is a build route to test, rather than a prebuilt NexusTrade plugin advertised as installed.
NexusTrade MCP URL: https://nexustrade.io/api/mcp
Authentication: OAuth
Initial workflow: list and inspect my owned portfolios using read tools only.3. Prove 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.4. 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.
5. 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.