Connect assistant: AI help that reads the connection diagnostic
The Connect assistant is a chat panel on the AI Agents page that reads the last connection diagnostic (broker, route, gateway, system, the six preflight stages) and walks you through what to try next. It never asks for a password and never states a cause as established.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- Sz menu → AI Agents → "Broker access" tab, or the button "Trouble connecting a broker?" on the agent tab; also opened by "I am stuck on this step" in the step-by-step connection guide
- Requires
- Your own AI API key (the key gate appears first when none is saved) and a model chosen in the compact model picker in the panel header
- Context
- The last connection snapshot: broker, route (Rithmic direct or local bridge), environment, system name, gateway, probe symbol, market open/closed, the outcome of the gateway → system → route → auth → subscribe → firstTick stages
- Never sent
- Username, password, API key, account number, balance, positions or P&L — the snapshot type has no field for them
What it does
The Connect assistant lives on the AI Agents page rather than inside the connection modal, so the conversation survives closing a dialog. When you click "I am stuck on this step" in the connection guide, the page switches to the "Broker access" tab and pre-fills the input with the sentence "I cannot connect {broker}. I am stuck at the “{step}” step. Here is what the diagnostic measured:" followed by the plain-text diagnostic.
The same plain-text block is shown above the chat under "What was measured: {system}" with a "Copy the diagnostic" button. It is exactly the text the model receives, so what you paste to your broker and what the assistant reasons about are one and the same. If the diagnostic has never run, the panel says "Run the connection diagnostic" instead and the model is told to ask you to run it first.
Each conversation has its own request identifier prefixed with "connect", so tokens streamed for the market agent never appear in this panel and vice versa. History sent to the model is trimmed to the last 12 turns, and each answer is capped at 2,000 output tokens.
Panel elements
| Element | Default | What it changes |
|---|---|---|
| Model picker (compact) | The model selected on the AI Agents page | Which engine answers; it is shown here so the panel never answers with an unnamed model |
| What was measured (collapsible) | Collapsed | Reveals the diagnostic text as received by the model, with the Copy button |
| Input box | Empty, or the pre-filled stuck-step sentence | Enter sends, Shift+Enter inserts a newline; the send button is disabled while a reply streams |
| ✕ (New conversation) | Hidden until the first turn | Clears the local turns; the diagnostic snapshot is kept |
| Permanent notice | Always shown | "This guide never tells you why a refusal happened. It states what was measured, and lists the possible causes by frequency…" |
How to use it
- Run the connection diagnostic first (Connection preflight). Without it the assistant has nothing measured to read and will say so.
- Open the assistant from the step where you are stuck: the model is told the title of that step and starts there.
- Expect one action per message, followed by how you will know it worked. Do the action, then report the result.
- When the remaining causes are outside the application (unsigned data agreements, no third-party API entitlement, suspended prop-firm account, closed market), the assistant gives you the exact question to ask your broker and suggests opening a problem report.
Limits and pitfalls
- The assistant is instructed to state causes as possibilities ordered by frequency. A refusal worded "permission denied" is explicitly not treated as proof of missing rights: at login it usually means the account is unknown on that system.
- It cannot open, fix or verify the connection itself. The diagnostic decides whether the connection works, not the chat.
- On the local-bridge route (NinjaTrader or Quantower) the six-stage diagnostic does not apply; the model is told so and reasons about the bridge instead.
- Answers are produced with your own API key and billed by your AI provider; nothing is sent when no key is saved.
Related pages
This page in other languages
Frequently asked questions
- Does the assistant see my Rithmic password?
- No. The connection snapshot type has no username or password field, and the system prompt forbids asking for or repeating credentials, account numbers, balances or P&L.
- Why does it keep saying a cause is only possible?
- Because identical refusals on screen have had different causes. The assistant may only say what the diagnostic reports and list likely causes; it is not allowed to declare that your account lacks rights unless the measured result literally says so.
- Can I use it without running the diagnostic?
- You can type, but the model is told nothing has been measured yet and will ask you to run the connection diagnostic first.