← portfolio

My most advanced AI project

Claude NY.

An AI agent that runs a trading research lab around the clock: it turns ideas into MetaTrader 5 strategies, tests every one on real tick data, deploys only what passes, and guards a live portfolio with real money on it.

Showcase, not for sale

99live strategy charts
176strategies coded from courses and research
26,488tester runs on real ticks since 15 Sep 2026
9parallel testers on real ticks
3 to 5Claude agents at any time
24/7orchestrator on duty

What it is

Claude NY is my autonomous trading research and operations system. A Claude agent (Claude Opus, by Anthropic) lives on a Windows server in New York and never clocks off. I set the rules and the goals in plain language. It does the engineering: it reads trading ideas from free courses, YouTube strategies, published papers and my own older Expert Advisors, writes each one as an MQL5 Expert Advisor, and sends it to a second machine in Perth that tests it on real tick data.

Only strategies that clear a strict bar go live. From then on the agent watches them, protects them and keeps improving them, writes to the broker on my behalf, and reports to me. I can reach it from my phone at any hour through Claude Code Remote Control.

Architecture

Two machines with different jobs, a git repository as the nervous system, and AWS for data and mail.

Claude NY architecture: Luca sets rules; on the New York VPS the Claude orchestrator, agents, watchers, live MetaTrader 5 and the risk daemon; in Perth nine Strategy Testers and a standing queue; a GitHub bus between them; AWS Sydney for data, secrets and mail.
How Claude NY works: I set the rules, Claude builds, tests, deploys, protects and reports. Diagram drawn by Claude NY itself.
New York · Windows Server VPS

