What Claude Code Actually Is

Claude Code is an AI coding assistant that runs in your terminal. You describe what you want, and it writes the code. It can read your files, edit them, run commands, and iterate based on errors.

It’s genuinely powerful. I built 6 trading bots with it, and I’m not the kind of developer who builds trading bots.

But it has limits. Understanding those limits is the difference between building something that works and building something that looks like it works.

What Claude Code Is Great At

Writing Boilerplate

Exchange API connections, order placement, data fetching — Claude handles these perfectly. The ccxt library setup, Binance Futures authentication, OHLCV data fetching: all standard patterns that Claude knows well.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

# Tell Claude: "Connect to Binance Futures and fetch 5m candles"
# You'll get something like:

import ccxt

exchange = ccxt.binance({
    'apiKey': API_KEY,
    'secret': API_SECRET,
    'options': {'defaultType': 'future'},
    'enableRateLimit': True,
})

ohlcv = exchange.fetch_ohlcv('BTC/USDT', '5m', limit=100)

This code works. First try. Every time.

Implementing Known Algorithms

RSI calculation, moving averages, Bollinger Bands, CHOP index — Claude knows these. If you ask for an RSI calculation, you’ll get a correct implementation.

Debugging

This is where Claude really shines. Paste an error, describe the context, and it’ll find the bug faster than you can read the stack trace. My timezone bug? Claude found it in seconds once I described the symptom.

Refactoring

“Make this function handle both long and short positions” — Claude excels at structural changes. It understands code patterns and can transform them cleanly.

What Claude Code Is Terrible At

Trading Strategy Design

Claude will build whatever strategy you describe. It will not tell you the strategy is bad.

I asked Claude to build a grid bot. It built a beautiful grid bot. It worked flawlessly — the code was perfect. The strategy was structurally broken in trending markets.

Claude didn’t warn me. It’s not a quant researcher. It’s a code generator.

You need to know what to build. Claude knows how to build it.

Backtest Interpretation

Claude can tell you the numbers. It cannot tell you if those numbers mean anything.

“Your win rate is 85%!” — Claude will report this proudly. It won’t mention that an 85% win rate with a 1:0.3 risk-reward ratio is a losing strategy.

You need to understand trading statistics. Claude just runs the calculations.

Market Intuition

“Should I use a 14-period or 21-period RSI?” Claude will give you a reasonable-sounding answer. It has no idea which one works better in crypto specifically, in the current market regime, for your timeframe.

Test everything. Trust data, not AI opinions.

How to Get the Best Results

1. Be Specific About Requirements

Bad prompt:

“Build me a trading bot”

Good prompt:

“Build a trend-following bot for Binance USDT-M Futures. Entry: 5m candle body ≥ 0.7% AND volume ratio ≥ 1.8 AND CHOP index < 50. Exit: 2% trailing stop activated at 2% profit, checked on 5m candle close only. Use ccxt library.”

The more specific you are, the less Claude needs to guess. Guesses are where bugs hide.

2. Build Incrementally

Don’t ask Claude to build the entire bot at once. Build in layers:

  1. Exchange connection + data fetching
  2. Signal detection (entries)
  3. Order placement
  4. Exit logic (SL, trailing, TP)
  5. Position management
  6. Logging and monitoring

Test each layer before adding the next. This way, when something breaks, you know which layer caused it.

3. Always Read the Code

Claude writes correct-looking code that sometimes has subtle bugs. The stop loss might check > instead of >=. The timestamp might be off by one candle. The order type might be wrong for your exchange.

Read every line. Understand every line. If you can’t explain what a line does, you shouldn’t deploy it with real money.

4. Build the Backtest First

Before building the live bot, build the backtest. This gives you:

  • A reference implementation to compare against
  • Confidence that the strategy works (or doesn’t)
  • A testing framework for parameter changes

Then build the live bot to match the backtest exactly. This is hard — I spent weeks aligning them — but it’s essential.

5. Ask Claude to Explain, Not Just Build

“Explain how this trailing stop logic works step by step”

“What edge cases could break this position sizing code?”

“Walk me through what happens when the exchange returns an error here”

Claude’s explanations are often better than its code. Use them to build your understanding.

The Process That Works

1. Research strategy (YOU, not Claude)
2. Define exact rules on paper (YOU)
3. Build backtest (Claude + YOU reviewing)
4. Validate with out-of-sample data (YOU analyzing)
5. Build live bot matching backtest (Claude)
6. Dry run comparison (YOU monitoring)
7. Live deploy with small capital (YOU deciding)

Steps 3 and 5 are where Claude does the heavy lifting. Steps 1, 2, 4, 6, and 7 are where you do the heavy lifting.

AI is the tool. You are the engineer.

Claude Code can build you a trading bot in a day. Whether that bot makes money depends entirely on what you told it to build.