Operate a crypto trading bot nightly and stress-test proposed strategy changes

A hobbyist had Claude run a spot crypto bot's evening checks and reports. It found a holding-period tweak that flipped a backtest from -10 to +22, then talked itself out of shipping it.

Done withClaude· Nov 9, 2026

What they did

The author runs a small spot-only crypto trading bot as a side project and handed its daily operations to Claude. Every evening the agent checks the bot, runs analyses on past trades, writes a daily report and proposes changes. It may not change trading logic by itself. The author also gave it a short plain-language rulebook, including one rule that logic only changes once an edge is confirmed, and that a rejected idea must be written down with the reason. When the agent saw most losses came from round trips of a few hours, it backtested a minimum holding period on about four months of 15-minute candles, trying 17 variants.

How it went

The backtest looked like a win: no hold gave 178 trades and about -10 cumulative, an 8 hour hold about +9, a 24 hour hold about +22 with a 50% win rate. The agent then tried to break it. Bootstrapped 95% intervals crossed zero for every setting, the latest period lost money for all of them, simply holding the asset made about +44, and random entries did about as well as the current rules. Nothing was deployed. The agent instead started a forward-only comparison of the 24 hour variant, to be judged after 30 round trips or four weeks.

Worth knowing

The agent has no memory between evenings, so the author makes it log rejected ideas and the criteria for revisiting them in a Decisions and reasons section of each report, or the same tweak returns every day. The author credits the written rule, not the model, for stopping the change. The harness running Claude was not named, and the forward test had no result yet.

Try it

With Claude· 4 parts to fill in

You are the nightly operator for my trading bot at [repo or server path]. Each evening: check the bot is running, pull the day's trades from [exchange or log file], analyse wins and losses, and write a report to [report location]. You may propose strategy changes but never edit trading logic. For any proposal, backtest it on [period] of data and then try to break it: bootstrap confidence intervals, split the data into periods, compare against buy-and-hold and random entries, and count how many variants you tried. Only recommend a change if it survives all of that. Record every rejected idea and what would make you revisit it under a Decisions and reasons heading, read that section before proposing anything, and stop after the report for my review.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related