TradingAgents: When LLMs Build a Trading Firm — Mapping Wall Street Roles onto GPUs
The Scenario
Imagine walking into a Wall Street trading firm. Fundamental analysts on the left, sentiment analysts on the right, a news analyst glued to the Bloomberg terminal, a technical analyst staring at candlestick charts. In the back room sit the researchers — bull and bull-bear teams debating across the table. Further in, a trader synthesizes everyone's views and places orders, a risk team watches volatility and liquidity, and finally a portfolio manager signs off.
What TauricResearch's TradingAgents does is port this division of labor, unchanged, into LLMs. Each role is played by an LLM agent; agents collaborate through structured conversations to produce a final trading decision. It's not a single model improvising — it's an entire LLM team running a process.
Architecture: A Trading Firm, LLM Edition
TradingAgents' core design is role specialization + debate mechanics, organized into four layers:
Analyst team — four agents, each with a distinct remit:
- Fundamentals analyst: reads company filings and performance metrics to find intrinsic value and red flags
- Sentiment analyst: aggregates headlines, StockTwits, and Reddit posts into a single sentiment reading
- News analyst: monitors global news and macro indicators, interpreting event impact on markets
- Technical analyst: detects trading patterns using indicators like MACD and RSI
- v0.2.0 (February): multi-provider support — GPT-5.x, Gemini 3.x, Claude 4.x, Grok 4.x
- v0.2.3 (March): multilingual support, GPT-5.4, backtest date fidelity
- v0.2.4 (April): structured-output agents, LangGraph checkpoint resume, persistent decision logs, Docker support
- v0.2.5 (May): grounded sentiment analyst, Qwen/GLM/MiniMax dual-region support, Ollama local models
- v0.3.0 (June): validated data-access contracts, expanded provider registry (NVIDIA, Kimi, Groq, Mistral, Bedrock), FRED and Polymarket data sources
- v0.3.1 (July): Alpha Vantage look-ahead filtering, graph-router crash safety, graph-shape-aware checkpoint resume, Claude Sonnet 5 / Fable 5 support
- Octopus-style DNA pretraining + RNA inference-time compute — different layers for different problems
- SOPHIA's differential flow directions — different exit directions for different states
- Euclid-MCP's LLM + Prolog — LLM as poet, Prolog as accountant
- Rebucca's small-model screening + large-model verification
- GitHub: https://github.com/TauricResearch/TradingAgents
- Paper: https://arxiv.org/abs/2412.20138 (267 citations)
- Latest version: v0.3.1 (2026-07)
- Supported providers: OpenAI / Anthropic / Google / xAI / DeepSeek / Qwen / GLM / Mistral / Groq / NVIDIA / Bedrock / Ollama
- License: MIT
Researcher team — bull and bear agents critically evaluate the analysts' insights. Through structured debate, they weigh potential upside against risk. This step is key — you don't trade immediately; you argue first.
Trader agent — synthesizes analyst reports and the researcher debate to decide trade timing and size.
Risk management + portfolio manager — the risk team continuously evaluates volatility, liquidity, and other factors, adjusts strategy, and produces an assessment. The portfolio manager approves or rejects the proposal. Once approved, the order goes to a simulated exchange.
The most notable aspect of this architecture: it doesn't ask one LLM to do everything — it decomposes the trading decision into specialized roles, letting each agent handle only its own part. This is isomorphic to the org structure of a real trading firm — not a coincidence, but a deliberate design choice.
Academic Backing: 267 Citations
TradingAgents isn't an ad-hoc framework; it has a research paper behind it. The paper, arXiv:2412.20138, was published in December 2024 and has accumulated 267 citations — a solid count for the AI-for-finance field.
The paper's core contribution is showing that multi-agent debate produces more stable decisions than single-agent decision-making. The bull/bear researcher debate isn't theater; adversarial discussion surfaces blind spots. This mirrors real-world investment-committee debates — no single person thinks through everything; decisions emerge from clashing perspectives.
Engineering: From Paper to Open-Source Framework
Since its first release, TradingAgents has iterated rapidly to v0.3.1:
Several engineering decisions stand out:
1. No provider lock-in: supports OpenAI, Anthropic, Google, xAI, DeepSeek, Qwen, GLM, Mistral, Groq, NVIDIA, Bedrock, and any OpenAI-compatible endpoint. You can use different models for different roles — e.g., GPT-5.5 for fundamentals, Claude 4.6 for debate, a local Ollama model for sentiment.
2. LangGraph checkpoint resume: the pipeline (analysts → researchers → trader → risk) can be long; if it crashes mid-run, checkpointing lets you resume from the failure point instead of starting over.
3. Look-ahead filtering: filters future information during backtests to prevent data leakage from inflating returns — a classic quant backtesting pitfall, specifically addressed in v0.3.1.
4. Structured outputs: the Research Manager, Trader, and Portfolio Manager all emit structured output rather than free text, so downstream agents can reliably parse upstream results.
The Analogy: Specialization Beats Unification
TradingAgents embodies a recurring engineering principle: division of labor beats monolithic unification.
TradingAgents is this principle instantiated in finance: rather than one LLM doing everything, specialized roles do specialized work. The fundamentals analyst doesn't need to understand technical indicators; the technical analyst doesn't need to read the news. Each agent handles its own domain, integrated through structured dialogue.
The design has a hidden advantage: debuggability. When a trading decision goes wrong, you can localize the failure — did the sentiment analyst misread Reddit? Was the bull researcher's debate insufficiently thorough? Did the risk team miss a liquidity issue? A single-LLM black box offers no such attribution granularity.
Real-World Limitations
TradingAgents explicitly states it is for research purposes only, not investment advice. Trading performance depends on many factors: backbone model choice, temperature parameters, trading horizon, data quality, and non-deterministic effects. The framework currently connects to a simulated exchange, not real trading.
That limitation is reasonable. LLM agents aren't yet reliable enough in financial trading to manage real money. But as a research framework, it provides a reproducible, debuggable, comparable experimental platform for multi-agent trading.
Data
Why It's Worth Watching
TradingAgents grounds the abstract concept of "multi-agent collaboration" in a concrete domain — financial trading. Its value goes beyond trading itself: it demonstrates how to map a human organization's division of labor onto an LLM agent architecture. Analysts → researchers → trader → risk → portfolio manager maps one-to-one onto a real trading firm.
This "organizational isomorphism" design pattern transfers to other multi-role domains — medical diagnosis (symptom analysis → differential diagnosis → treatment decision → risk review), legal analysis (fact gathering → statute matching → debate → review), even code review (static analysis → security audit → performance evaluation → architecture review).
As LLM agents move from solo operation to team collaboration, TradingAgents offers a template worth studying.