RepoPilot

tauricresearch / tradingagents

Search tauricresearch/tradingagents

GitHub

Code

How tauricresearch/tradingagents is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new financial data vendor

  • Implement data accessor functions following Yahoo/Alpha Vantage patterns
  • Register vendor in the router to map data requests to your new connector
  • Add vendor configuration and error handling to dataflows/errors.py

Add a new specialist analyst agent

  • Create new analyst class in tradingagents/agents/analysts/{domain}_analyst.py inheriting LangChain agent patterns
  • Define analyst prompt, tools, and output schema using tradingagents/agents/schemas.py
  • Register analyst node and routing logic in tradingagents/graph/setup.py
  • Export analyst from tradingagents/agents/analysts/__init__.py

Add support for a new LLM provider

  • Create new client class in tradingagents/llm_clients/{provider}_client.py inheriting from base_client.BaseLLMClient
  • Implement message formatting, streaming, and tool use compatible with LangChain
  • Register model capabilities and parameters in tradingagents/llm_clients/model_catalog.py
  • Add factory instantiation logic in tradingagents/llm_clients/factory.py

Add a new CLI command or workflow

  • Define new CLI command function in cli/main.py using Typer decorators
  • Create display helper functions in cli/display.py for Rich terminal rendering
  • Add user preference handling in cli/prefs.py if command needs persistent options
  • Call tradingagents/graph/trading_graph.py to execute agent orchestration

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

  • Branch points11 per file on average
  • Code issues0 errors, 8 warnings
  • Largest file785 lines
  • Hotspot load1 high-risk file

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions2 workflows
  • Tests89 test filesPytest · 0.95 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: tests

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.