Credentials. Your LLM key lives in the runtime .env, so keep it private and out of shared folders.
Who it is forA developer with a strategy idea who does not want to write data loading and backtest code by hand.
The problemTesting even a simple moving-average idea means wiring data, signals and metrics together first.
The outcomeA finished backtest with a summary of return and drawdown, and the generated code saved in the run directory.
What you need first
- Python 3.11 or later for a local install, or Docker
- An LLM API key from a supported provider, or Ollama locally
- Market data works without keys for many markets through free fallbacks
Steps
- Install with
pip install -U vibe-trading-ai - Run the interactive setup (vibe-trading init in the README quick start) to write your .env with an LLM key
- Ask for a backtest with vibe-trading run and a prompt, for example a BTC-USDT 20/50 moving-average strategy for 2024
- Read the run card: settings it did not recognise are reported, and values it cannot compute come back as null instead of a guess
Prompt for your agent
Install HKUDS/Vibe-Trading and backtest <strategy in plain English> on <symbol> for <period>. Report return, max drawdown and number of trades, and list any backtest setting the run card flagged as unrecognised.
Caveat. A backtest is not a forecast, and the project warns it has never launched a token, so ignore any coin using its name. Not financial advice: paper trade first, and remember you can lose money.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for HKUDS/Vibe-Trading and "Backtest a trading strategy described in plain English"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer