Tell us how we could make the product more useful to you.
Completed
Add your own broker server
Right now, if your broker's server isn't already in our list, you have to wait for our team to add it before you can connect that account. We're building it so you can add the server yourself and connect straight away; once it connects successfully, everyone else gets it too, and we can still remove an entry that turns out to be wrong. To start with this will cover DXTrade, DXTrade XT, MatchTrader and TradeLocker. MT4 and MT5 servers will still be added by our team for now.
Help finding your platform credentials
When you connect an account, you have to track down the credentials your trading platform gives you, and every platform keeps them somewhere different. We would like to write a short set of steps for each platform we support, such as MT5 and cTrader, and put them within reach of the connection screen. Nothing here is available yet, and we have not committed to building it. Which platform would you want us to cover first?
Mobile app
We're considering a dedicated Trada app for iPhone and Android, separate from the web app you use in a browser today. Nothing is built yet. What would you use it for first: checking your accounts and copiers, or getting alerts when something needs your attention?
Trader profiles and activity badges
We're exploring an optional public profile that would show your activity — things like days journalled, accounts connected and platforms used — with badges you could earn and share. Nothing here is built yet, and the details may change as we shape the idea. The intent for this profile is activity only: no P&L, no returns, no profit leaderboards. Would you use a page like this, and what would you want it to show?
Prop firm rule profiles
Today you can set drawdown, max loss and max exposure limits on any copier, but you have to enter each firm's numbers by hand. We're looking at firm profiles, so you could pick the firm an account belongs to and have its limits applied without retyping them. Payout terms aren't part of this one. Which of your firm's rules would be most useful to have carried across automatically?
Limit and stop orders
Right now copying and your journal are built around market orders. We're looking at handling limit and stop orders in the same way, so an order that sits waiting on the account you follow can be placed on yours and recorded in your journal alongside your other trades. This one is still under consideration rather than scheduled. Would this change how you trade?
Copier templates and folders
We're looking at letting you save a copier's settings as a template and reuse it, group your copiers into folders, and move a whole setup from one account to another. None of this is built yet. Today the closest thing is duplicating an existing copier and editing the copy, which still takes real time if you run several qualifying funded accounts. Would templates, folders, or both be the bigger help?
Multi-currency support
Today Trada shows balances, protection thresholds and reporting in US dollars, whatever currency your trading account is held in. We're considering showing those figures in your account's own currency instead, so the numbers match the account they came from. This one is still under consideration and nothing is committed yet. If you trade a non-USD account, how much does this affect you?
Trada API
We're considering a documented API over your own Trada data — accounts, copiers, trades and reporting. The idea is that you could pull that data into your own tooling, or connect Trada to systems you already run. Nothing is built yet. If this is something you'd use, what would you want to pull out of Trada first?
Wider alert coverage
Trada alerts you in-app and by email today. We want to widen what those alerts cover to the events you cannot afford to miss while you are away from the dashboard — starting with an account disconnecting — and to give you control over which alerts reach you and when. The new alerts and the controls are not built yet, and the full list of events is still being scoped. Which events would you most want covered first?
Planned
Sign in with Apple
You can already sign in to Trada with Google or Discord. We're adding Sign in with Apple, so you can use your Apple account instead.
Completed
Position reconciliation across copy accounts
Open positions on your connected copy accounts are compared against the source on an ongoing basis, so a position the copy engine can no longer match to the source is closed automatically instead of sitting there skewing your P&L. Positions you opened yourself, outside of copying, are left alone. The work in flight now is tightening that check so it only acts on confirmed evidence of what the source account is actually holding. Comparing fill prices and timestamps, and showing you which account has drifted, are not part of it yet.
Completed
We now check your MT4 and MT5 logins
When you add an MT4 or MT5 account, we now sign in to the platform to confirm your credentials work. The check runs in the background just after you add the account, so it shows as validating for a short while until the result comes back. We're still finishing the part that tells you clearly when a check fails, and we're working through broker servers that aren't covered yet.
Completed
First-run setup
We're working on the first run so signing up leads you through to your first connected account, instead of leaving the setup video to carry it. The setup steps themselves are being improved now, and how much step-by-step guidance comes back on top of that is still being decided. Would a guided walkthrough help you, or would you rather go straight to connecting an account?
Planned
Close a position from Trada
You'll be able to close an open position from inside Trada, without switching to your trading platform. It's meant for the moments when you need out and the platform isn't in front of you. Closing every position at once, on an account or across a copier, isn't part of this work yet.
Planned
Copier start control and Reverse Trading label confuse traders
TLDR Two soft-launch traders couldn't start their copier because the start button only shows its label on hover. One trader mistook the Reverse Trading toggle for the on/off switch — flipping it trades the opposite direction. Neither trader's copier ran until support explained where to click. Done when [code] The start control says what it does without hovering - Check: Copy Trading detail page and list view with a configured, stopped copier - Expect: a control that reads as an action at rest (e.g. "Start copier"), not a status word that changes only on hover [human] The start action is discoverable without hovering - Check: the same page on a touch device - Expect: the action is discoverable and tappable; a hover-only affordance has no equivalent on mobile [code] One state has one name - Check: the detail panel says "Stopped" and the list view says "Paused" for the same state (copy-trading-view.tsx:3094-3107 vs 2675-2691) - Expect: one word, used everywhere, matching the docs, which call it Paused [code] Reverse Trading cannot be mistaken for a power switch - Check: the Reverse Trading column in the receiver table - Expect: it does not render as a bare On/Off next to the start control; label or group it so its meaning is obvious (it inverts buy/sell) [human] A configured but stopped copier tells the trader it is not running - Check: a copier with sender, receivers and mappings all set, left stopped - Expect: the page says trades are not being copied yet and points at the start control Out of scope TRADA-1041 — showing in the UI when reverse trading is switched on (in QA); complementary, not the same fix TRADA-1044 — admin option to hide reverse trading per service TRADA-615 — disabled buttons showing no explanation in copy-trading screens Tech context Both traders are on the soft launch: Jéssica Rodriguês (Featurebase #28) and Johnny Koueik (Featurebase #25) Jéssica's screenshot circles the Reverse Trading column reading "Off" across all three receivers, with the message "como que deixa ON lol" ("how do I turn it ON lol") Support told Johnny in plain words: "The copier must be activated on the Copy Trading page" The control is an InteractiveHoverButton whose label swaps on hover — idle "Active" / "Draft" / "Stopped", hover "Stop" / "Activate" (copy-trading-view.tsx:3094-3107); the list view uses "Active" / "Draft" / "Paused" with hover "Stop" / "Start" (2675-2691) aria-label is already correct ("Activate copier" / "Start copier") — this is a visual affordance problem, not a screen-reader one Reverse Trading is set in the Add/Edit Receiver dialog's Trading tab advanced section as "Reverse positions"; the table column is display-only. Trada blocks it on prop firm accounts, so Jéssica could not actually have enabled it on those three accounts — but she did not know that, and neither will the next trader There is a confirmation dialog for start/stop in the file ("Start Copier?" / "Stop Copier?", 5089-5117) that nothing ever opens — both buttons call toggleCopierState directly. Decide whether to wire it or delete it while in here Gating text already exists and is good ("Connect a sender and receiver account to start", 3110-3114) — the gap is only the enabled state Source Featurebase support conversations #28 (Jéssica Rodriguês, 11 Sep 2026 12:48 UTC) and #25 (Johnny Koueik, 11 Sep 2026). Filed 14 Sep 2026. https://trada.featurebase.app/dashboard/inbox/conversation/28
Planned
New copiers ship unmapped and disabled, so first trades silently fail
TLDR A trader set up a copier, placed a trade, and nothing copied — new copiers need two manual setup steps nobody tells traders about. Support had to walk him through it by hand. Since this is the first thing every new trader does, silent failure makes the worst first impression. Done when [code] A new copier arrives with symbols mapped - Check: create a copier, add a sender and one receiver, open Map Symbols without touching anything - Expect: mappings are already populated (Automap has run for that receiver), not an empty grid [code] A new copier arrives with symbols enabled - Check: the Status column on a freshly created copier - Expect: symbols are enabled by default, so a trader who changes nothing still gets their trades copied [human] Adding a second receiver to an existing copier does the same - Check: add another receiver to a running copier - Expect: its column is mapped and enabled without the trader opening Map Symbols [human] A trader who cannot copy is told why, where they are looking - Check: place a trade on the sender when a symbol is unmapped or disabled - Expect: the copier detail page says so plainly; today the symbol failure banner has no link to Map Symbols (symbol-failure-banner.tsx) [human] The affected customer is told it is fixed - Check: Johnny Koueik, Featurebase #25 - Expect: told, and confirms his copier copies without manual steps Out of scope TRADA-1190 — the FTUK MT5 connection outage from the same conversation (done) TRADA-1095 — Automap on the MT5→MT4 pair specifically TRADA-1213 — Automap not knowing cross-broker aliases like US100/NAS100. Different problem: that is Automap running and finding nothing; this is Automap never running. Tech context Customer: Johnny Koueik (johnny.koueik@gmail.com), FTUK MT5 sender → FTMO demo MT5 receiver The whole diagnosis happened in the ticket. Support: "Did you turn on the copier after setting up the sender and receiver?" … "Could you check the mapping settings and confirm the mapping is correct?" … "Try clicking Automap first" … "Then please scroll down, find these 2 symbols, and make sure the mapping between them is correct." Customer's own summary of the fix: "i clicked on automap" / "and enable all" Automap is manual only — a button on the Map Symbols page that runs client-side with a progress bar (src/app/(authenticated)/copy-trading/[id]/map-symbols/page.tsx:372-395, 399-412). Nothing calls autoMapSymbols() on copier or receiver creation Map Symbols is reachable from one place only: an icon button in the copier detail header, aria-label="Map symbols" (copy-trading-view.tsx:3125-3138). A trader who never opens it never sees the grid Mappings are stored per follower, current_mappings: Record (services/copy-flows/types.ts:355), so every new receiver needs its own pass Worth checking as part of this: whether symbols start disabled by default, or whether they start enabled and something disables them. The customer needed "Enable All", which suggests the former — confirm against the backend before fixing Related guard to respect: page.tsx:157-165 (TRADA-961) refuses to save when the sender's symbol list hasn't loaded, because the payload is a full replacement. Any automatic run must wait for instruments to load or it will wipe mappings Source Featurebase support conversation #25 (customer Johnny Koueik), 10-11 Sep 2026. Filed 14 Sep 2026 at Tim's request. https://trada.featurebase.app/dashbo
Planned
Automap can't match indices when brokers name them differently
TLDR Automap only matches symbols with the same name stripped of decoration, so it can't tell US100 and NAS100 are the same index. Traders must map every index and metal by hand, and a miss fails silently without warning. Support has twice told customers this happens automatically — it doesn't. Done when [code] Automap suggests a match for common cross-broker aliases - Check: an MT5 sender with US100 and a receiver offering NAS100 (also USTEC, NDX, US30/DJ30, GER40/DE40, XAUUSD/GOLD, SPX500/US500) - Expect: Automap proposes the correct instrument [code] Suggested-not-certain matches are distinguishable from exact ones - Check: the Map Symbols grid after Automap - Expect: an alias-based suggestion is visibly marked for review, so we do not trade a wrong instrument in the name of convenience (this is the failure mode TRADA-960 and TRADA-924 are about) [human] Unmatched symbols are obvious before the trader goes live - Check: Map Symbols after Automap when some rows still have no mapping - Expect: the unmapped rows are called out, not just left blank among hundreds of rows [human] Support's answer is corrected - Check: Featurebase #25 (Johnny Koueik) and #28 (Jéssica Rodriguês) - Expect: both told what Automap can and cannot do [human] The affected customer is told it is fixed - Check: Jéssica Rodriguês, Featurebase #28 - Expect: her US100 maps to all three receivers Out of scope TRADA-1095 — Automap failing specifically on the MT5→MT4 pair (in progress) TRADA-960 / TRADA-924 — Automap pairing a symbol with the wrong instrument Whether the bridge retries or falls back server-side when no mapping row exists — unknown, and not in the traders-app repo. Worth confirming separately. Tech context src/app/(authenticated)/copy-trading/[id]/map-symbols/symbol-normalisation.ts:116-145 — autoMapSymbols() tries an exact name match, then a match on normalised forms symbol-normalisation.ts:55-110 — normalizeSymbol() only strips separator-delimited decoration (., /, -, _, #) and a fixed suffix list (PI, PRO, RAW, ECN, STP, MICRO, MINI, CENT, …). It deliberately refuses to strip quote currencies and contract tails There is no alias/synonym table and no fuzzy matching anywhere in the repo. Grepping US100|NAS100|NDX|USTEC across src returns only an unrelated TradingView chart map in the journal (journal/components/constants.ts:65-68) and a static list in src/lib/constants.ts:13 — neither is used by the mapper The current design is deliberate: comments at symbol-normalisation.ts:11-15, 26-28 state a missing suggestion is preferred to a wrong one, with tests at map-symbols/__tests__/symbol-normalisation.test.ts:27-59. So the fix is to add a curated alias table, not to loosen normalisation Zero-match toast already says the right thing (map-symbols/page.tsx:283-285): "Automap found no matching symbols. The receiver may name them differently — map them manually below." The problem is a partial run, where indices silently stay unmapped among many matched FX pairs Consequence of an unmapped symbol: symbol_not_found / symbol_not_available → "The receiver's broker does not offer this symbol — add a symbol mapping" (symbol-failure-banner.tsx:31-32); the copy fails on that receiver, is not retried, and the copier stays Active Note: the Status toggle is not per receiver — disabling a row blocks that symbol on every follower (map-symbols/page.tsx:176-183) Source
In Progress
Browser auto-translation crashes the app for non-English traders
TLDR A Brazilian trader's page crashed while configuring her copier, because Chrome auto-translated the app and broke it. The app has no protection against this, so any trader who doesn't read English risks the same crash. Worse, these crashes go unreported, so we can't see how often it happens. Done when [code] The app is marked as not translatable - Check: src/app/layout.tsx - Expect: the html element carries translate=no (plus a google notranslate meta tag), so Chrome offers no auto-translation and the DOM is left alone [human] The SL & TP tab survives translation - Check: Chrome with Portuguese auto-translate forced on, Copy Trading → Add Receiver → switch to the SL & TP tab, then between all three tabs repeatedly - Expect: no crash, no error boundary [code] Crashes on copy-trading are reported - Check: src/app/(authenticated)/copy-trading/error.tsx - Expect: it calls Sentry.captureException(error) like src/app/error.tsx:16-17 does; today it only calls console.error, so every crash on our most important page is invisible to us [human] Confirm no other route-level error.tsx has the same gap - Check: every error.tsx under src/app - Expect: all report to Sentry [human] The affected customer is told it is fixed - Check: Jéssica Rodriguês, Featurebase #28 - Expect: told it is fixed and can open the SL & TP tab Out of scope Translating the product into Portuguese (no i18n library exists — separate decision) The broker dropdown that closes on open, TRADA-1168 (Featurebase #23) — likely the same root cause; re-test it once this lands before doing more work there Tech context Customer: Jéssica Rodriguês, MT5, FTMO sender + FXIFY / FTMO-Demo / BlueGuardian receivers. Screenshot shows the whole UI in Portuguese with tabs rendered "Negociação / SL e TP / Proteção" — the real labels are "Trading / SL & TP / Protection" (copy-trading-view.tsx:4152-4156) Exact error shown: "Falha ao executar 'removeChild' em 'Node': O nó a ser removido não é filho deste nó" Root cause: the translator rewrites text nodes, React can no longer reconcile them, and the error boundary fires The app is English-only — no i18n library in package.json, no locale files, all strings hardcoded (src/app/error.tsx:21). So a Portuguese UI can only be the browser translating Conditions that make the crash likely: Radix Tabs with no forceMount, so inactive TabsContent fully unmounts and remounts on every tab switch (src/components/ui/tabs.tsx); the modal renders through a portal onto document.body (src/components/ui/dialog.tsx:58); and inline conditional text nodes as siblings in one parent (copy-trading-view.tsx:4596-4600, 4685-4689, same pattern at 4176-4178) No notranslate attribute, translate="no" attribute, or google notranslate meta tag anywhere in the repo — verified by grep across src, public, next.config.ts and src/app/layout.tsx Not yet reproduced in-house: the code shape and the customer's evidence point clearly at translation, but nobody has run the repro above. Do that first. Source Featurebase support conversation #28 (customer Jéssica Rodriguês), messages of 11 Sep 2026 12:27 UTC. Filed 14 Sep 2026. https://trada.featurebase.app/dashboard/inbox/conversation/28
In Progress
Futures Terminals
We're planning copy trading on the futures terminals — NinjaTrader, Rithmic and DXFeed. None of it is available yet: connecting a futures account, journalling your trades from it and copying between futures terminals are all still to be built. We'll post an update here as soon as the first connector is ready.