EagleCapital

A personal trading operations suite — started as a prop-firm account tracker, has grown into a full toolkit spanning account tracking, live broker sync, trade copying, journaling, and AI-backed review. No firm's rules or risk math are hardcoded in anywhere; every number is either user-entered or pulled live from a real broker. Data is per-user in Supabase (sign in required).

What's in here

• Accounts — prop-firm challenges/evaluations/funded accounts and real live broker accounts, side by side. No firm's rules are encoded; risk limits, payouts, rewards, and funded dates are all manual entry, since every firm's math is different.
• Trade Copier — real-time copying between MT5 accounts, executed by a Windows worker (worker/) that holds the broker MT5 terminals open and places the orders itself. It is the only part of the system that can reach a broker. The worker is platform infrastructure: the founders run it and it serves every user, each in their own process, claimed through expiring leases so no user is ever run by two machines. Add machines to scale out. Master/follower copy links (created disarmed), risk profiles with stopouts/unlock, a per-copy execution log, and test-connection / close / flatten commands pushed to the worker. The worker applies symbol mappings from the symbol_mappings table, but the app has no screen for editing them yet. The worker also has a DXtrade executor. cTrader and MT4 are stubs, and Tradovate is blocked. Futures copying isn't built.
• Live Trading — open positions across every connected account with unrealised P&L, streamed from the worker's snapshots over Supabase Realtime, with a per-position Close.
• Live MT5 sync into the journal — a copier account can be linked to a dashboard account ("Journal trades"). The worker then journals its closed trades from the terminal's own deal history and reports its balance. The balance comes from the broker's figure at link time (opening_balance_at), so the 72h backfill isn't counted twice.
• Broker Connections (parked) — the older MetaApi.cloud (MT5) and Tradovate credential flow. It depends on the separate eaglecapital-broker-sync service, which isn't deployed. The page is hidden from the nav unless VITE_BROKER_SYNC_API_URL is set. Tradovate is also blocked on a paid API plan.
• Trade Journal & Trade Log — manual entry or CSV import (MT4/5-style exports), a 3-pane journal (list / stats·tags·notes·strategy / price chart via Financial Modeling Prep), and playbooks with real performance stats tied to logged trades, exportable to PDF/Word.
• Trader Management — a daily Report Card (execution checklist built from your own rules, not a generic list, the "5 Whys" process review) and a personal rules library, independent of any prop firm.
• AI Insights — two layers: free, instant, deterministic pattern detection (revenge trading, overtrading, size escalation — computed straight from your trade log, no API call) plus an on-demand coaching digest from the trading-insights Edge Function. It uses Groq if GROQ_API_KEY is set, otherwise Anthropic, and is capped per user per day.
• Economic Calendar — real structured release data (not an embed), proxied from the ForexFactory weekly feed by the economic-calendar Edge Function, filterable by impact and by country/instrument.
• Charting — a full TradingView "Advanced Chart" widget for any symbol.
• Settings — username, CSV + JSON export, sign out, and account deletion (a 30-day reversible request, completed server-side by purge-deleted-accounts).
• Observability — Sentry (errors/performance) and PostHog (usage analytics, capture deliberately conservative — no session replay, autocapture text/attributes masked — since the UI shows real balances and trade data).

There is no separate backend service for the copier. The browser reads and writes the copier's tables directly under RLS. The copier-gateway Edge Function handles the two things that need ENCRYPTION_KEY (connecting an account, fixing its credentials) and is the worker's fallback API. The worker itself talks to Postgres directly (worker_api functions) and receives commands by NOTIFY. See WORKER.md for the whole picture.

Quickstart

npm install
npm test        # run the test suite
npm run lint    # correctness lint — run it, typecheck alone misses hook-order bugs
npm run dev     # open http://localhost:5173

Requires a Supabase project. Set the env vars in .env.example in .env.local, then run these three files in the SQL editor, in this order:

1. supabase/schema.sql — the app's tables.
2. supabase/delta-engine-schema.sql — the copier's tables (read its header first).
3. supabase/migrations-worker-direct.sql — the worker's direct database path.
4. supabase/migrations-shared-worker.sql — one worker serving every user (leases, terminal reservation, the operator fleet view).

All four are idempotent. The other supabase/migrations-*.sql files are deltas for a database created before they were folded into the two schema files. A fresh project doesn't need them.

Deployment

Three pieces, none of which a git push deploys completely:

• Frontend — Vercel. Set the VITE_* vars in the Vercel dashboard. .env.local never reaches production.
• Supabase — the SQL above, plus four Edge Functions (copier-gateway, trading-insights, economic-calendar, purge-deleted-accounts) and their secrets. See DEPLOY.md.
• Worker — one or more Windows machines with the brokers' MT5 terminals, run by the founders and shared by every user. See WINDOWS-SETUP.md for the bring-up and worker/README.md for running and scaling it.

The GitHub remote is still named prop-tracker (github.com/Chris-Selorm-Gadze/prop-tracker) from before the app outgrew that name — renaming it is a deliberate call to make later (affects clone URLs and any CI/deploy hooks tied to it), not something to do in passing.

Where things are

Path	What
CLAUDE.md	Architecture and invariants (context for Claude Code sessions)
workflow.txt	Change log, incl. the LOAD-BEARING fixes not to revert
later.txt	Known gaps deliberately deferred
DEPLOY.md	Supabase deploy steps: schema, Edge Functions, secrets, cron
WORKER.md	How the worker, the database and the gateway fit together
WINDOWS-SETUP.md	Step-by-step bring-up of the Windows worker
supabase/schema.sql, supabase/delta-engine-schema.sql	Postgres schema + RLS policies (app, copier)
supabase/migrations-*.sql	Deltas for databases created before a change was folded in; migrations-worker-direct.sql and migrations-shared-worker.sql are still required
supabase/functions/	Edge Functions: copier-gateway, trading-insights, economic-calendar, purge-deleted-accounts
scripts/verify-copier-gateway.sh	Contract check for the gateway's worker endpoints
worker/	The Windows copy engine (Python + PowerShell); engine/tenancy.py is the multi-user supervisor — see worker/README.md
src/db/	Supabase-backed data access (accounts, sessions, payouts, rewards, trades, report cards, playbooks, trading rules, copier, live positions, broker connections, account deletion)
src/features/accounts/	Prop-firm + live account management, risk cockpit
src/features/copier/	Trade Copier page
src/features/liveposition/	Live Trading page
src/features/brokers/	Broker Connections (parked MetaApi/Tradovate flow)
src/features/trades/	Trade Log + Trade Journal
src/features/playbooks/	Setup library with performance stats and PDF/Word export

Disclaimer

Personal tool for tracking accounts and journaling trades — not financial advice, and not a substitute for your own risk judgment. No firm's rules or risk math are encoded anywhere; the Trade Copier mirrors real orders between accounts you connect, so treat it with the same care as any other live-trading tool.