Repository navigation
FAQ
Status: active Category: E (product / user) Created: 2026-10-31 Last updated: 2026-10-31 Owner: TCS team
No claim is made, and none should be inferred. The shipped configuration is an engineering baseline, not a strategy that has been validated to make money. Some of the project's own measurements have found losing patterns in its default bots — the point of publishing them is that they are measured rather than assumed away.
Anyone who tells you their trading bot is profitable without showing you the sample size and the period is selling something. This project refuses to do that. See the Financial Disclaimer.
To run the app: no. To trade through it: yes.
Without it you get every page, the database, scoring, backtesting, the Lab and the charts. What you lose is broker bridging — positions, account state and order placement — because those genuinely only exist at a broker. A second route exists for data: 14 provider adapters, several of which need no key at all.
By design. There is no sample or demo data. The project does not ship fabricated numbers to make a first screenshot look full, because a fake number in a trading app is indistinguishable from a real one until it costs someone money.
What you get instead: a setup wizard at /status/setup that reports exactly what is and is not
configured, and provider health on /api/health.
Not unless you configure a bot to. Bots have a mode — auto dispatches on the loop, semi-auto and
manual do not — and a bot with no protocol subscription is never queued at all. That last case is
silent by nature, so there is an audit for it:
npm --prefix nest run audit:bot-activation.
Usually one of: the bot is not subscribed to that protocol; the score did not clear the threshold; a gate refused it; or the broker cannot trade that symbol at that size (a minimum-volume floor is a common blocker). Every one of those is recorded with a reason — the decision trail exists precisely so the answer is a lookup rather than a guess.
Yes, for everything except the bridge. The bridge drives the MetaTrader 5 terminal, which is Windows software. Trade execution is therefore Windows-only today; everything else is not.
It is not built for that yet, and the project says so rather than leaving you to find out. A real-account safety gate — detect a real account, require explicit risk limits and an acknowledgement before automated trading — is in progress (#1153). Until it lands, treat it as a demo-account tool.
Modular Expert Trading Architecture. The scoring approach: instead of one monolithic strategy, a protocol selects a subset of directives, each scoring independently against its own maximum. Protocol-gated scoring is cheaper than scoring every directive for every symbol, and it is why a protocol is a first-class object here rather than a config block.
| Install and run | SETUP.md |
| Counts and versions |
docs/GENERATED-FACTS.md — generated, build-checked |
| Concepts | Glossary · How it works |
| In the app |
/education/glossary — 99 entries, and the page explains the app's own vocabulary |
| API surface |
GET /api/directives, GET /api/scoring/protocols, /api-docs for Swagger |
A reproduction: the command or click path, and what you saw instead. Numbers help enormously — "the score was 71 and the threshold was 75" is fixable; "it did not trade" is not. See Contributing.
It is one person's project with an unusually strict evidence culture: every number in the documentation is either generated and build-checked, or absent. That produces dense files and long comment blocks — and it is also why the same class of bug does not come back six times.
Trading Command Suite · Financial Disclaimer · Installing · FAQ
Source · AGPL-3.0 · Issues · Discussions Built by Ryan Bayne · FifeCIC
💚 Support this project → — free, complete, no premium edition, and no income.
🛑 Not financial advice. The app ships unconfigured and is not set up to make money for you. Test on a demo account before connecting anything real.
v0.162.0 · alpha · © 2026 Ryan Bayne / FifeCIC · AGPL-3.0 · generated from the repository — corrections belong in the repo, not this page.
🛑 Financial Disclaimer — read before connecting an account.
🌐 Website · Screenshots
💚 Support this project — the app is free, complete, and has no income.
Start here
Understand
- How it works
- Glossary
- Scoring architecture
- Risk controls
- How a bot becomes a trade
- Screener contract
- Trading constraints
- Readiness tiers
- Notice codes
Help