The brain and the live desk

  • Live MetaTrader 5 terminal, one chart per strategy (99, the platform's maximum)
  • Python risk daemon guarding every open trade
  • Watchers streaming events into the agent
  • The Claude Code orchestrator session
Perth · a 2020 gaming laptop

The muscle

An Acer Predator Helios 300 bought in Canada in 2020 and upgraded by hand: Intel Core i7-10750H (6 cores, 12 threads), 64 GB DDR4, RTX 2070 Max-Q, and two 4 TB NVMe drives plus a 1.92 TB SSD, almost 10 TB in all.

  • 9 MetaTrader 5 Strategy Tester copies in parallel
  • A standing job queue that never runs dry
  • Every test, study and machine learning experiment runs here
  • New York only plans, trades live and analyses
  • Plus a read-only data terminal feeding the market-data store
Private WireGuard tunnel with SSH · GitHub as the message bus: jobs, EA sources and results travel as commits
AWS · Sydney region

Data and voice

  • S3 market-data store: MT5, Binance and Dukascopy history as Parquet, one file per month, updated incrementally
  • Secrets Manager for the mail sender, and HELLO's mailer for reports and alerts by email

The whole loop in one line

Luca (phone / chat) -> Claude NY orchestrator -> agents -> GitHub bus -> Perth testers (real ticks) -> results -> scorer -> pass? -> auto-deployer -> live MT5 (99 charts) <- risk daemon (locks, guards, throttle) -> watchers -> orchestrator -> reports to Luca

The agents

One orchestrator holds the whole picture and makes deploy and retire decisions inside my standing rules. Background agents, each with exactly one job, do the rest. They talk through messages and shared files; a deploy lock and a restart gate make sure only one of them touches the live terminal at a time.

Orchestrator. Decides, deploys, retires, writes to the broker, answers me.
Course pipeline. Reads the curriculum, codes new strategies, queues batches of about 100 tests.
Course scorer. Polls Perth every 10 minutes and judges each finished group.
Live exit engineer. Makes the tester behave exactly like the live risk daemon; runs the auto-deployers.
Research agents. Web research on demand, for example stop and reverse against hold on crypto.
Data agent. Builds and feeds the market-data store.

How a strategy earns real money

  1. Idea. A course lesson, a YouTube strategy, a paper, or one of my old EAs.
  2. Code. Claude writes it as an MQL5 Expert Advisor, with the shared safety modules compiled in.
  3. Queue. It goes to Perth as a git commit and joins the standing queue.
  4. Test on real ticks. One week, one month, one year, then an out-of-sample year. Crypto is split into weekdays and weekends; everything is split by weekly open, weekly close, the rest of the week and news.
  5. The bar. All four must hold, or it does not go live: positive monthyear drawdown at most 10%profit factor at least 1.2positive out-of-sample year
  6. Deploy. The auto-deployer puts it on a live chart. If the profile is full, the weakest chart is retired first.
  7. Grow carefully. A lot-size sweep: a bigger lot only if every smaller size has passed too.
Bar chart of completed Strategy Tester runs per day on the Perth machine, rising from a few hundred to over 4,600 a day, 26,488 runs since 15 September 2026.
Every strategy is tested on real ticks before it trades: 26,488 completed tester runs since 15 Sep 2026, up to 4,600 in a single day.
One ETH weekend at five-minute resolution with a Bollinger band and the fade signals of the WeekendRevert idea, from public Binance data.
What an EA sees: the WeekendRevert fade idea on one ETH weekend (public Binance data, illustrative).

Risk controls

Never close at a loss automatically. A virtual first lock arms at a small net profit and closes only while the trade is still positive. Losers wait; only I close a negative trade, by hand.
Stop guard. Broker stops may only sit where even a slipped fill is still positive.
Exposure caps. An account-wide cap on concurrent losing trades, and a margin-level gate on new entries.
Calendar guards. High-impact news, weekend and rollover windows, and quote gaps at the open.
Broker-load throttle. Back-off after any rejected request, with per-trade and per-minute caps.
Restart and bar guards. At most one planned restart per 2 hours; a restarted EA never re-enters the same signal.
Inside every EA. A profit lock, lot sizing from free margin, and a cap on negative trades per strategy.

Monitoring and recovery

Watchers stream every trade close, risk-daemon event, Perth failure, idle alarm and lot-sweep verdict straight into the agent's session. The server reboots daily on purpose: a resume checklist and a logon hook bring every watcher and agent back. Scheduled guards restart the risk daemon if it ever dies, a hygiene task compacts git storage every 4 hours, and if Claude's login is ever revoked I get an email.

Every rule I set and every lesson it learns is written to persistent memory files, so its behaviour survives restarts instead of starting from zero each morning.

Lessons that became rules

Every incident changed the system, not just the moment.

A broker stop slipped and a "safe" stop became a loss→Profit locks went virtual; the never-close-negative rule was born
The broker renamed a symbol→Charts are identified by magic number, never by name or file
MT5 refused a 100th chart→Profile compaction, and retire before add
A rejected modify was retried in a tight loop and the broker noticed→Request throttle and restart gate
Test-result history filled the disk→Git compaction every 4 hours
Tester exits differed from live exits→The live exit logic now runs inside the tester

Giving back

Building Claude NY meant reading other people's MetaTrader tools closely. Where one could hurt a live account, I wrote it up for the maintainer, with the fix.

Components

The 99 live charts by market (indices 40, gold and silver 27, forex 19, crypto 12, stocks 1) and by strategy family (Learn course strategies 31, HourOne 29 and others).
The live portfolio: 99 strategies across indices, gold and silver, forex, crypto and stocks, by market and by strategy family.

Best week so far

In its best week, 26 Sep to 3 Oct 2026, on a 14,000 AUD deposit made on 23 Sep 2026, Claude NY made +447.81 AUD net on closed trades: about +3.2% of the deposit in seven days.

Best week, not an average: closed trades only (profit plus swap plus commission), open positions not included, and the account was eleven days old when this was written (5 Oct 2026). Past results say nothing certain about future ones.

Milestones

2025 My first live algorithmic trading system with Claude models in the loop, and hard risk limits.

Mid 2026 The first Claude-built EAs and studies on the New York server.

Sep 2026 The Perth testing machine linked; the learning programme starts: every free course and YouTube strategy tested as an EA.

30 Sep 2026 The never-close-negative rule and virtual profit locks.

2 to 3 Oct 2026 Re-entry and predicted-entry studies live; tester and live exits unified; the profile reaches 99 charts.

4 Oct 2026 Request throttle and restart gate; the AWS market-data store started; batch 22 (Heikin Ashi, Hull MA, Ehlers Fisher) live.

Why it matters to me

Thirty years of running technology taught me that the hard part is never the clever bit. It is the guard rails, the recovery, the rule that survives the next incident. Claude NY is that lesson with an AI doing the engineering: I decide what must never happen, and the agent builds, tests and runs everything inside those lines. It is a showcase of how I work, not a product and not advice.

Trading carries real risk of loss. Nothing on this page is financial advice.